Really happy to see crashes finally getting reported properly through Xcode now. I think a combination of the issues with Testflight and lack of users were causing us problems before but looks like it's good now. The more I see Testflight working the more I question our Breakpad/crash-stats integration. There seems to be some issues with it reporting correctly still. There's currently a bunch of crashes showing up in Xcode but nothing is showing up on crash-stats [1]. Also, using Breakpad is more unconventional on iOS than other crash reporting options (such as PLCrashReporter). The only product I know that is using it is Chrome and documentation around iOS support is sketchy at best. The advantages I see using crash-stats/Breakpad is the ability to control the data we send and make use of the rich data analysis we get through crash-stats. Also, if we plan on releases not through Testflight, we woudn't get the iTunes crash reports.
[1] https://crash-stats.mozilla.com/search/?product=FenneciOS&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature On Fri, Nov 13, 2015 at 8:55 AM, Stefan Arentz <[email protected]> wrote: > We have always complained that it is so difficult to get crash reports on > iOS via Apple's reporter. To make them show up in the Xcode crash > organizer. This is mostly due to the low volume of testers and installs we > used to have. > > Those days are over :-) > > Now that we have done the global launch, we have about 2 dozen reports > within 24 hours of usage. This is great. We can now deal with these reports > much more quickly. > > I would like to propose that we start doing periodic triage of these > crashes. How about we turn the ones we think are relevant into Bugzilla > bugs? I know Aaron has been doing this for a bunch of crashes, but I think > we should make it part of a steady routine. > > Every crash comes with a signature, so I think we should simply file them > with that as the bug summary. And then if you right click on a report in > Xcode, you can open the actual crash report bundle and copy the crash meta > data and crash info into the bug. The meta data is important because it > shows if the crash is a top-crasher and on what platforms it is happening > together with some more useful data. So lets not lose that info. > > This is something we can probably automate with a little bit of Python > eventually. > > S. > > > _______________________________________________ > mobile-firefox-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/mobile-firefox-dev > >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
