firebase crash reporting caused an ANR on launch during initialization

[xcvr]

This bug manifested yesterday after Google Play Services was updated.

The repro was simply to add firebase as a dependency in our build process, and it caused a critical ANR on all devices running version 9.6.80 of google play services during firebase's crash reporting's initialization. It appears to be a deadlock.

The version of firebase we are using is 9.2.0.

As a side note, this stackoverflow post seems related: http://stackoverflow.com/questions/39480257/firebase-crash-produces-anr-during-launch

[lu...@pixelized.studio]

Hi there,

I currently have the exact same issue when implementing a BroadcastReceiver (BOOT_COMPLETED) on my Nexus 5X - 7.0 - Play services 9.6.80 - Firebase 9.4.0.

Could not figure out why this specific device could not handle the intent... Had to go through my commits...

Thanks!

[Frank van Puffelen]

Thanks for the report. We're investigating what may have caused this regression. 

A workaround (posted here on StackOverflow) may be to temporarily disable Firebase Crash Reporting.

We'll post here when there is an update or a proper fix. 

     puf

[Shinki Hong]

Fyi, this happens only for Lollipop or higher. Kitkat has no problem. 

[xcvr]

We have it repro'd solidly on 4.2.2. It's only tied to the google play services version on the device.

[Doug Stevenson]

You can track this issue here: https://status.firebase.google.com/incident/Crash%20Reporting%20%28Beta%29/16003

[xcvr]

This is kind of a rant, but maybe it'll help you realize the importance of the most basic "does it load" test for next time.

You had our whole company panicked, and everyone wound up working late. We have millions of users, and they blame us for your mistake. Our team pulled together and got a fix out for all of our apps in less than 36 hours after your software shipped, but we got lots of negative reviews and support requests in the meantime.

Furthermore, it kinda sucks that the google play services version can be swapped out from under us after we ship.

Stuff happens though. Thanks for hopefully fixing it relatively quickly, and listening to this small rant.

[Kato Richardson]

Kato here, thanks so much for the feedback. We love hearing from developers, especially your criticisms. Feedback like yours has been a big part of shaping Firebase over the years.  Do me a favor and please reach out to me directly with your project name and some details, and I'll see if we can do anything to help out here.

To make this perfectly clear, nobody monitoring this mailing list (i.e. the Firebase community) manages Google Play versions, testing, or release schedules. However, we do have a dependency on their service, so that doesn't excuse away our responsibility to review this failure and to do what we can to make sure it doesn't happen again.

It does mean that the rant isn't necessarily reaching the people with the most influence over that product. I'll do my best to forward this on and make sure they feel your pain here. 

☼, Kato

P.S. If it's not offensive to your culture or beliefs, I'd encourage you to introduce yourself! We are a close-knit family. It's easier to keep that culture strong when we remember that there are real people on the other end of our emails. Getting to know one another by name is a great first step.

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/49ab27d1-ceba-4cd0-ae11-734982b2fb83%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398