-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Android] Duplicate class com.google.android.play.core.common after upgrade from 2.0.4 to 2.2.4 #26
Comments
+1 |
@ofavre Issue seems to be created by line 71 here: https://github.com/wonderpush/wonderpush-android-sdk/blob/master/sdk/build.gradle
This makes all the react-native app rating libraries unusable together with react-native-wonderpush because of duplicate class errors. If you are aware of any possible workaround please advise. Any suggestion will be greatly appreciated. Doubled the bounty here: https://stackoverflow.com/questions/74692599/react-native-store-review-duplicate-class-com-google-android-play-core-common |
To fix the issue we had to make a PR in the library (react-native-inapp-review) that had conflicts with react-native-wonderpush dependencies. More info at the stackoverflow link I added in my previous comment. |
I have the exact same problem, is it possible to fix it directly in react-native-wonderpush instead of having to fork another lib? ---- EDIT Fix it by upgrading "react-native-store-review" to "^0.4.3". Maybe this could be added in the documentation as troubleshooting. |
It seems that
react-native-wonderpush
is usingcom.google.android.play.core
version 2.0.0 and top 2 react-native libraries used for app review/rating use older versions of that module. Tried both react-native-store-review and react-native-in-app-review latest versions.Is there any workaround to avoid such conflicts for react-native-wonderpush 2.2.x?
Added a stackoverflow question here:
https://stackoverflow.com/questions/74692599/react-native-store-review-duplicate-class-com-google-android-play-core-common
I will attach a bounty to it this evening.
Any response that could help in finding a workaround will be greatly appreciated.
The text was updated successfully, but these errors were encountered: