-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: EAS Build fails for iOS and Android on expo 49 #212
Comments
I just ran into the same error. Couldn't find anything. |
@cspeer do you mean update eas-cli? what version you are using? And is your method solved iOS error or android? |
Sorry, yes I meant eas-cli, the latest version is 5.9.1, which I updated to:
It fixed both, iOS & Android. |
@cspeer No, didn't fix the issue for me.. |
I just had the same issue :
I tried :
Working on Android but not iOS. |
@DengpaoHuai Hello, can you share versions of expo, expo-notifications and possibly @notifee/react-native or other related to notifications packages please? |
Hi, we just got the same problem. It turns out we needed to put "onesignal-expo-plugin" plugin as the first element of the plugins array. https://github.com/OneSignal/onesignal-expo-plugin/tree/main?tab=readme-ov-file#plugin |
@Gandalf-pro unfortunately didn't work in my case.. |
Hi, I got : eas-cli : eas-cli/5.9.1 win32-x64 node-v16.16.0 The custom build work. I also tried to put "onesignal-expo-plugin" plugin as the first element. |
@DengpaoHuai I am not able to reproduce the build failure on iOS did you let eas create distribution certificates and provisioning profiles for both the main app and extension targets? |
the same is happening for me, but with node 20.0.0 and expo 50. @emawby I created the identifier & provisioning profile for the onesignal service |
@ddwebdevv were you able to fix the issue? I got the exact same error, and I have notifee installed as well. |
Having the same problem right now trying to build with eas on iOS, after transferring apple app to another account. |
Same issue here |
same issue for me: [RUN_GRADLEW] FAILURE: Build failed with an exception.
[RUN_GRADLEW] * What went wrong:
[RUN_GRADLEW] Execution failed for task ':app:checkDebugDuplicateClasses'.
[RUN_GRADLEW] > Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
[RUN_GRADLEW] > Failed to transform jackson-core-2.16.1.jar (com.fasterxml.jackson.core:jackson-core:2.16.1) to match at.
[RUN_GRADLEW] > Execution failed for JetifyTransform: /Users/brunogarcia/.gradle/caches/modules-2/files-2.1/com.faste.
[RUN_GRADLEW] > Failed to transform '/Users/brunogarcia/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.c)
[RUN_GRADLEW] Suggestions:
[RUN_GRADLEW] - Check out existing issues at https://issuetracker.google.com/issues?q=componentid:460323&s=modi.
[RUN_GRADLEW] - If this issue has not been filed, please report it at https://issuetracker.google.com/issues/ne.
[RUN_GRADLEW] * Try:
[RUN_GRADLEW] > Run with --stacktrace option to get the stack trace.
[RUN_GRADLEW] > Run with --info or --debug option to get more log output.
[RUN_GRADLEW] > Run with --scan to get full insights.
[RUN_GRADLEW] * Get more help at https://help.gradle.org
[RUN_GRADLEW] BUILD FAILED in 38s
[RUN_GRADLEW] Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.
Build failed
Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.
npx exited with non-zero code: 1 |
We're seeing the same thing. We're on Expo SDK 51:
|
This is now resolved in the latest version. Cheers |
@rgomezp Still not working with expo 51. |
What happened?
EAS Build failing for both platforms after adding Onesignal in my project.
Steps to reproduce?
What did you expect to happen?
Expected to build will be successful.
Seems like similar issues were found before but no clear solution
like for example:
#71
OneSignal Expo SDK version
expo 49.0.0
Platform
No response
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: