User is not able to sign in into Firefox sync account with a verified account
Categories
(Cloud Services :: Server: Firefox Accounts, defect)
Tracking
(firefox67.0.1+ fixed)
People
(Reporter: ailea, Unassigned)
References
Details
Attachments
(5 files)
Affected versions
Tested on Release 67.0.1
Affected platforms
Tested on Mac OS 10.14 and Ubuntu 18.04
Prerequisites:
To be able to see the about:welcome page on a version where this is not implemented please go to about:config and set:
identity.fxaccounts.autoconfig.uri to https://accounts.stage.mozaws.net
browser.newtabpage.activity-stream.fxaccounts.endpoint to https://accounts.stage.mozaws.net
Restart the browser.
Steps:
- Go the about:welcome page
- Log in into your firefox sync account (click to the FxA Avatar icon from the Toolbar --> Turn on Sync). Please enter an address that is already verified.
- Click on Continue
Expected result
User is taken to the "Sign in" page
Actual result
User is taken to "Create a Firefox Account" page
Comment 1•6 years ago
|
||
Can you provide more information? I just signed in with a verified account.
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
Reporter | ||
Comment 4•6 years ago
|
||
(In reply to Shane Tomlinson [:stomlinson] from comment #1)
Can you provide more information? I just signed in with a verified account.
Have you tried on Release build 67.0.1 or on Nightly build? Because on Nightly the issue is not reproducible, only on Release 67.0.1 the problem occurs.
Comment 5•6 years ago
|
||
(In reply to Alin Ilea from comment #4)
(In reply to Shane Tomlinson [:stomlinson] from comment #1)
Can you provide more information? I just signed in with a verified account.
Have you tried on Release build 67.0.1 or on Nightly build? Because on Nightly the issue is not reproducible, only on Release 67.0.1 the problem occurs.
I'm using a treeherder release from here: https://treeherder.mozilla.org/#/jobs?repo=mozilla-release&searchStr=build-signing&selectedJob=248698342
Updated•6 years ago
|
Comment 6•6 years ago
|
||
We are using this: https://treeherder.mozilla.org/#/jobs?repo=mozilla-release&searchStr=build-signing&selectedJob=248871687
Comment 7•6 years ago
|
||
(In reply to ovidiu boca[:Ovidiu] from comment #6)
We are using this: https://treeherder.mozilla.org/#/jobs?repo=mozilla-release&searchStr=build-signing&selectedJob=248871687
I still don't have any issues as long as about:config prefs are reset back to the expected values.
Comment 8•6 years ago
|
||
Comment 9•6 years ago
|
||
This is the result in my case.
Comment 10•6 years ago
|
||
From looking at the video above, the behavior seems correct to me. If I query the backend for whether "mozillatest1234@yahoo.com" is registered, the response says the user does not exist. From that respect, the UI is behaving as intended for a new user.
Is "mozillatest1234@yahoo.com" an address that was registered with either prod (accounts.firefox.com) or latest (latest.dev.lcip.org)? They all have distinct user databases.
Reporter | ||
Comment 11•6 years ago
|
||
I've tested again with a new account and the issue is not reproducible, so the problem was related to the account.
I will close this bug as Resolved-Invalid.
Comment 12•6 years ago
•
|
||
I'm reopening this bug as I'm able to reproduce it.
The steps are
- Go the about:welcome page
- Use an email address that is already verified.
- Click on Continue
Expected result
User is taken to the "Sign in" page to enter their password.
Actual result
Page to sign in does not load completely and it gets stuck loading. (See attached gif for reference)
Comment 14•6 years ago
|
||
This has the same root cause as Bug #1553758, closing as a dup.
Comment 15•6 years ago
|
||
I'd like us to verify this as well as bug 1553758, though, once it's fixed.
Updated•6 years ago
|
Comment 16•6 years ago
|
||
From discussion in bug 1553758 and in triage it sounds like the STR should be followed differently (ie, this bug is a result of the test not being set up quite right).
Reporter | ||
Comment 17•6 years ago
•
|
||
Hi,
I've retested the issue with new steps from: https://bugzilla.mozilla.org/show_bug.cgi?id=1553758#c19 and it works, following that steps the issue is not reproducible.
Note that it works also if the user restart the browser after disconnect the account without doing the prerequisites again, just restart the browser and log in again.
Description
•