Page MenuHomePhabricator

[EPIC] Improve crash diagnostics
Closed, DeclinedPublic

Description

In our iOS 4.1 post mortem, we identified poor diagnostics as an obstacle which prevented us from reproducing crashes, and as a result, verifying fixes.

Expected results

Will it increase our velocity?

This could potentially increase our velocity, in that crashes/bugs will be easier to fix if we have better diagnostics included with reports.

Will it reduce risk?

If these reports allow us to reproduce crashes and verify fixes, then yes.

Will it improve user happiness?

If it leads to fewer crashes, yes.

Event Timeline

BGerstle-WMF raised the priority of this task from to Needs Triage.
BGerstle-WMF updated the task description. (Show Details)
BGerstle-WMF subscribed.

@BGerstle-WMF any of this need to be salvaged for 5.0. Otherwise lets close this ticket.

MBinder_WMF set Security to None.

@MBinder_WMF @JMinor TL;DR; Yes, but low/normal prio. Having better diagnostics (TBD) could be very helpful in the event of unforeseen crashes.


IMO this is still a problem as it was never ended up improving diagnostics. I'm reluctant to add more scope to 5.0, but seeing this ticket again makes me wonder if we should include this as, at minimum, a nice to have for 5.0. Having these kinds of diagnostics could be life-saving if things get ugly, and we've continued to encounter crashes which we haven't been able to reproduce.

That said, this ticket needs is more definition as to what diagnostics would've allowed us to reproduce crashes & confirm fixes. Some suggestions of things to log at time of crash (with user's permission):

  • Device language
  • Search site
  • Last 5 articles in history
  • Free memory
  • Free disk space
JMinor raised the priority of this task from Lowest to Low.Feb 9 2016, 10:41 PM
JMinor edited projects, added iOS-app-v5.0.1-Kiwi; removed iOS-app-v5-production.