-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Not compatible with react-native-push-notification #831
Comments
I am facing the same issue. I have used react-native oneSignal instead. The app stops on real device in android without a stack trace. It works on ios simulator though. will try on ios device as well. |
I have the same issue with onesignal and react-native-maps. It runs on iOS perfectly. Edit: Ok after some analyzing, it seems it's a version mismatch of google play services between the two. I edited node_modules/react-native-maps/android/build.gradle and changed the dependencies:
|
Thanks man. You save my life! 🍻 |
@getconcar your suggestion fixed my issue #874 🙌 Do you have any idea why adding those dependencies fixed my issue? |
@getconcar suggestion works but I'm get another error when load a view with a MapView:
And if I try to reload app throws another error:
Have 2 conflict packages: react-native-onesignal and react-native-admob. |
I just had this same issue last night after updating Android studio. Is there a way do fix this without editing code in |
@MobiusHorizons in android/app/build.gradle try this:
and below this
|
@lucianomlima - thanks for this! But can you explain why we need this in the first place? RN maps is coming with a build.gradle file and there we have this:
I checked on my machine and I do have 9.8.0, so I would think that the build process would take those? But i ran in in the
error. |
@compojoom The problem is that other packages may compile other versions of Google Play Services. |
@lucianomlima - aah, I see. I scanned my nodes_modules for com.google.android.gsm and found that react-native-device-info is adding compile 'com.google.android.gms:play-servies-gcm:+' I don't know what the gcm is for , but the + should mean latest version. So most probably it includes 10.2.0 - RN maps is hardcoded to 9.8.0 and then we run into this issue. Wouldn't it be best if RN maps also compiles with + instead of hardcoded version? |
@compojoom GCM is Google Cloud Messaging, used for push notifications. |
Add troubleshooting information for common error with Google Play services error react-native-maps#831 (comment)
I added this info to the installation.md I hope that this make the installation a little easier on new users. |
Issue still persist after trying the above .Here is my configuration |
@linux08 same problem with maps and notifications, plz did you find any solution?? |
Hi @SarahYT Yea i was able to fix it,I created a repo containing how i integrated the packages. Check and see if it works for you |
Hi, my project is use react-native-push-notification and react-native-maps. Previously my project already configured to use react-native-push-notification, and it's work. But when I try insert react-native-maps, I got an error. I have guess something is wrong with my configuration. So I have do some experiment.
First, I fork your repo, and I can run your Example project in my android. But when I try to add react-native-push-notification on your Example project, I got same error.
EDIT:
I also create fork for testing https://github.com/pewh/react-native-maps and let's see Example folder :)
The text was updated successfully, but these errors were encountered: