Unable to find a specification for `ExpoModulesCore` depended upon by `EXApplication`
See original GitHub issueSummary
Since upgrading expo to SDK 44, I get the following error while running pod install --repo-update:
Unable to find a specification for ExpoModulesCore depended upon by EXApplication
I also upgraded all the other expo packages I was using. I am currently using the following packages and versions:
- expo: 44.0.5
- expo-keep-awake: 10.0.1
- expo-notifications: 0.14.0
- expo-secure-store: 11.1.0
I am using react-native version 0.67.0.
Is someone also having this problem?
Thank you!
Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!
bare
What platform(s) does this occur on?
iOS
SDK Version (managed workflow only)
44
Environment
System: OS: macOS 11.2.3 CPU: (8) x64 Intel® Core™ i7-4770HQ CPU @ 2.20GHz Memory: 437.14 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 14.16.0 - /usr/local/bin/node Yarn: 1.22.11 - /usr/local/bin/yarn npm: 7.18.1 - /usr/local/bin/npm Watchman: 2021.11.15.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.11.2 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4 Android SDK: Not Found IDEs: Android Studio: 4.1 AI-201.8743.12.41.7042882 Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild Languages: Java: 11.0.11 - /usr/bin/javac npmPackages: @react-native-community/cli: Not Found react: Not Found react-native: Not Found react-native-macos: Not Found npmGlobalPackages: react-native: Not Found
Reproducible demo
I get the error while running pod install --repo-update.
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (1 by maintainers)
Top Related StackOverflow Question
In my case I faced this error when integrating Expo Modules to a Bare RN
0.67.2Project. However, the project is a monorepo with multiple targets in the Podfile. This custom structure meant the auto patch failed.I added this snippet (from the setup guide) to the very end and everything works now.
EDIT: some findings / background - for my use case is desire to simply use expo-web-browser and get an app with 4 tabs. It seemed like I could simply start up the expo project and quickly eject. This I believe is what the expokit sdk was for - which is deprecated/obsolete. Ejecting seems like a road to horror / or at least unfavourable to get things working. To get around this problem - seems like best to start a new expo project - import/ cherry pick across all the code - and avoid run expo eject. I’m fine with that - it should be noted that running expo run:ios (automatically runs eject) as opposed to yarn run ios which keeps you inside expo. The fixes below are likely to be out of date come sdk 45.
RANDOM RAMBLINGS - TROUBLESHOOTING I’m running node 14 and seeing same problem - if that helps. going to bump to later version.
still no joy.
this is my package.json https://gist.github.com/pe-johndpope/74d330f531d2fed95c997a14a264cb38
UPDATE - still no joy… I’m seeing this with sdk 43…
PARTIALLY WORKING
package.json -> “expo”: “42.0.0”, app.json -> “sdkVersion”: “42.0.0”
downgrading to 42 works for now. Need to remove Podfile react_native_post_install
https://stackoverflow.com/questions/66833868/how-do-i-troubleshoot-an-error-with-react-native-and-cocopods-on-a-mac-using-r
UPDATE - FIX you’re gonna need to overhaul your podfile with extra things here’s a comparison to my broken file. https://gist.github.com/pe-johndpope/e34987568454dd3b4b3fc8104122414b