-
Notifications
You must be signed in to change notification settings - Fork 1.3k
App menu shows "Sign in to sync" menu item until I tap it, even though I'm already signed in to sync #25486
Comments
While investigating this I noticed that in the current implementation of This behavior is fixed in the contributor's PR, however the menu dismissing is something we may not want to add. actual.mp4contributor.mp4Since the authentication state takes some time to be updated and notify the observers about it, the There are several solutions we can apply to avoid this: One would be to avoid displaying the menu for those few seconds, another would be to add another state ("Authentication in progress..") until we get an update from the account manager. solution1.mp4Tagging UX to check with which of these solution we want to go with, or keeping the current behavior. |
Confirmed this has been fixed in Nightly. Closing |
I'm still experiencing this bug in Firefox Nightly 110.a1 (Build #201592213). The STR are the same as originally reported with the added step of disabling network before launching Fenix in step 3 (i.e., I experience this problem most frequently when I have poor network access). |
@rocketsroger This bug is still reproducible in Nightly 110.a1. |
Was able to find a quick fix, now need time to make sure it doesn't break anything. Implementations of The issue looks rather simple. The menu items are build upon the screen opening, but the account manager at that point doesn't have the actual state. It takes just a few millisecond for it to get updated usually, but we never update the items in the list. (with the exception of account error, but I have yet to verify that it works for authentication errors). |
The long term solution is caching the profile. A-S will provide us with the API to always get a cached profile (ticket), then we have to support it on the A-C and fenix side. |
mozilla-releng/staging-firefox-android@fa23088
This issue is no longer reproducible with the latest Nightly 111.0a1 (2023-01-26) build. |
Steps to reproduce
Maybe I am experiencing #24112? But I don't think my account is in a bad authentication state.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: