-
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
(Android) - App crashes when clicking on Map's "Update" button to update Google Services #618
Comments
I also have this problem |
Me as well Android - Samsung Galaxy S4 - API 19 (Physical Device) |
+1. When device dont have the Google Services installed and you press on "Update" or any part of map view, app crash At the moment i "fix" it, checking the Android play services with Google singing component:
And if catch is called, i dont show the maps in app. |
Me as well react-native-maps: 0.12.2 Update |
We are getting this issue too - The map not working isn't a huge issue if Google Play Services needs updating, but having the whole app crash is an issue. If it helps, I have a crash report: |
MapView must be inflated from an actual "Activity" context so that the Intent called by the "Update" button will know where to start. Just a guess but, AirMapView.java takes an appContext that uses .getCurrentActivity() which may not be resolving to an activity? |
Exactly the same error as @mitchward . |
This seems to be triggered when user touched the blank area around the "Update" button. |
I created a PR to fix this issue, any comments are welcome. |
As the title states, running on a device with an old version of Google Services (for instance I am running a phone with Google Play services 8703470 while RN-maps requires 9452000), the Map correctly shows an "Update" button, but clicking on it results in a crash.
Relevant log's lines:
android.util.AndroidRuntimeException: Calling startActivity() from outside of an Activity context requires the FLAG_ACTIVITY_NEW_TASK flag. Is this really what you want?
RN@0.33 , RN-maps@0.8.2, tested on Android M and Android 5
The text was updated successfully, but these errors were encountered: