Closed
Bug 1601180
Opened 5 years ago
Closed 4 years ago
UITour's `fxa` configuration request fails if the fxa account is in a bad state.
Categories
(Firefox :: Tours, defect, P1)
Firefox
Tours
Tracking
()
RESOLVED
FIXED
Firefox 73
Tracking | Status | |
---|---|---|
firefox73 | --- | fixed |
People
(Reporter: markh, Assigned: markh)
References
Details
Attachments
(1 file)
If a user is signed in to FxA, but is unverified or in a "needs authentication" state (eg, when their account password was changed on another device), we will fail to report any information when the FxA configuration (added by bug 1548404) is requested.
We will fail to populate everything in that case, but should still populate what we can. We should probably also try and report the user is in that state (although it's not clear what consumers will do in that scenario, but they might as well know)
Updated•4 years ago
|
Priority: -- → P1
Assignee | ||
Comment 1•4 years ago
|
||
Pushed by mhammond@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/776c7e62ea26 have UITour's FxA configuration info report account state and handle that it might not be OK. r=MattN
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox73:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 73
You need to log in
before you can comment on or make changes to this bug.
Description
•