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.
Posted Apr 23, 2020 - 15:29 PDT
The Android app is now starting to behave better. We are seeing reduced numbers of Android crashes across the board. Please have your drivers clear app data in the settings and relaunch to hopefully restore a fully operational state. We will continue to monitor things closely.
Posted Apr 23, 2020 - 15:25 PDT
Updated links for this issue within Google's issue tracker:
We have received no updates from Google yet but are continuing to monitor any and all communication channels with them. It looks like many global apps that initialize the Google Maps SDK (Uber, Lyft, Airbnb) on some or all mobile operating systems are currently experiencing the same crashing behavior. Unfortunately, the only readily available fix is for Google to resolve this on their end. Thank you for your patience.
Posted Apr 23, 2020 - 14:07 PDT
Google enterprise phone support has confirmed that they are all hands on deck at this time attempting to resolve this global outage affecting thousands of their customers.
Posted Apr 23, 2020 - 13:31 PDT
For iOS users, we have established that it's the map view that triggers the crash. We highly recommend that drivers do not load it while Google works to resolve this issue so that the app can be used normally. Unfortunately, we have not yet found a similar temporary solution for Android users.
Posted Apr 23, 2020 - 13:25 PDT
We are waiting for any news from Google and looking for potential ways to avoid map initialization to see if the app can be used without crashing. Unfortunately, this is a very serious global issue on Google's part that may be hard for us to make stop via a hotfix but we are working on any and all options.
It appears that Google has messed something up on their end which is resulting in crashes for both our Android and iOS driver apps. We are quickly working on a hotfix however this does appear to be a global issue. We currently have a critical priority ticket open with their enterprise support team.