From bcd5699e2a608dfb284d9cfd2d38b33af1965fea Mon Sep 17 00:00:00 2001 From: sravan Date: Fri, 31 Jul 2026 19:55:10 +0530 Subject: [PATCH] Fix pod install: drop the stale Podfile.lock that cap-sync's pod install created MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- mobile/scripts/ios-patch.sh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/mobile/scripts/ios-patch.sh b/mobile/scripts/ios-patch.sh index 2d3f585..92e587f 100644 --- a/mobile/scripts/ios-patch.sh +++ b/mobile/scripts/ios-patch.sh @@ -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:"