Status Update
No update yet.
Comments
iv...@google.com
Thank you for the post. We are currently looking into this issue internally.
iv...@google.com
After looking into this further, DeadSystemException does not seem to be coming from the Maps SDK itself. We've checked out other issues with this error and we can see that this is an OS related issue. Another thing to note is that we haven't heard from any other customers with regards to this exception.
So please make sure that you follow our
Then please provide the steps to reproduce it so that we can check on our end. Thank you for your understanding.
tr...@gmail.com
Thank you for your investigation. We have looked at the documentation, but it seems there's a contradiction. We are using a MapView in lite mode in the ViewHolder of a RecyclerView. There is even a sample application for this.
public static synchronized int initialize (Context context)
If you are using MapFragment or MapView and have already obtained a (non-null) GoogleMap by calling getMapAsync() on either of these classes, then it is not necessary to call this.
If you are using MapFragment or MapView and have already obtained a (non-null) GoogleMap by calling getMapAsync() on either of these classes and waiting for the onMapReady(GoogleMap map) callback, then you do not need to worry about this class. See the sample application for some examples.
The IDE context pop-up for MapsInitializer.initialize has an even stricter wording:
Do not use this method if you obtain a valid GoogleMap reference using the onMapReady(GoogleMap map) callback. Instead provide the callback to either MapFragment#getMapAsync() or MapView#getMapAsync(). For examples, see the sample application.
But the MapsInitializer.initialize() in the callback:
@Override
public void onMapReady(GoogleMap googleMap) {
MapsInitializer.initialize(getApplicationContext());
map = googleMap;
setMapLocation();
}
Could you please clarify why MapsInitializer.initialize() is called in the callback, since the docs seem to indicate that that's not necessary?
iv...@google.com
It seems that your additional queries are now unrelated to the initial issue DeadSystemException. Can you please confirm?
If so, can you please file a separate issue for us to separate your concerns? Or I would suggest that you file a support case so that we can assist you better/in a timely manner if you have any more queries. Since the Issue Tracker does not have SLO. Thank you!
Please see:
tr...@gmail.com
For anyone who comes across this thread, the response from Google Cloud support was that the example app code is incorrect:
Upon investigation of the code, it seems that this example from the documentation is using a redundant/ deprecated method. Like you mentioned and the documentation states, you shouldn't use this initialization again if you have already got a valid reference to GoogleMap through the onMapReady() callback.
As a next steps, we recommend using the information from our documentation for optimal results. As this line of code could be redundant in the example.
Our solution was to remove usage of the Google Map API for certain older Android versions. This issue can be closed as far as we are concerned.
Description
Since April 24, we see a sudden and significant amount of crashes related to the Google Maps API. The number of crashes keep increasing daily, across various device brands and Android versions, so it looks like a Google flipped a switch and is rolling out something.
com.google.android.gms:play-services-maps:18.1.0LATEST12451000, this is common across all crashesWe determine the GooglePlay API version like so:
Crash log