Closed Bug 1747621 Opened 4 years ago Closed 4 years ago

Can't sign in successfully after entering password, Google authentication code is "Invalid"

Categories

(Cloud Services :: Server: Firefox Accounts, defect)

Firefox 95
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Allessio77, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:95.0) Gecko/20100101 Firefox/95.0
Firefox for Android

Steps to reproduce:

Signing into Firefox.accounts on my PC is always unsuccessful.

Actual results:

After I enter may password, the next screen asks for authentication code. I get it from google and type it in, but it is rejected by FF as "Invalid"

Expected results:

I should have been taken to my FF account page.

The Bugbug bot thinks this bug should belong to the 'Cloud Services::Server: Firefox Accounts' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Server: Firefox Accounts
Product: Firefox → Cloud Services

Thanks for filing an issue. It's possible for your authentication codes to get out of sync if the time on your device is different from our servers. According to our records it looks like you were last able to login on 2021-12-26, is that correct?

I was not successful logging in on that date...I tried but the auth app had no code for me.
Yesterday, I opened another Firefox account under another email and managed to sync my phone.
I don't actually know what I have lost by abandoning my original account, but I am happy this new one works. I did not set up the two step authentication on my new account.

If there is some way to combine the two accounts, I would be interested in knowing.

Sorry for the inconvenience. Unfortunately we don't have a way to combine accounts at this time. If you've logged in to the new account on one of your devices that you've previously used all of that will be synced and nothing should be lost.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.