Closed Bug 1288252 Opened 9 years ago Closed 9 years ago

additional Addons account created while trying to merge Addons and Firefox accounts with different email addresses

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: ruben, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160629102529 Steps to reproduce: Have Firefox account with one email and Addons https://addons.mozilla.org/ with another. Logging into Addons prompts to merge with an existing Firefox account or create a new one ("Add-ons is switching to Firefox Accounts for login. Sign in now to transfer your account."). When no Firefox account exists for the email address of the Addons account, the prompt to create a new one or sign into an existing account ("Create a Firefox Account to continue to Add-ons. Have an account with a different email? Sign in!"). I chose to sign in with an existing email. Actual results: I was created a new Addons account for the email of my Firefox account. I hoped setting my user name to the same as that of my Addons account would rectify it, but it didn't. Expected results: It should have merged the Addons and Firefox accounts, probably changing the Addons account to the email address of the Firefox account.
According to the design of the AMO FxA migration at [1], what's supposed to happen here is that your AMO account is moved over to match the email address on your FxA account. :andym, has this user run into a bug in the migration process? [1] https://github.com/mozilla/addons/pull/9#discussion_r45803604
Flags: needinfo?(amckay)
This appears to have regressed. I have filed https://github.com/mozilla/addons-server/issues/3151 to work on it.
Flags: needinfo?(amckay)
Thanks Mark, I'll close out this bug in favour of the one in github.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.