Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Maps SDK is crashing

issuetracker.google.com

Post reply on HN
Print view View original

21–28 of 28 posts

Re: Google Maps SDK is crashing

#21

Post by tmpz22 »

x86_64Ubuntu wrote: post #19
AdamJacobMuller wrote: post #12

Earlier quoted context omitted.

And even worse it doesn't crash in realtime. It crashes parsing locally cached data caused by a bad update, meaning this possibly can't be quickly fixed merely by fixing the API.

Imagine writing a test for that. Just to replicate it repeatedly. Would they be able to use a phone emulator and point it to the old api to cache data, and then go to the new api to replicate the failure?

That actually doesn't sound that hard, it's very similar to writing e2e tests over Selenium (except in this case instead of talking to chrome you're talking to the android emulator).

Re: Google Maps SDK is crashing

#22

Post by stefan_ »

tersers wrote: post #20
whalesalad wrote: post #18

Reminder to think of your application as a system composed of many sub-systems, where any sub-system can fail at any time. Plan for this, engineer for this.

To an extent due diligence is required of any library, but there must always be some guarantees for the benefit of the developer. It's unreasonable to expect a developer to accommodate for the failure of any SDK call.

Sure, but if your business is broken because of a 3rd party library, I'd sooner be looking at patching the bytecode than to write breathless "me too but we are very important" in the bug tracker.

Re: Google Maps SDK is crashing

#23

Post by microcolonel »

stefan_ wrote: post #22
tersers wrote: post #20

Earlier quoted context omitted.

To an extent due diligence is required of any library, but there must always be some guarantees for the benefit of the developer. It's unreasonable to expect a developer to accommodate for the failure of any SDK call.

Sure, but if your business is broken because of a 3rd party library, I'd sooner be looking at patching the bytecode than to write breathless "me too but we are very important" in the bug tracker.

> patching the bytecode

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.

Re: Google Maps SDK is crashing

#24

Post by interestica »

Aha. I just loaded up the Samsung Health app for the first time in forever and it would crash everytime it tried to grab location for a tracked run. I tried rolling back and and reinstalling and presumed it was an app bug. Ended up uninstalling because there wasn't much info to investigate.

Reluctantly installed Strava and they mentioned an ongoing issue with Google maps - but it seemed to display and record fine.

Re: Google Maps SDK is crashing

#26

Post by whalesalad »

tersers wrote: post #20
whalesalad wrote: post #18

Reminder to think of your application as a system composed of many sub-systems, where any sub-system can fail at any time. Plan for this, engineer for this.

To an extent due diligence is required of any library, but there must always be some guarantees for the benefit of the developer. It's unreasonable to expect a developer to accommodate for the failure of any SDK call.

> It's unreasonable to expect a developer to accommodate for the failure of any SDK call.

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.

Re: Google Maps SDK is crashing

#27

Post by jfim »

whalesalad wrote: post #26
tersers wrote: post #20

Earlier quoted context omitted.

To an extent due diligence is required of any library, but there must always be some guarantees for the benefit of the developer. It's unreasonable to expect a developer to accommodate for the failure of any SDK call.

> It's unreasonable to expect a developer to accommodate for the failure of any SDK call. 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…

Multiple comments are commenting that even with a try/catch, the error still crashes the app.

From https://issuetracker.google.com/issues/154855417#comment39

> 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.

From https://issuetracker.google.com/issues/154855417#comment86

> instead of crashing the app even though try/catch is used and this cryptic message cited above.

Re: Google Maps SDK is crashing

#28

Post by noitsnot »

anaphor wrote: post #15

Looks like you have to hit "Clear Storage" on Android in order to get it working again (tested it with Uber). That is, not the cache, but the actual application data. I.e. this will require users to wipe any data being locally stored and log back in again. This is pretty bad. Edit: Google has confirmed this is the case https://issuetracker.google.com/issues/154855417#comment181 but apparently the data will be invalid…

Yep. I tried clearing cache on Redfin but it does open after clearing app data.
Post reply on HN