Closed Bug 1226242 Opened 9 years ago Closed 5 years ago

Investigate missing crash-stats reports

Categories

(Firefox for iOS :: General, defect)

All
iOS
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: aaronmt, Unassigned)

References

Details

Stephan hooked Breakpad into Fennec for iOS, and Ted is our Breakpad expert, adding both of them here.

Stephan, any idea what's up there? Is Breakpad not working right in our iOS builds?
Flags: needinfo?(sleroux)
Is it possible that reports are simply not being processed or shown? Is there any raw data for submitted reports on crash-stats Kairo?
So I think I see what the issue is here. Now that I have a crash I can reproduce on the App Store build I can see what's going on.

1. When the App Store app crashes, the 'Send Crash' prompt is never shown to the user. Since crash reporting is off by default, there's a very good chance no one has manually turned it on in the settings page which is why we're not seeing any crashes in the app.

2. After turning on crash reporting manually, I was able to crash the app and verify a request was sent to the crash-stats server. It created a new crash as expected: https://crash-stats.mozilla.com/report/index/a76c7635-7aad-4b30-9fc2-389f12151119. However, when I do a query for all crashes in FenneciOS that are marked with the 'release' release channel, nothing shows up.
(In reply to Aaron Train [:aaronmt] from comment #2)
> Is it possible that reports are simply not being processed or shown?

No, the search shows all submitted crashes that we could process (the only issue could be a systemic corruption of the data that makes the processor fall over, but I would have heard about that from the Socorro team, I think).

(In reply to Stephan Leroux [:sleroux] from comment #3)
> 1. When the App Store app crashes, the 'Send Crash' prompt is never shown to
> the user. Since crash reporting is off by default, there's a very good
> chance no one has manually turned it on in the settings page which is why
> we're not seeing any crashes in the app.

Why is it off by default? Sending crashes is on by default on all our other products (with a prompt on every crash for desktop/Android*, and on the first crash for FxOS).

*subject to change based on discussions going on right now
I know before we had to make it opt-in because we didn't have prompt when a crash occurred but now that we have the prompt I feel like that can change to being opt-out.
Flags: needinfo?(sleroux)
(In reply to Stephan Leroux [:sleroux] from comment #5)
> I know before we had to make it opt-in because we didn't have prompt when a
> crash occurred but now that we have the prompt I feel like that can change
> to being opt-out.

That would be great, would match our other products.
Just to add some more detail, the report crash dialog is showing but only in cases where there are tabs open with history. Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1226389 to track a fix for that.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.