My addon is being poorly reviewed

Add-ons addons.mozilla.org
1

Every time I try to publish my addon, it gets a random refuse, with no details but things that doesnt makes sense. If I reply the refuse e-mail, I don’t get any answers. How can I interact with the reviewer? It doesnt make sense for me to keep creating new versions just to reply.

2

Reviewers are not exactly eager to discuss the rules…
But if you write some of those issues here, we may be able to help.

1 Like
3

Hey Juraj, one example is that I got:

  • Sources, specifically Testing information required: Please provide us with detailed information on how to test this add-on. If authentication to a website is necessary, give us a test username and password to facilitate our work. This can be provided in the Whiteboard field, which can be found in the Edit Listing page under the Technical Details section. This information is only available to reviewers..

But the Whiteboard already have the information needed to test… URL for the page, test account authentication details, tutorial, etc.

4

You can discuss a review verdict by either replying to the email or using the text area hidden behind the “Review History” link on the Manage Status & Versions on the Developer Hub. Both feed into the same communication system.

Can you clarify what you mean by “I don’t get any answers”? I see two interpretations: the reviewer never replies or the reviewer replies with the same response. For the former, we are currently experiencing higher than normal review times, so reviewer responses may be significantly delayed. For the latter, you may need to follow up on the thread to request clarification again.

Could you share the ID of your extension?

5

Great, maybe the problem is just delay. I was afraid that it takes too much time and my addon gets deleted.

For reference, I access my addon on https://addons.mozilla.org/developers/addon/2900946 so I think the id is 2900946

6

AMO doesn’t remove rejected add-ons like that. So no need to worry :slight_smile:

It looks like the reviewer did not review version 0.0.47 after you updated your testing information, but did review 0.0.48. You should have received a separate notification about the newer version on April 4, 2025.