> "Hi William, We have identified an issue stemming from an outage with Google Maps that is causing the Whistle app to immediately crash upon opening. Our team is aware of the issue and monitoring the situation closely. While there is no estimated time for resolution from Google, rest assured that the safety of Bella is still our top priority. Please keep Bella close for the time being. [...]"
Edit: Google has confirmed this is the case https://issuetracker.google.com/issues/154855417#comment181 but apparently the data will be invalidated within a few hours.
Reluctantly installed Strava and they mentioned an ongoing issue with Google maps - but it seemed to display and record fine.
This is not even remotely close to unreasonable. In fact, it is the opposite. Doordash, Uber, Lyft etc. are completely dead on arrival due to a remote bug that could have easily been protected against.
During SDK initialization, if shit hits the fan, pull the chute and inform the user that things cannot proceed. Easy as pie. If you do not have that level of control or the foresight/wisdom to implement, well yep you are going to be the victim of a situation like this. And if you are the mobile lead at any of the aforementioned companies I can guarantee your head is gonna be on a stick by 5pm.
> This happens even with a MapView.onCreate call for me, even when encased in a try / catch error. So beyond the fact that Google Maps isn't working, the Google Maps library isn't handling the error throwing properly and is bypassing the app's ability to catch errors.
> instead of crashing the app even though try/catch is used and this cryptic message cited above.
Tell that to the developers who barely grasp that the JVM exists.
But yeah, the degree of helplessness people engineer themselves into without a second thought is absurd. I guess it's a blessing that the Play Store isn't embedding the Maps SDK and crashing before it can update the Maps SDK heheh.