Signing in to sync containers causes account to become unverified
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 685
- Forks
- 237
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 136
Description
Description
On a fresh install of Firefox, after I enable syncing with Containers, my previously signed in account now has 'unverified' and asks me to re-verify it.
Steps to reproduce
- Fresh install of Firefox on Windows
- Sign in with Firefox account (including 2FA)
- View Settings page and there is no warning about account being unverified
- Click on Containers icon in toolbar
- Sign in again to enable Container syncing (including 2FA)
- Containers are now syncing, but Firefox reports on Settings page that account is unverified
Expected result
Signing into Container sync should not cause account to change to unverified
Actual result
Need to click on Verify Account to re-verify the account again!
Environment
Windows 11, Firefox 137.0.2 (64-bit)
┆Issue is synchronized with this Jira Task
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported flow on a fresh Firefox install on Windows 11: sign in with 2FA, then sign in again through the Containers toolbar icon and inspect the Settings page. Use the linked Jira task FXA-11565 for additional context; done means enabling Container sync no longer changes a previously verified account to unverified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100