# Extension review problems

**URL:** <https://discourse.mozilla.org/t/extension-review-problems/13034>\
**Category:** addons.mozilla.org\
**Created:** [January 15, 2017, 9:40pm UTC](https://discourse.mozilla.org/t/extension-review-problems/13034 "2017-01-15T21:40:25Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![booksfordc](https://avatars.discourse-cdn.com/v4/letter/b/34f0e0/32.png) [@booksfordc](https://discourse.mozilla.org/u/booksfordc)\
**Post date:** [January 15, 2017, 9:40pm UTC](https://discourse.mozilla.org/t/extension-review-problems/13034/1 "2017-01-15T21:40:25Z")

</div>

Just wanted to check that our add on update wasn’t in purgatory, because it has only moved one spot in the queue in the last 3 days. Seemed like the weekly status had things moving pretty quickly.

It’s a pretty small extension and it would be great to be able to post about the update (the current version is badly broken and the Chrome update has already uploaded).

[https://addons.mozilla.org/en-us/firefox/addon/booksfordc/](https://addons.mozilla.org/en-us/firefox/addon/booksfordc/)

Thank you!

---

<div class="post-metadata">

**Author:** ![booksfordc](https://avatars.discourse-cdn.com/v4/letter/b/34f0e0/32.png) [@booksfordc](https://discourse.mozilla.org/u/booksfordc)\
**Post date:** [January 16, 2017, 3:41pm UTC](https://discourse.mozilla.org/t/extension-review-problems/13034/2 "2017-01-16T15:41:06Z")

</div>

Following on: Is there a way for me to have an add-on update available through a link while it is undergoing review for being publicly listed? What’s the normal process for getting an update out quickly if the version currently on AMO has broken? It looks like @erosman originally reviewed my add-on.

---

<div class="post-metadata">

**Author:** ![booksfordc](https://avatars.discourse-cdn.com/v4/letter/b/34f0e0/32.png) [@booksfordc](https://discourse.mozilla.org/u/booksfordc)\
**Post date:** [January 16, 2017, 5:55pm UTC](https://discourse.mozilla.org/t/extension-review-problems/13034/3 "2017-01-16T17:55:23Z")

</div>

Uh oh. I just tried signing my extension with web-ext and it moved me to the last position in the queue! @erosman could you assist? The web-ext sign command even returned an error and the submitted version no longer shows up in the version history.

---

<div class="post-metadata">

**Author:** ![erosman](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/erosman/32/15447_2.png) [@erosman](https://discourse.mozilla.org/u/erosman)\
**Post date:** [January 16, 2017, 6:50pm UTC](https://discourse.mozilla.org/t/extension-review-problems/13034/4 "2017-01-16T18:50:14Z")

</div>

There are others addons in the queue and all will be reviewed.

It is worth noting that update reviews are often quicker since often there are not a lot of changes to the code.

In case of migrations to WebExtension, the code changes and the review is like a brand new review from scratch which takes longer.

---

<div class="post-metadata">

**Author:** ![booksfordc](https://avatars.discourse-cdn.com/v4/letter/b/34f0e0/32.png) [@booksfordc](https://discourse.mozilla.org/u/booksfordc)\
**Post date:** [January 16, 2017, 8:23pm UTC](https://discourse.mozilla.org/t/extension-review-problems/13034/5 "2017-01-16T20:23:48Z")

</div>

Is there no way to fix my extension going suddenly from 20th to 83rd in the queue when I tried to sign it? Thanks!

---

<div class="post-metadata">

**Author:** ![jorgev](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jorgev](https://discourse.mozilla.org/u/jorgev)\
**Post date:** [January 18, 2017, 11:59pm UTC](https://discourse.mozilla.org/t/extension-review-problems/13034/6 "2017-01-18T23:59:56Z")

</div>

What do you mean by “tried to sign it”?

---

<div class="post-metadata">

**Author:** ![booksfordc](https://avatars.discourse-cdn.com/v4/letter/b/34f0e0/32.png) [@booksfordc](https://discourse.mozilla.org/u/booksfordc)\
**Post date:** [January 19, 2017, 7:00am UTC](https://discourse.mozilla.org/t/extension-review-problems/13034/7 "2017-01-19T07:00:25Z")

</div>

@jorgev I ran web-ext build and web-ext sign. It returned an error (if I recall correctly) that my extension could not be signed due to something like a difference with my system clock.

I later looked at the review queue and the version of my extension up for review changed from v1.2.1 (which I had uploaded manually through the AMO interface) to v1.2.2 (which I didn’t and had locally). This removed v1.2.1 from the queue (which was in position 20), and moved me to the back of the queue with v1.2.2.

---

<div class="post-metadata">

**Author:** ![jorgev](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jorgev](https://discourse.mozilla.org/u/jorgev)\
**Post date:** [February 9, 2017, 11:02pm UTC](https://discourse.mozilla.org/t/extension-review-problems/13034/8 "2017-02-09T23:02:07Z")

</div>

Yes, resubmitting takes you back in the queue and `web-ext sign` submits a new version for review.