Sravan/BizGaze_Remote
0
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix pod install: drop the stale Podfile.lock that cap-sync's pod install created

Browse Source 
The git-tag pin worked, but the build failed: "could not find compatible versions
… In snapshot (Podfile.lock): LiveKitClient (= 2.0.18) … In Podfile: LiveKitClient
(from git, tag 2.15.3)". Cause: `npx cap sync` runs `pod install` internally with
the PRE-pin Podfile, creating a Podfile.lock pinned to 2.0.18; our injected git-tag
source then conflicts with that lock. Fix: rm the Podfile.lock right after injecting
the pin so the real "Install CocoaPods" step re-resolves against tag 2.15.3.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Sravan
2026-07-31 19:55:10 +05:30
parent 2c97f45245
commit bcd5699e2a
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mobile/scripts/ios-patch.sh
+5
View File
@@ -149,6 +149,11 @@ if [ -f "$PODFILE" ]; then
'
fi
grep -n "LiveKitClient" "$PODFILE" || true
# `npx cap sync` already ran `pod install` with the PRE-pin Podfile, leaving a Podfile.lock that pins
# LiveKitClient = 2.0.18 — which conflicts with the git-tag source we just injected ("could not find
# compatible versions … In snapshot (Podfile.lock): LiveKitClient (= 2.0.18)"). Drop the lock so the
# later "Install CocoaPods" step re-resolves cleanly against tag 2.15.3.
rm -f "mobile/ios/App/Podfile.lock" && echo "Removed stale Podfile.lock (cap-sync pinned 2.0.18)"
fi
echo "Info.plist patched:"