AMO review pending since Dec 17 - no response for over a month

Hi Mozilla / AMO Support team,

I’m posting here as a last resort because we haven’t been able to get any response through the normal AMO channels.

The oldest pending update for our Firefox extension (Ambire Web3 Wallet – Get this Extension for 🦊 Firefox (en-US)) was submitted for review on Dec 17. As of today, it has been pending for over a month with no reviewer feedback, no rejection, and no request for changes - just silence.

For context, over the same period we have shipped 6 major versions via the Chrome Web Store without delays of more than a day. We understand AMO reviews can take time, but a >1 month wait for a routine update (with no communication) is creating real product and support impact for us.

We’re not trying to be difficult - we just need some signal on status. A month-long delay with no reply is close to unacceptable for maintaining a production extension.

Thanks in advance for any clarification or escalation help.

4 Likes

We had a similar experience, submitted on December 17, but was rejected January 13 without any review at all. Our extension requires the reviewer to log into an account in order to use it, but our auth logs showed that no one had ever even logged into the account. The reviewer couldn’t have possibly known what our addon even does beyond what we wrote in the description.

Honestly a shocking experience.

1 Like

@sottaku you should receive a rejection reason in the email, but also visible on the web in the “Status and versions” section:

Also, I think reviewers are mainly looking at the source code.
They don’t have time to actually “test” the addons and make cloud accounts :upside_down_face: .


@superkalo it may sound like a month :smiley: , but it was Christmas, so it’s like minus 2 weeks of holiday, maybe more. I’m not saying it’s OK, but it’s understandable.

It’s a price for having addons store more secure.

PS: I’m now also awaiting review, but it’s been only 6 days so far :slight_smile:

Oh and I’m not sure you know, but you can submit new version even if old one didn’t finished review yet (unlike in Chrome store). And this does not reset your review queue position. The reviewer will simply review the latest submission.
Sometimes I submit several “hotfixes” while I’m awaiting review.

They provided the reason “clone or fork” – that they wouldnt host multiple addons with the same functionality. But there isn’t any addon that has the same functionality. And like I said, they would have no way of knowing whether or not our addons functionality was the same as any other addon, because they never used it!

We already made the account for them, all they had to do was login with the credentials we provided.

i did not know this, is this information documented somewhere officially?

Review processes are not very documented, probably also for security reasons.

I know it only from this comment:

1 Like

thanks! thats good to know!

@juraj.masiar It’s now been almost two months. We can’t ship a single Firefox update in almost two months.

Yes, I know I can submit new version even if the old one didn’t finished review yet. I submitted 12 separate builds for review in the last two months. None of them have progressed at all.

If this is what’s meant by “the price of security”, something is seriously off.

If they call these absurd delays “the price of security”, I think they got it all wrong. Stopping updates entirely is not protection. It’s a liability.

1 Like

I regret not making a home for that information in the official docs when I was still part of the add-ons team :neutral_face:

@dotproto Hi Simeon, could you review my add-on here:
“regex-tab-router”
by user: User Profile for urmish – Add-ons for Firefox (en-US)

@urmish, unfortunately I cannot. I used to work on the Add-ons team, but now I’m just a community member that helps moderate this forum.