Open Bug 1792913 Opened 3 years ago Updated 3 years ago

Remove unique identifiers from Sentry reports

Categories

(Firefox for Android :: Crash Reporting, task, P3)

All
Android
task

Tracking

()

People

(Reporter: csadilek, Unassigned)

References

Details

From github: https://github.com/mozilla-mobile/android-components/issues/6577.

Sentry is not very good at understanding that the following reports are really all the same:

IllegalStateException
androidx.fragment.app.Fragment in setOnStartEnterTransitionListener
Trying to set a replacement startPostponedEnterTransition on HomeFragment{2b916fc} (66d6e8b1-e1dd-4a10-b54d-f03f7003a312) id=0x7f090170}
IllegalStateException
androidx.fragment.app.Fragment in setOnStartEnterTransitionListener
Trying to set a replacement startPostponedEnterTransition on HomeFragment{55af279} (b5a85f9a-a118-45cf-9314-620f1801bbe9) id=0x7f090170}

It groups exceptions with a similar type and message pretty well, but when UUIDs or pointer addresses are in the message, that process fails and results in a very large number of reports that we need to group manually.

This ticket is to run an experiment where we try to write a preSubmit Sentry hook that blanks out UUIDs and Pointer addresses. I think a simply regular expression can probably catch those pretty easily.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Severity: -- → N/A
Type: defect → task
Priority: -- → P3
Flags: needinfo?(cpeterson)
See Also: → 1792914
You need to log in before you can comment on or make changes to this bug.