1919386 - Fenix Nightly not sending crash reports

Status: RESOLVED INVALID

(Firefox for Android :: Crash Reporting, defect, P1)

Description

[Ryan VanderMeulen [:RyanVM]]

I noticed today that we're not seeing any new crash report submissions in Socorro from the currently-available Fenix Nightly build in Google Play (the first once to ship since the new crash reporter was disabled due to the high volume of old reports being submitted). I'm not sure if this is a regression caused by bug 1918750 or a newly-introduced regression in the old crash reporter caused by the new reporter's landing which only got exposed once the new one was disabled. Accordingly to discussion with Jeff, Sentry is also showing this regression.

Comment 1

[Matt Tighe [:matt-tighe]]

We're seeing Socorro crashes from the build id that is the latest release according to GPS. Where are you looking and not seeing them?

Comment 2

[Ryan VanderMeulen [:RyanVM]]

I was looking at https://crash-stats.mozilla.org/topcrashers/?product=Fenix&version=132.0a1&days=3&process_type=any&_range_type=build. But given slow Google Play review times lately, this might just be due to a lack of many newer builds at the moment.

Given your findings, maybe we just need to wait for more newer builds to get through review so we can hopefully get more clear of the submission volume from last week's builds.

Comment 3

[Jeff Boek [:boek]]

We tested submitting crashes to both Sentry and Socorro locally in a debug build and the code paths are still working.

It looks like we may have hit our quota in Sentry as well with the large amount of extra crashes that was sent on Nightly which may explain why we're seeing a dip in reports over the last couple of days. Will continue to keep an eye on this.

Comment 4

[Ryan VanderMeulen [:RyanVM]]

Looks like we're getting reports just fine from the current release. Closing this out as a false alarm.