For the past month I’ve been trying to get in contact with the Mozilla devs who rejected our add-on. They’ve asked for Sources (which I’ve provided), for build instructions (which I’ve provided), for a testing account (which I’ve provided) and testing how-to (which I’ve provided) but still the add-on got rejected without anyone telling me exactly what the issue with it is. It seems that everything that I’m writing into the review notes isn’t getting through to the devs since the add-on was automatically rejected due to the delay being expired. However before the delay was expired I already provided everything that the devs asked for but still radio silence.
Maybe the devs will read this and can get back to me?
Looks like version 1.0.2 was approved a couple days ago, but I’m not sure what is happening with the versions submitted after that one. I’ve reached out internally to request assistance.
@Edward_Sullivan@dotproto Can someone please get back to me? The latest update was that assistance was requested internally but I don’t know why this is necessary or when we can expect an answer.
Hey @IDControl. Sorry I missed your message on Jan 31 and for the poor communication experience you’ve been having in general. You should receive a message from a reviewer in a day or so. I’ll also follow up here in a couple days in case that doesn’t happen as expected (as in the case with my Jan 22 message).
If you are using NPM, make sure to submit also package-lock.json file.
Also, the build instructions should be as simple as possible, for example I use this:
The problem in question was that the dev ran our build script with sudo privileges and the npm utility was not in the PATH variable of the root user. Therefore the required packages could not be installed thus failing the build.
Just popping in to say I saw the updates. Looks like you’ve already diagnosed the reviewer’s build issue, so now we’re just waiting on them to read the update and give it another shot.
I got an email stating that our latest version would be disabled due to the automatic grace period expiring. However I provided all the required information before that time. Will the automatic disabling be undone when a review is done or do I need to upload yet another version of the plugin?
It’s possible for a disabled item to be re-enabled if a developer’s reply addresses the reason for rejection. In most cases that I’ve seen, though, it’s necessary for a developer to change something about the submitted extension in order to address reviewer feedback, which would require a new submission.