Created attachment 8601500 [details] Gif showing the issue Affected builds: - Latest Nightly Affected OS`s: - Windows 7 64-bit - Ubuntu 14.04 32-bit - Mac OS X 10.9.5 STR: 1. Start Firefox 2. Click Hello icon 3. Click Sign In or Sign Up 4. Create an account 5. Verify the account from the selected mail provider Expected results: Successfully logged in FxA and a call can be made. Actual results: Did not logged in to FxA and Notes: 1. Strange thing is that If I verify the account in another browser, hello works just fine and I`m logged in to FxA. 2. I used guerrillamail and yahoo mail service, with the same result. 2. This is a regression: m-c: Last good revision: 2015-04-23 - 0b202671c9e2 First bad revision: 2015-04-24 - 22a157f7feb7 Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0b202671c9e2&tochange=22a157f7feb7 m-i: Last good revision: 8ed771ecfecd First bad revision: 27a61b918d5b Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=8ed771ecfecd&tochange=27a61b918d5b Probable cause: Bug 1153788 - Obtain encryption keys from FxA for Loop
Thanks for catching this Bogdan. This seems related, but not the same as bug 1159520. After verification, there's a message on the console that the keys haven't been obtained for Loop and so sign-in fails. Signing in again gives the keys, and all is well. This kinda reflects what we're seeing elsewhere, that if the user hasn't provided the password, then we don't have the keys. However, this also seems a slightly failing in the FxA flow. I suspect this is going to be an issue for FxA to fix, though I could be wrong. Moving to the FxA component for the first part of the discussion at least. Ryan, any ideas here?
Component: Client → FxAccounts
Flags: needinfo?(standard8) → needinfo?(rfkelly)
Product: Loop → Core
> I suspect this is going to be an issue for FxA to fix Yes, I believe this is most likely to be a bug on our side.
FxA server-side bug filed at https://github.com/mozilla/fxa-content-server/issues/2384
This should be fixed by https://github.com/mozilla/fxa-content-server/commit/fd2fc72d3af8abaa7acff61f026c166fc306d3c3 which will be deployed as part of FxA train-37 next week. Sorry for the delay in getting this fixed, it turned out to depend on quite a few subtle details of our authentication process.
The FxA fix has been deployed to production, you should now be able to make a call directly after sign-up.
Bogdan, would you mind retesting now?
(In reply to Mark Banner (:standard8) from comment #6) > Bogdan, would you mind retesting now? Sorry for the late reply. Seems to work fine using latest Nightly across platforms. Marking this as fixed.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.