Android Build Error: ":expo-core" not found in ":expo-react-native-adapter"
See original GitHub issue🐛 Bug Report
Environment
Expo CLI 2.10.1 environment info: System: OS: macOS 10.14.2 Shell: 3.2.57 - /bin/bash Binaries: Node: 8.11.4 - /usr/local/bin/node Yarn: 1.12.1 - /usr/local/bin/yarn npm: 5.6.0 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Android Studio: 3.3 AI-182.5107.16.33.5314842 Xcode: 10.1/10B61 - /usr/bin/xcodebuild npmGlobalPackages: expo-cli: 2.10.1
My app’s target is Android
Steps to Reproduce
When I try to build my app in the Android Studio, I get below error.
Project with path ':expo-core' could not be found in project ':expo-react-native-adapter'.
in “android/build.gradle”.
Does anyone know how to fix this issue?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
React Native Error: Project with path ':expo-modules-core ...
I have tried updating Expo as well as installing an older version of it instead and I'm still getting the same error. Not...
Read more >Error in EAS build caused by expo-react-native-adapter
I'm running into build failures on Android EAS build. ... I'm getting two errors: “Plugin with id 'maven' not found.
Read more >React-Native and WebGL without Expo | by Steve Liles | Medium
From the project navigator, open your project, then the Libraries folder and remove the EXGL library. If you don't do this you'll get...
Read more >expo-react-native-adapter - npm
Start using expo-react-native-adapter in your project by running `npm ... lines inside the dependencies block in android/app/build.gradle :.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems in my case I had an outdated dependency on
expo-react-native-adapter
, which was added when upgrading to Expo 34. It seems as if this has been subsumed byreact-native-unimodules
, and seems to work after removing.Hey @thlee1122,
This is an ejected Expokit project, correct? Also, what version of the Expo SDK are you using and did you recently upgrade that version? It would help if you provided a way to reproduce the error you’re getting
Thanks! -Charlie