Skip to content

fix(ios): make podspec webrtc path relative - #2

Merged
Magmusacy merged 1 commit into
fishjam-cloud:mainfrom
Critteros:fix/podspec-relative-webrtc-path
Nov 12, 2026
Merged

Magmusacy merged 1 commit into
fishjam-cloud:mainfrom
Critteros:fix/podspec-relative-webrtc-path

Conversation

@Critteros

Copy link
Copy Markdown
Contributor

Problem

The podspec resolves @fishjam-cloud/react-native-webrtc with node and wrote the absolute directory into HEADER_SEARCH_PATHS.
CocoaPods writes the evaluated podspec to Pods/Local Podspecs/FishjamReactNativeWorklets.podspec.json, and the SPEC CHECKSUMS entry in Podfile.lock is the SHA-1 of that file.
Thus each machine, worktree and CI runner got a different checksum, and pod install left Podfile.lock modified in each app that uses this package

Change

The node resolution stays, because the package can be hoisted.
The result is now relative to the pod directory and starts at $(PODS_TARGET_SRCROOT):

-"<checkout>/node_modules/@fishjam-cloud/react-native-webrtc/common/cpp/fishjam-video/public"
+"$(PODS_TARGET_SRCROOT)/node_modules/@fishjam-cloud/react-native-webrtc/common/cpp/fishjam-video/public"
image

The absolute webrtc path in HEADER_SEARCH_PATHS went into the
evaluated podspec, so the Podfile.lock checksum was different in
each checkout and pod install left the lock file modified.

Anchor the path on PODS_TARGET_SRCROOT. Keep symlinks in __dir__,
because Xcode collapses ".." as text.
@Magmusacy
Magmusacy self-requested a review November 12, 2026 12:36
@Magmusacy
Magmusacy merged commit a50609a into fishjam-cloud:main Nov 12, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants