Fresh SDK upgrade fails at pod install with a Mapbox clash, while a sibling app on the same SDK builds
iOSLikely fix
Expo SDK 57, @rnmapbox/maps
There is no error message for this one, only the symptom in the title.
Cause
A fresh install pulled newer patch versions of Expo packages than the known-good app's lockfile, and the newer Expo modules clashed with Mapbox's prebuilt binaries.
Fix
Pin the shared packages to the exact versions from the known-good lockfile, remove packages the app does not need, then run npx pod-install locally before spending a cloud build.
More iOS errors
- pod install fails: react-native-firebase SPM + static linkage is not supported[!] [react-native-firebase] SPM + static linkage is not supported (target(s): ...). firebase-ios-sdk's Swift Package products are automatic libraries (not `type: .dynamic`), so each react-native-firebase pod that resolves Firebase via SPM embeds its own copy.
- iOS build fails in react-native-skia: 'third_party/base64.h' file not foundnode_modules/@shopify/react-native-skia/cpp/api/third_party/base64.cpp:7:10: fatal error: 'third_party/base64.h' file not found
- Dev build fails codesigning: provisioning profile doesn't include the Apple Pay capabilityprovisioning profile doesn't include the Apple Pay capability
- EAS iOS build stops at signing: provisioning profile expired