Summary
Google is experiencing a crash with Google Maps SDK beginning around Thursday, 2020-04-23 12:57 US/Pacific. This is impacting lots of Android applications - Uber, Lyft, DoorDash, Instacart, WeatherBug, etc and Digital Fleet. https://issuetracker.google.com/issues/154855417 .
As of Wednesday, 2020-04-29 16:09 US/Pacific Google has marked this issue as resolved.
Suggested Resolution (updated 4/30/2020)
Google has published an update to all devices with Google Play Service version 17.4.55 and newer to fix the ongoing Google Maps crash. This update should fix the crash without further action from you. If you continue to see Google Maps crash in the DigiTrack application, an update to a new verison of DigiTrack is required.
Latest Updates
Update from Google:
4/29/2020 06:02 PM CST
Update from Google:
Description: On April 23 2020 starting at 11:30 PDT, Google served for 4 hours an update to the configuration of a Maps mobile component, triggering crashes in Maps SDKs for Android and iOS. Applications on devices that downloaded this version of the configuration (during the outage period) were vulnerable to the crash. Workaround solutions are offered for Maps SDKs for Android and iOS.
The updates to Google Play Services to fix the crash has been published to all devices with Google Play Services version 17.4.55 and newer. There is no change to the version number of Google Play Services on the device after the update is installed. No action is required from developers or end users to receive the updated Maps module.
4/29/2020 01:48 AM CST
Update from Google:
Description: # Android
The updates to Google Play Services to fix the crash is now available to all devices with Google Play Services version 17.4.55 and newer. End users' devices need to download and apply the updates. There will be no change to the version number of Google Play Services on the device after the update is installed. We continue to see crash rates of Android Maps SDK v2, which is included in Google Play Services, decrease significantly.
If your app uses Android Maps SDK v2 and you have not updated your app with the client-side code workarounds mentioned below, please monitor your app's crash rate. If the crash rate does not decrease, we recommend you to apply the workarounds and update your app. If your app uses Android Maps SDK v2 and you have already updated your app with the workarounds, no further action is required. The Google Play Services update will not have bad effects on your app.
4/28/2020 02:05 AM CST
Update from Google:
Description: # Android
We have pushed the updates to the Google Play Services on Android to a larger scale, and continue to monitor how the roll-out is progressing.
We still highly recommend developers to roll out their own client-side code workarounds via an update to their apps.
4/27/2020 1:56 PM CST
Update from Google:
Description: News since last update: We started rolling out updated versions of the Google Play Services on Android, at this stage at a small scale. We are monitoring how the roll-out is progressing throughout the day and plan to target a larger scale roll-out this evening PT based on our findings. We are continuing to monitor this tracker for updates from the community and will share more details about the progress of the roll-out according to the next update time communicated below (sooner if there are significant updates to be shared in the interim).
In the meantime, we still highly recommend developers to roll out their own client-side code workarounds via an update to their apps.
4/27/2020 6:18 AM CST
Update from Google:
What’s New since last update: Nothing. Work on this incident is still ongoing, but we have nothing new to share at the moment.
We will provide the next update by Monday, 2020-04-27 08:00 US/Pacific
The backend service that caused this crash has been hot-fixed on 2020-04-23 15:00 PT, and we have seen a significant decrease in crashes since then.
The remaining crashes are due to client-side caching, which is why we recommend the workarounds mentioned below.
For Android: We are expediting a new release of the Google Play Services (that contains the Maps SDK runtime) which will fix this issue client-side. Our initial 48 hours estimate for rolling out this fix was overly optimistic, and we are currently reassessing the release timeline. Currently the best course of action is for developers to roll out their own client-side workarounds via an update to their apps.
4/25/2020 10:00 AM CST
Update from Google:
Please note that we are shifting to longer intervals between updates and will provide the next update by Sunday, 2020-04-26 18:00 US/Pacific.
The backend service that caused this crash has been hot-fixed on 2020-04-23 15:00 PT, and we have seen a significant decrease in crashes since then.
The remaining crashes are due to client-side caching, which is why we recommend the workarounds mentioned.
For Android: We are expediting a new release of the Google Play Services (that contains the Maps SDK runtime) which will fix this issue client-side. Our initial 48 hours estimate for rolling out this fix was overly optimistic, and we are currently reassessing the release timeline. Currently the best course of action is for developers to roll out their own client-side workarounds via an update to their apps.
4/24/2020 9:39 PM CST
Update from Google:
Description: Here's an update focusing on the code mitigations for iOS and Android. The Android mitigation is an elaboration of the mitigation already published.
Please note that we are shifting to longer intervals between updates and will provide the next update by Saturday, 2020-04-25 17:00 US/Pacific.
4/24/2020 7:17 PM CST
Update from Google:
The backend service that caused this crash has been hot-fixed on 2020-04-23 15:00 PT, and we have seen a significant decrease in crashes since then.
The remaining crashes are due to client-side caching, which is why we recommend the workarounds mentioned.
For Android: We are expediting a new release of the Google Play Services (that contains the Maps SDK runtime) which will fix this issue client-side. Our initial 48 hours estimate for rolling out this fix was overly optimistic, and we are currently reassessing the release timeline.
We are also aware of customer reports where clearing the application data or uninstalling and reinstalling the application has not fixed the issue, and we are continuing to investigate the issue.
We will provide another update here by Friday, 2020-04-24 21:00 US/Pacific.
4/24/2020 2:41 PM CST
Update from Google:
The backend service that caused this crash has been hot-fixed on 2020-04-23 15:00 PT, and we have seen a significant decrease in crashes since then.
The remaining crashes are due to client-side caching, which is why we recommend the workarounds mentioned.
For Android users, although we are still expediting a new release of the Google Play Services (that contains the Maps SDK runtime) that will also fix this issue client-side, it appears our initial 48 hour estimate for rolling out the fix was overly optimistic. We are currently reassessing the release timeline.
We are also aware of a few customer reports where clearing the application data or uninstalling and reinstalling the application has not fixed the issue, and we are continuing to investigate the issue.
Thank you to everyone for your continued patience. We will provide another update here by Friday, 2020-04-24 16:00 US/Pacific.
4/24/2020 10:57 AM CST
Update from Google:
Description: Here's an update on the current mitigation and resolution steps:
The backend service that caused this crash has been hot-fixed on 2020-04-23 15:00 PT (17 hours ago), and we have seen a significant decrease in crashes since then.
The remaining crashes are due to client-side caching, which is why we recommend the workarounds mentioned.
For Android users, although we are still expediting a new release of the Google Play Services (that contains the Maps SDK runtime) that will also fix this issue client-side, it appears our initial 48 hour estimate for rolling out the fix was overly optimistic. We are currently reassessing the release timeline.
Thank you to everyone for your continued patience. We will provide another update here by Friday, 2020-04-24 11:00 US/Pacific.
4/24/2020 9:00 AM CST
Working with customers to discuss their options. Summary below.
Yesterday afternoon our monitoring of DigiTrack saw a spike in application crashes. Google Maps was identified to be the issue and we reached out to Google Maps to create a support ticket immediately. Google confirmed an issue with Google Maps. Their underlying SDK is the issue and this is breaking lots of Android applications - Uber, Lyft, DoorDash, Instacart, WeatherBug and Digital Fleet...this list goes on and on.
To stop the Digital Fleet application from crashing, yesterday afternoon we disabled Google Maps in your application so your drivers currently do not have access to the map inside DigiTrack or turn by turn directions.
You have 2 options for resolution:
- Wait for Google to fix Google Maps
- Here is the official issue with updates from Google.
- Here is the latest update from Google:
- For Android users, we are currently expediting a new release of the Google Play Services (that contains the Maps SDK runtime) that will also fix this issue client-side. The previous ETA of 48 hours as communicated previously still applies.
- Thank you to everyone for your continued patience. We will provide another update here by Friday, 2020-04-24 08:00 US/Pacific.
- Update your vehicles to a fix version of the Digital Fleet application.
- The engineering team has been working overnight to develop new versions of our application that resolve the Google Maps crash and we have those available for you to download now. We just need to coordinate that roll out with you.
4/24/2020 6:09 AM CST
Update from Google:
Description: Here's an update on the current mitigation and resolution steps:
- The backend service that caused this crash has been hot-fixed on 2020-04-23 15:00 PT (13 hours ago), and crashes have steadily reduced since. Remaining crashes are due to client-side caching, which is why we recommend the workarounds mentioned.
- For Android users, we are currently working on a release of the Google Play Services (that contains the Maps SDK runtime) that will also fix this issue client-side.
The previous ETA of 48 hours as communicated previously still applies. Thank you to everyone for your continued patience. We will provide another update here by Friday, 2020-04-24 06:00 US/Pacific. (~ 2 hours from now)
4/24/2020 2:34 AM CST
Update from Google:
Description: Based on additional investigations, it appears the remaining crashes might be due to some race condition, where the updated data doesn't get fetched early enough, leading to a crash loop.
We are working with highest priority on a new fix, but current ETA for deployment is around 48 hours.
We will provide an update by Friday, 2020-04-24 02:15 US/Pacific with the latest details.
4/24/2020 12:50 AM CST
Plan B in place...if Google has not resolved, we have patch versions of the app available
4/23/2020 11:15 PM CST
Began working on Plan B to have patch versions of Digi.Track ready in the morning
4/23/2020 11:13 PM CST
Update from Google:
Description: We believe the root cause of the crashes of Google Maps SDK has been fixed. The fix is being propagated to the affected applications and it is continuing toward resolution at the expected pace.
Please note that even after full resolution, the first launch of an application might still trigger a crash. However, all following launches should start working as expected.
As for Maps SDK for Android, full resolution is expected to complete by Thursday, 2020-04-23 22:45 PDT.
4/23/2020 9:58 PM CST
Update from Google:
Description: We believe the root cause of the crashes of Google Maps SDK has been fixed. The fix is being propagated to the affected applications and it is continuing toward resolution at the expected pace.
As for Maps SDK for Android, full resolution is expected to complete by Thursday, 2020-04-23 22:45 PDT.
4/23/2020 6:19 PM CST
Update from Google:
We believe the crashes of Google Maps SDK are partially resolved. Full resolution is expected to complete by Thursday, 2020-04-23 19:45 US/Pacific.
We will provide an update by Thursday, 2020-04-23 16:53 US/Pacific with current details.
4/23/2020 5:21 PM CST
Update from Google:
Mitigation work is currently underway by our engineering team; roll-out of a potential fix is in-progress. We will provide more information by Thursday, 2020-04-23 16:30 US/Pacific.
4/23/2020 4:12 PM CST
We disabled Google Maps in Digi.Track and put up a web banner to inform all users:
"Google Maps is currently experiencing a widespread issue affecting many applications. Google Maps has been temporarily disabled in the DigiTrack application until Google has resolved the issue."
4/23/2020 2:51 PM CST
Internal monitoring showing Google SDK issues and Digi.Track app crashes. Issue reported to Google Maps, support ticket created.
Comments
0 comments
Please sign in to leave a comment.