EAS iOS build failed: Compatible version of some pods could not be resolved. Fully Managed Workflow

See original GitHub issue

Summary

iOS build failed: Compatible version of some pods could not be resolved. You are seeing this error because either:

Versions in the Podfile.lock cached by EAS do not match required values for some of the libraries, it can be triggered when upgrading Expo SDK or any other library with native code. To fix that update value of “cache.key” field in the eas.json to invalidate the cache. Some of your npm packages have native code that depend on different versions of the same pod. Please see logs for more info. Tried as per above error message said cache.key to invalid or any string in eas.json file No fix yet, need a more clear idea about this error.

eas.json file:

{ “build”: { “preview”: { “ios”: { “node”: “16.13.0”, “simulator”: true, “cache”: { “key”: “181121” } } }, “release”: {}, “release-stage”: { “ios”: { “releaseChannel”: “stage”, “image”: “latest”, “cache”: { “disabled”: true, “key”: “17112021” } } }, “cli”: { “version”: “>= 0.35.0”, “requireCommit”: true } }

Environment C:_Projects\XXX>expo diagnostics

Expo CLI 4.12.10 environment info: System: OS: Windows 10 10.0.19042 Binaries: Node: 14.18.0 - C:\Program Files\nodejs\node.EXE npm: 6.14.15 - C:\Program Files\nodejs\npm.CMD IDEs: Android Studio: Version 4.0.0.0 AI-193.6911.18.40.6626763 Expo Workflow: managed

C:_Projects\XXX>eas diagnostics

EAS CLI 0.36.1 environment info: System: OS: Windows 10 10.0.19042 Binaries: Node: 14.18.0 - C:\Program Files\nodejs\node.EXE npm: 6.14.15 - C:\Program Files\nodejs\npm.CMD Utilities: Git: 2.27.0.

Error output Installing pods Installing unimodules: expo-app-auth@10.2.2 from …/node_modules/expo-app-auth/ios expo-application@3.1.2 from …/node_modules/expo-application/ios expo-constants@10.1.3 from …/node_modules/expo-constants/ios expo-device@3.2.0 from …/node_modules/expo-device/ios expo-error-recovery@2.1.0 from …/node_modules/expo-error-recovery/ios expo-facebook@11.0.5 from …/node_modules/expo-facebook/ios expo-file-system@11.0.2 from …/node_modules/expo-file-system/ios expo-font@9.1.0 from …/node_modules/expo-font/ios expo-image-loader@2.1.1 from …/node_modules/expo-image-loader/ios expo-keep-awake@9.1.2 from …/node_modules/expo-keep-awake/ios expo-localization@10.1.0 from …/node_modules/expo-localization/ios expo-location@12.0.4 from …/node_modules/expo-location/ios expo-modules-core@0.4.8 from …/node_modules/expo-modules-core/ios expo-network@3.1.1 from …/node_modules/expo-network/ios expo-notifications@0.11.6 from …/node_modules/expo-notifications/ios expo-permissions@12.0.1 from …/node_modules/expo-permissions/ios expo-splash-screen@0.13.5 from …/node_modules/expo-app-loading/node_modules/expo-splash-screen/ios expo-structured-headers@1.0.1 from …/node_modules/expo-structured-headers/ios expo-updates@0.5.5 from …/node_modules/expo-updates/ios unimodules-app-loader@2.1.0 from …/node_modules/unimodules-app-loader/ios unimodules-barcode-scanner-interface@6.1.0 from …/node_modules/unimodules-barcode-scanner-interface/ios unimodules-camera-interface@6.1.0 from …/node_modules/unimodules-camera-interface/ios unimodules-constants-interface@6.1.0 from …/node_modules/unimodules-constants-interface/ios unimodules-core@7.1.2 from …/node_modules/@unimodules/core/ios unimodules-face-detector-interface@6.1.0 from …/node_modules/unimodules-face-detector-interface/ios unimodules-file-system-interface@6.1.0 from …/node_modules/unimodules-file-system-interface/ios unimodules-font-interface@6.1.0 from …/node_modules/unimodules-font-interface/ios unimodules-image-loader-interface@6.1.0 from …/node_modules/unimodules-image-loader-interface/ios unimodules-permissions-interface@6.1.0 from …/node_modules/unimodules-permissions-interface/ios unimodules-react-native-adapter@6.2.2 from …/node_modules/@unimodules/react-native-adapter/ios unimodules-sensors-interface@6.1.0 from …/node_modules/unimodules-sensors-interface/ios unimodules-task-manager-interface@6.1.0 from …/node_modules/unimodules-task-manager-interface/ios Found some duplicated unimodule packages. Installed the ones with the highest version number. Make sure following dependencies of your project are resolving to one specific version: expo-modules-core, expo-splash-screen Auto-linking React Native modules for target XXXXXXXX: RNCAsyncStorage, RNCMaskedView, RNGestureHandler, RNReanimated, RNSVG, RNScreens, RNVectorIcons, lottie-react-native, react-native-geolocation-service, react-native-maps, react-native-safe-area-context, react-native-view-shot, react-native-viewpager, and stripe-react-native Analyzing dependencies Fetching podspec for DoubleConversion from …/node_modules/react-native/third-party-podspecs/DoubleConversion.podspec Fetching podspec for Folly from …/node_modules/react-native/third-party-podspecs/Folly.podspec Fetching podspec for glog from …/node_modules/react-native/third-party-podspecs/glog.podspec Adding spec repo trunk with CDN https://cdn.cocoapods.org/ CocoaPods 1.11.2 is available. To update use: sudo gem install cocoapods For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.11.2 [!] CocoaPods could not find compatible versions for pod “ExpoModulesCore”: In Podfile: ExpoModulesCore (from …/node_modules/expo-modules-core/ios) Specs satisfying the ExpoModulesCore (from …/node_modules/expo-modules-core/ios) dependency were found, but they required a higher minimum deployment target. [stderr] [!] <PBXResourcesBuildPhase UUID=XXXXXXXXXXXXXXX> attempted to initialize an object with an unknown UUID. XXXXXXXXXXXXXXXX for attribute: files. This can be the result of a merge and the unknown UUID is being discarded. Error: Compatible version of some pods could not be resolved. You are seeing this error because either:

Versions in the Podfile.lock cached by EAS do not match required values for some of the libraries, it can be triggered when upgrading Expo SDK or any other library with native code. To fix that update value of “cache.key” field in the eas.json to invalidate the cache. Some of your npm packages have native code that depend on different versions of the same pod. Please see logs for more info. Reproducible demo or steps to reproduce from a blank project https://github.com/durgesh2007/sample-facebook-login-code

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

iOS

SDK Version (managed workflow only)

41

Environment

–> C:_Projects\XXX>expo diagnostics

Expo CLI 4.12.10 environment info: System: OS: Windows 10 10.0.19042 Binaries: Node: 14.18.0 - C:\Program Files\nodejs\node.EXE npm: 6.14.15 - C:\Program Files\nodejs\npm.CMD IDEs: Android Studio: Version 4.0.0.0 AI-193.6911.18.40.6626763 Expo Workflow: managed

–> C:_Projects\XXX>eas diagnostics

EAS CLI 0.36.1 environment info: System: OS: Windows 10 10.0.19042 Binaries: Node: 14.18.0 - C:\Program Files\nodejs\node.EXE npm: 6.14.15 - C:\Program Files\nodejs\npm.CMD Utilities: Git: 2.27.0.

–> C:_Projects\Meel\XXXX>expo diagnostics Expo CLI 4.12.10 environment info: System: OS: Windows 10 10.0.19042 Binaries: Node: 14.18.0 - C:\Program Files\nodejs\node.EXE npm: 6.14.15 - C:\Program Files\nodejs\npm.CMD IDEs: Android Studio: Version 4.0.0.0 AI-193.6911.18.40.6626763 npmPackages: expo: ~41.0.1 => 41.0.1 react: 16.13.1 => 16.13.1 react-dom: 16.13.1 => 16.13.1 react-native: https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz => 0.63.2 react-native-web: ^0.16.0 => 0.16.5 Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

https://github.com/durgesh2007/sample-facebook-login-code

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:15 (2 by maintainers)

github_iconTop GitHub Comments

3reactions
Norfeldtcommented, Sep 30, 2022

eas build --clear-cache worked for me

3reactions
byCedriccommented, Nov 22, 2021

Hi @durgesh2007! It seems like you have versions of Expo SDK libraries that are not compatible with "expo": "~41.0.1".

  • The new Expo modules core was introduced in SDK 43, so you should not have that in your project at all.
  • Looking at your package-lock.json, you also have multiple versions of expo-modules-core, looks like 0.4.8 and 0.2.0.
  • Next to expo-modules-core, you also have multiple versions of expo-splash-screen in your project. Both 0.13.5 and 0.10.3 are there.

To make sure you always install the right version for the SDK you are using, we recommend you use expo install <package>. This avoids exactly the issue you are running into. It will take some effort to “untangle” these libraries and use the appropriate versions for SDK 41, I would heavily recommend running npm install and expo upgrade 41. It warns you that you are already on SDK 41, but it will also fix your dependencies for this specific version.

Hope it helps!

Read more comments on GitHub >

github_iconTop Results From Across the Web

expo EAS build (iOS) fails in Pod installation step (SDK45 & 46)
Error : Compatible versions of some pods could not be resolved. You are seeing this error because either: - Versions in the Podfile.lock...
Read more >
EAS build fails all the time, expo build:ios works - Expo Forums
Error : Compatible version of some pods could not be resolved. You are seeing this error because either: - Versions in the Podfile.lock...
Read more >
Troubleshooting | React Navigation
I'm getting an error "Unable to resolve module" after updating to the latest version​. This might happen for 3 reasons: Stale cache of...
Read more >
React Native Firebase
Once changed, reinstall your projects pods via pod install and rebuild your project with npx react-native run-ios . Increasing Android build memory. As...
Read more >
EAS build error - RevenueCat Community
Anyway, I had the same issue in expo managed workflow. To solve the problem I just upgraded ExpoSDK to the newest version by...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found