# Fresh SDK upgrade fails at pod install with a Mapbox clash, while a sibling app on the same SDK builds

> 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.

Web page: https://davidewins.com/errors/mapbox-pod-install-after-fresh-expo-install

iOS. Likely fix, 9 October 2026.

Versions: 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](https://davidewins.com/errors/rnfirebase-spm-static-linkage)
- [iOS build fails in react-native-skia: 'third_party/base64.h' file not found](https://davidewins.com/errors/skia-base64-h-not-found-use-frameworks)
- [Dev build fails codesigning: provisioning profile doesn't include the Apple Pay capability](https://davidewins.com/errors/apple-pay-entitlement-dev-bundle-id)
- [EAS iOS build stops at signing: provisioning profile expired](https://davidewins.com/errors/eas-expired-provisioning-profile-noninteractive)

[Search all errors](https://davidewins.com/errors)
