Open Bug 1869319 Opened 6 months ago Updated 6 months ago

Update Fxa Error handling

Categories

(Fenix :: Accounts and Sync, enhancement)

All
Android
enhancement

Tracking

(Not tracked)

People

(Reporter: bdk, Unassigned)

References

Details

There's been a few crashers in recent releases when application-services added a new FxA exception:

Fxa errors are usually handled by handleFxaExceptions, which uses shouldPropagate to determine its behavior and shouldPropagate defaults to re-throwing the exceptions.

My feeling is that shouldPropagate() should default to not throwing the exceptions. Maybe it should report an error to Sentry instead. I don't know much about the original intent of that code though.

Severity: -- → S3
See Also: → 1869134
You need to log in before you can comment on or make changes to this bug.