[IPProtection] Delay onboarding vpn card until fxa is ready
Categories
(Firefox for Android :: Privacy, defect)
Tracking
()
People
(Reporter: mavduevskiy, Assigned: mavduevskiy)
References
(Depends on 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [fxdroid] [group2])
Attachments
(3 files, 3 obsolete files)
There is a race condition between IPProtectionOnboardingPrompt and FxaAccountManager on start: the prompt might be shown while the account manager is still being initialized, so that by the time a user finishes auth flow, the toolkit code is never informed about an existing user, and won't be able to connect automatically.
We used to get stuck in connecting state - that was fixed in 2054812, but ideally we would minimize the amount of users that could would get an error & retry after finishing auth.
| Assignee | ||
Updated•1 month ago
|
| Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
| Assignee | ||
Comment 1•1 month ago
|
||
| Assignee | ||
Comment 2•1 month ago
|
||
Updated•1 month ago
|
| Assignee | ||
Comment 3•1 month ago
|
||
Adding NoAccount state for the onboarding to distinguish between fxa
manager initializing and having no account at the app start.
Updated•1 month ago
|
| Assignee | ||
Updated•1 month ago
|
| Assignee | ||
Comment 4•1 month ago
|
||
Comment 5•1 month ago
|
||
Set release status flags based on info from the regressing bug 2050967
Updated•1 month ago
|
Updated•1 month ago
|
Backed out for causing fenix failures
Backout link
Push with failures
Failure log(s)
Comment 10•1 month ago
|
||
Adding NoAccount state for the onboarding to distinguish between fxa
manager initializing and having no account at the app start.
Original Revision: https://phabricator.services.mozilla.com/D313887
Updated•1 month ago
|
Updated•29 days ago
|
Updated•29 days ago
|
Comment 11•29 days ago
|
||
| uplift | ||
Comment 12•28 days ago
|
||
| bacckout uplift | ||
Updated•28 days ago
|
Comment 13•28 days ago
|
||
Comment on attachment 9624396 [details]
Bug 2057032 - Make vpn onboarding wait past WarmingUp
Backed out for android failures
Comment 14•28 days ago
|
||
Adding NoAccount state for the onboarding to distinguish between fxa
manager initializing and having no account at the app start.
Original Revision: https://phabricator.services.mozilla.com/D313887
Updated•28 days ago
|
Updated•28 days ago
|
Updated•28 days ago
|
Updated•28 days ago
|
Comment 15•28 days ago
|
||
| uplift | ||
Updated•28 days ago
|
Fix verified in Fx Nightly 155.0a1 (Build #2016178394) and Fx Beta 154.0b10 (Build #2016178218) using a Google Pixel 7a (Android 16). The race condition seems to be fixed.
Updated•6 days ago
|
Description
•