Android - Fabric Crash, Unable to destroy activity
We could wait this issue out till 2.14, cuz its happening in a class (MyCoursesListActivity) that we'll be getting rid of in 2.14 release.
Also, after we send out the 2.13 release, this issue should stop happening on prod as the culprit class in this issue is only used in the old dashboard. Having said that, after 2.13 is sent out, lets keep a close eye on it and monitor if it gets resolved or we face a similar issue in another class related to new tabs based dashboard.
Related to activities (and maybe glide?) this would be worth another wave of triage and grooming in the coming weeks. , . Thanks! (Now the second biggest android crash cause by the looks of it -.08% of users)
This isn't the most common crash, and has been around since August /16. I wouldn't slow down any release for this, but it should be reviewed in the next couple sprints.
Is this still the most common crash? This should be a CAT-1 if it is.
This impacts .13% of android users (the single most common cause of crashes) could we do a quick triage or would this take a deeper review?