Errors on EAS / Expo build
See original GitHub issueEnvironment
- Expo EAS
Steps to reproduce
Use Expo EAS to build
eas build -p android
results in a build error
[stderr]
FAILURE: Build failed with an exception.
[stderr]
* What went wrong:
[stderr]
Could not determine the dependencies of task ':app:mergeReleaseNativeLibs'.
[stderr]
> Could not resolve all task dependencies for configuration ':app:releaseRuntimeClasspath'.
[stderr]
> Could not find com.mapbox.mapboxsdk:mapbox-android-accounts:0.7.0.
[stderr]
Searched in the following locations:
[stderr]
- file:/home/expo/.m2/repository/com/mapbox/mapboxsdk/mapbox-android-accounts/0.7.0/mapbox-android-accounts-0.7.0.pom
-
EAS / Expo folks saying its a package maintainer issue related to jcenter?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Troubleshooting build errors and crashes - Expo Documentation
Go to your build details page (find it on the build dashboard if you don't have it open already) and expand any failed...
Read more >Android build failed using eas build. · Issue #1101 · expo/eas-cli
While building the project using the command eas build -p android , it fails with the above errors. However, the ios build is...
Read more >EAS build failed with error code 1 but Expo Build succeeds, i ...
Please do EAS build if you was doing Expo build. This Error will be solved by doing EAS build as it removes the...
Read more >Getting error when building iOS app by using EAS : r/expo
I am creating an Expo app, which I plan to publish to the app store. I have published it to the Android store...
Read more >EAS build error - RevenueCat Community
When i run eas build it fails with the following error: (ios/Pods/RevenueCat/Sour ... Anyway, I had the same issue in expo managed workflow....
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 FreeTop 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
Top GitHub Comments
v10 isn’t really production ready for us - we can’t just not ship any code for the next few months? This is going to affect everyone on v8, expo or not…is there anything else I can do to help myself? I don’t know how I can fix a upstream dependency being removed 😦
I’ve also been struggling with this for a while. The working solution I found is to add the patch you’re talking about with mavenCentral() and mapbox credentials to
node_modules/expo/android/build.gradle
instead ofnode_modules/react-native-mapbox-gl/maps/android/build.gradle
. You also need to add"eas-post-install": "patch-package"
to your package.json so that expo will run patch-package while building. I also patched mavenCentral() into the react-native-mapbox-gl build.gradle but I’m not 100% sure if that’s actually part of what fixed it.