Hi all,
Posting here at the recommendation of Mozilla Support, who reviewed my case three times and indicated that the AMO team would be the right point of contact for further help.
Background:
I’m an individual hobby developer. I published a Firefox extension on AMO in 2020 that has an active user base. 2FA on my Mozilla account was set up on an iPhone I no longer have, and I don’t have the recovery codes or AMO upload API credentials.
Why this matters now:
The extension applies hardcoded styling for several major sites. Those sites have updated their markup, so the extension is currently broken for users on those sites. The fix is ready and committed - I just can’t sign in to upload it. Recent 1-star reviews reflect this. Every additional week of delay damages the listing’s standing and disappoints users who otherwise have no idea what’s happening.
What I’ve already done:
- Filed a Mozilla Support ticket and been through three rounds of correspondence over the past few days.
- Provided the original “Two-step authentication enabled” confirmation email that Firefox Accounts sent to my account in 2021, forwarded as a .eml so the original DKIM signature, exact timestamp, IP address, and device fields are intact and verifiable against the Firefox Accounts security event log.
- Offered listing-internal data (registered support email, full description text I wrote, release notes, original review correspondence Mozilla sent me, screenshot details).
- Offered to produce a byte-identical reconstruction of any published .xpi version from my local source tree, and to walk through the source repository live with anyone from the AMO team.
What I’m asking:
- Is there a path for AMO staff to review developer-side evidence (specifically the kind that requires access to internal AMO listing records and Firefox Accounts security logs)?
- If so, what’s the right way to flag a case like this for that review?
- If anyone from the AMO team sees this and is willing to take a look, my Mozilla Support ticket has the full evidence already attached. Happy to share the ticket number privately.
Not posting the account email, ticket number, or sensitive specifics in this thread. Will share with AMO staff directly through any channel they prefer.
Thanks for reading.