Closed Bug 1865792 Opened 7 months ago Closed 7 months ago

Crash in [@ mozilla.appservices.fxaclient.FxaException$OriginMismatch: at mozilla.appservices.fxaclient.FfiConverterTypeFxaError.read(fxa_client.kt)]

Categories

(Fenix :: Accounts and Sync, defect)

Unspecified
Android
defect

Tracking

(firefox120 unaffected, firefox121 fixed, firefox122 fixed)

RESOLVED FIXED
122 Branch
Tracking Status
firefox120 --- unaffected
firefox121 --- fixed
firefox122 --- fixed

People

(Reporter: gsvelto, Assigned: bdk)

Details

(Keywords: crash, topcrash)

Crash Data

Attachments

(2 files)

Crash report: https://crash-stats.mozilla.org/report/index/5d6ae641-6c2a-4cd3-9d49-24c0f0231120

This appears to be a regression, it started in nightly with buildid 20231117214639.

The bug is linked to a topcrash signature, which matches the following criterion:

  • Top 10 AArch64 and ARM crashes on nightly

For more information, please visit BugBot documentation.

Keywords: topcrash

Ben, does FxaException$NoExistingAuthFlow exception https://crash-stats.mozilla.org/report/index/9926eab7-85d2-462f-a279-46fcd0231121 have the same root cause as this FxaException$OriginMismatch bug? Or should I file a new bug report for it?

[@ mozilla.appservices.fxaclient.FxaException$NoExistingAuthFlow: at mozilla.appservices.fxaclient.FfiConverterTypeFxaError.read(fxa_client.kt) ]

Assignee: nobody → bdeankawamura
Flags: needinfo?(bdeankawamura)

Yes and no.

The OriginMismatch crash happened because I added a new FxA error type. NoExistingAuthFlow has been around for a while, I don't think any recent change should have caused it.

That said, I think the fix is the same, we should remove that error type from the shouldPropagate list. Mike: does that make sense to you? If so, I can update the existing PR. If not, let's create a new bug and fix them in separate PRs.

Flags: needinfo?(bdeankawamura)
Flags: needinfo?(mavduevskiy)
Status: NEW → RESOLVED
Closed: 7 months ago
Flags: qe-verify+
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch

Comment on attachment 9365268 [details] [review]
[mozilla-mobile/firefox-android] Bug 1865792 - FxA OriginMismatch exceptions (backport #4552) (#4582)

Beta/Release Uplift Approval Request

  • User impact if declined: OriginMismatch exceptions from A-S layer with crash the app (they are not panic and they shouldn't)
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): the patch puts a recently added to A-S type of exception into not-to-be-propagated bucket of exceptions from A-S
  • String changes made/needed:
  • Is Android affected?: Yes
Flags: needinfo?(mavduevskiy)
Attachment #9365268 - Flags: approval-mozilla-beta?

Since there are no steps to follow to reproduce this issue, I'll just remove the qe-verify+ flag.

Flags: qe-verify+
Comment on attachment 9365268 [details] [review]
[mozilla-mobile/firefox-android] Bug 1865792 - FxA OriginMismatch exceptions (backport #4552) (#4582)

Approved for Android 121.0b3
Attachment #9365268 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Flags: qe-verify+

Thanks for fixing this one. I made https://bugzilla.mozilla.org/show_bug.cgi?id=1866799 for NoExistingAuthFlow

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: