You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Late last week Google pushed an update to a file used by the Maps SDK in all Android and iOS apps that caused widespread crashes. The issue is here: https://issuetracker.google.com/issues/154855417
If a user opened an app while this bad file was live, they are stuck in a crash loop. If the user didn't open the app while the bad file was live, they should be ok.
Google is working a release for Google Play Services to fix, but in the mean-time they are suggesting all developers push out a workaround update to their apps 🙄.
Summary:
Late last week Google pushed an update to a file used by the Maps SDK in all Android and iOS apps that caused widespread crashes. The issue is here:
https://issuetracker.google.com/issues/154855417
If a user opened an app while this bad file was live, they are stuck in a crash loop. If the user didn't open the app while the bad file was live, they should be ok.
Google is working a release for Google Play Services to fix, but in the mean-time they are suggesting all developers push out a workaround update to their apps 🙄.
Here's the latest advice:
https://issuetracker.google.com/issues/154855417#comment457
We can tell each user to manually do this:
Or we can push the following code fix:
In
Application.onCreate()
:Steps to reproduce:
Start the app while the bad Google Play Services file was live, and keep trying to restart the app
Expected behavior:
Not crash
Observed behavior:
App is in a crash loop if opened when bad file was live
Device and Android version:
All
The text was updated successfully, but these errors were encountered: