It would be nice if you could give answer to all developers individually (me included) who are waiting for extension approval and then give some explanation we could give back to our customers.
Fine ! My extension new version have been approved. Ty for my customers
The problem I have here is that I know there are bugs in version of my extension which is currently approved and distributed on AMO. These bugs, while not critical, are potentially very annoying and they are are fixed in the version of my extension that I submitted on July 8th, then re-submitted on August 8th. Most of my users haven’t hit these bugs yet, but some have(2 that I know of), and they’ve got in touch with me about it and all I can tell them is “Sorry, I’ve been stuck in AMO review for 2 months, nobody’s telling me anything about my situation, and there doesn’t seem to be anything I can do to help you. The only thing I know is that this seems to be happening to like, everybody” What am I supposed to do here? All I care about is fixing bugs and I can’t do that without Mozilla signing a redistributable plugin.
Hello Mozilla are you there???
@caitlin Given that the review backup seems to be persisting and that many folks are asking about it, do you think Mozilla might be able to give an update on the blog or something? I think answers - even unpleasant ones - might help with folks that are on edge now. It’s a bit tough when something unknown and out of our control is causing weeks-long delays. And as always, thank you for responding to developers here.
@zephyr hear hear. This is exactly my point, and the point I tried to raise in Matrix too. We’re all sitting around thinking of all the reasons that this review slowdown might be occurring and every reason I personally can think of sounds dire.
Hi @zephyr, unfortunately we don’t have a lot more we can share at the moment. However, I’ll talk to the team and see if there are any updates for next week.
Hi @caitlin.
unfortunately we don’t have a lot more we can share at the moment
Nothing has been shared so far. We still don’t know why this has happened, and what we can do to avoid it happening in the future. If you can’t answer these questions then please get someone who can to login and contribute to this post.
Mentioned in ublock release notes: https://github.com/gorhill/uBlock/releases/tag/1.38.0
No stable release will occur until dev build is no longer stalled
Apparently a certificate / signing problem at mozilla at the moment.
Maybe related: Could not update an old nightly build. Had to download and reinstall and only then received updates again.
Are you kidding me? uBlock Origin. They couldn’t find the time to approve and let Raymond release uBlock. Maybe the most valuable extension in any existing browser ecosystem. The only extensions that clearly deserves to be considered “recommended” to every single Firefox user. uBlock Origin.
I shouldn’t be surprised. I had to go to Matrix and beg. Outrageous.
Hello. For me it’s been 8 versions and 3 months, and still no progress.
Come on, Mozilla! This issue must be dealt with ASAP.
ive been awaiting a review of my unlisted extension since 9th september, what is going on? no official communication from Mozilla whatsoever.
Is mozilla about to go down the tubes into bankruptcy?
@caitlin this is what I’m talking about, people are getting scared. If I woke up tomorrow and addons.mozilla.org was completely shut down I would be heartbroken but totally unsurprised.
In the absence of any information or communication from Mozilla, I’m just going to continue to release normally until whatever is going on is resolved. Could someone at least update the text of the email, though? It’s pretty insensitive to keep telling people it’s going to be “a few hours” or a “couple of days” when it obviously won’t be.
- 9/26/21
Hello, Thank you for submitting your add-on I2P In Private Browsing 0.113 to addons.mozilla.org. Your submission is taking longer than usual to be reviewed and signed. This process could take a few extra hours and up to a couple of days.
- 10/1/21
Thank you for submitting your add-on I2P In Private Browsing 0.115 to addons.mozilla.org. Your submission is taking longer than usual to be reviewed and signed. This process could take a few extra hours and up to a couple of days.
- 10/4/21
Thank you for submitting your add-on I2P In Private Browsing 0.117 to addons.mozilla.org. Your submission is taking longer than usual to be reviewed and signed. This process could take a few extra hours and up to a couple of days.
Seriously, it’s squandering the (remaining)trust people have in Mozilla to mislead people in this way. Just say it’s going to be 2 months so people can adjust.
i wonder if the problems are related to manifest v3
Possibly. It could also be those jokers that are spamming extensions that pin specific websites or add shortcuts deliberately clogging up review queues in order to escalate to harmful behavior during an update, or a talent shortage, or a problem with the signing certificate itself or any number of completely nightmarish scenarios. No meaningful or honest communication on why has occurred from Mozilla yet.
Edit: Oh good they updated it to say 3-4 weeks. They’ve successfully communicated honestly once.
Edit: “It could also be those jokers that are spamming extensions that pin specific websites or add shortcuts.” - * Add-ons that serve the sole purpose of promoting, installing, loading or launching another website, application or add-on are no longer permitted to be listed on addons.mozilla.org . Add-ons Policy Changes 2021 I think I guessed part of this right. More importantly, they’re talking about it now.