Closed Bug 1891253 Opened 11 months ago Closed 10 months ago

[Menu Redesign] Display the correct state in the Mozilla account button

Categories

(Fenix :: Toolbar, task, P3)

All
Android
task

Tracking

(firefox127 fixed)

RESOLVED FIXED
127 Branch
Tracking Status
firefox127 --- fixed

People

(Reporter: gl, Assigned: gl, NeedInfo)

References

(Regressed 1 open bug)

Details

(Whiteboard: [fxdroid])

Attachments

(3 files)

Followup to https://phabricator.services.mozilla.com/D207053#7108155, where we need to add some form of AccountState inside of our SyncStore which is currently missing and as a result we are not properly able to display the state where we need to reauthenticate the account.

Note, I believe that only AccountUiView is displaying the correct sync states in a button at the moment compare to BrowserMenuSIgnIn

The task here is to do the following:

  • Add an AccountState to the SyncState that is managed by SyncStore
  • Observe the new AccountState from the SyncStore in the menu dialog in order to provide the correct properties to MozillaAccountButton.
  • Implement the correct navigation to the appropriate fragments given the AccountState. This should follow AccountUiView.
Flags: qe-verify-
Blocks: 1891360
Severity: -- → S3
Pushed by gluong@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1a4ab46225c0 Part 1: Add AccountState to SyncStore r=android-reviewers,matt-tighe https://hg.mozilla.org/integration/autoland/rev/d80c214825c1 Part 2: Observe the AccountState from the SyncStore in the menu dialog r=android-reviewers,matt-tighe https://hg.mozilla.org/integration/autoland/rev/2f0f2cbeef3f Part 3: Implement navigation to the Mozilla account screens from the Mozilla account menu button r=android-reviewers,matt-tighe
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 127 Branch
No longer blocks: menu-redesign

Hi :gl! I wonder if this patch stack could be causing the assertion in bug 1908838, and the recent spike in Sentry errors from bug 1909779?

Specifically, I'm wondering if calling authenticatedAccount.getProfile()? inside FxaAccountObserver.onReady() causes getProfile() to update the account state and log the user out as a side effect, then notify AccountAbnormalities.onLoggedOut() before AccountAbnormalities.onReady() has had a chance to run. Could that explain what's happening here?

Regressions: 1908838, 1909779
Flags: needinfo?(gl)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: