-
Notifications
You must be signed in to change notification settings - Fork 374
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]: Dependency problem while adding onesignal to an existing react native project #1710
Comments
@Yash-Goyal007 I believe this is a bug the google-services Gradle plugin. Can you try updating it to the latest version? |
I tried updating google services gradle plugin but still the same error persists. |
@Yash-Goyal007 could you share a project reproducing the build issue? |
Closing due to no response. @Yash-Goyal007 if this is still an issue for you please let us know! |
Thank you for your support, I fixed it by upgrading gradle version and updating all related packages and plugins. |
What happened?
I'm integrating OneSignal into my React Native application, but I'm encountering a Firebase dependency conflict error when trying to make a debug build. My React Native version is 0.62.3, Gradle version is 5.5, Google Services version is 4.3.3, and the conflicting Firebase version is 23.4.1. I'm also using "@react-native-firebase/app": "^16.5.0" and "@react-native-firebase/crashlytics": "^16.5.0" as app dependencies. I've tried removing all Firebase-dependent code and running OneSignal, but the dependency conflict error persists.
PS: I have added my build.gradle file config
build.gradle.txt
Steps to reproduce?
What did you expect to happen?
I expected the app to work normally after adding one signal sdk and send push notifications through one signal sdk.
React Native OneSignal SDK version
5.2.0
Which platform(s) are affected?
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: