I submitted this add-on for review 10 days ago but it has not been reviewed yet. Previously, reviews for new versions were completed automatically in a short time, but with the latest update I submitted, there has been no response for 10 days now.
Hi, and thanks for reaching out, and I am sorry for the wait.
You are right that update reviews often go through quickly. Some versions do get picked up for manual review, and once that happens they join the same queue as new submissions, which is where this one is now.
We have been working through a large influx of submissions and that has stretched review times. I am not able to give you an exact date, and resubmitting or following up unfortunately doesn’t move a version up the queue. We wrote about what is happening and what we are doing about it here: Important update: Addressing the long manual review times.
If the reviewer needs anything from you, it will show up on your add-on’s page in the Developer Hub under “Manage Status & Versions”. That is also the place to reply to them directly, since our reviewers don’t monitor this channel.
Thank you for your reply and for explaining the current review queue situation.
Just to update you — it has now been 18 days and my update is still in “Awaiting Review”. I understand manual reviews are delayed due to the influx.
In the meantime I have submitted a newer version (1.8.6) which includes the build-for-amo script as you suggested:
Source code is included and the build is reproducible via npm ci && npm run build-for-amo (output in build/firefox-mv2-prod).
Could you please let me know — does submitting this newer version restart the review waiting time from zero, or does it keep its place in the queue? I want to avoid doing anything that would further delay it.
I will keep an eye on “Manage Status & Versions” in the Developer Hub for any reviewer request.