Closed Bug 2057032 Opened 1 month ago Closed 1 month ago

[IPProtection] Delay onboarding vpn card until fxa is ready

Categories

(Firefox for Android :: Privacy, defect)

All
Android
defect

Tracking

()

VERIFIED FIXED
155 Branch
Tracking Status
firefox153 --- wontfix
firefox154 --- verified
firefox155 --- verified

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: nobody → mavduevskiy
Whiteboard: [fxdroid] [group2]
Attachment #9614668 - Attachment description: WIP: Bug 2057032 - Part 2: Refactor extra account statue enum into WarmingUp → WIP: Bug 2057032 - Part 2: Refactor extra account status enum into WarmingUp

Adding NoAccount state for the onboarding to distinguish between fxa
manager initializing and having no account at the app start.

Attachment #9615403 - Attachment description: WIP: Bug 2057032 - Make vpn onboarding wait past WarmingUp → Bug 2057032 - Make vpn onboarding wait past WarmingUp
Severity: -- → S3
Type: task → defect
Keywords: regression
Regressed by: 2050967
Attached video verification_new1.mp4

Set release status flags based on info from the regressing bug 2050967

Blocks: 2058646
Attachment #9614668 - Attachment is obsolete: true
Attachment #9614667 - Attachment is obsolete: true

Backed out for causing fenix failures
Backout link
Push with failures
Failure log(s)

Flags: needinfo?(mavduevskiy)
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 155 Branch
Regressions: 2060973

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

Attachment #9624396 - Flags: approval-mozilla-beta?
See Also: → 2061841
See Also: → 2061846
Attachment #9624396 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

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

Attachment #9624575 - Flags: approval-mozilla-beta?
Attachment #9624575 - Attachment is obsolete: true
Attachment #9624575 - Flags: approval-mozilla-beta?
Flags: needinfo?(mavduevskiy)
Attachment #9624396 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

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.

  • video - signed in to Sync with a FxA that signed in to VPN before
  • video - signed in to Sync with a FxA that didn't signed in to VPN before
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: