# Approval ETA 2 months - what can we do until our addon is reviewed?

**URL:** <https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002>\
**Category:** addons.mozilla.org\
**Created:** [April 12, 2017, 3:26pm UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002 "2017-04-12T15:26:48Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![askoli.net](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@askoli.net](https://discourse.mozilla.org/u/askoli.net)\
**Post date:** [April 12, 2017, 3:26pm UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002/1 "2017-04-12T15:26:48Z")

</div>

We’ve submitted an addon and now see the queue advancing horribly slowly.

We first uploaded minimized code with the full code attached, and that got it flagged for lengthy admin review.

So we cancelled this and uploaded it anew, with the plain, commented code and no attachment. But it’s still moving as slowly as before. ETA = 2 months!

We’ve secured 2 pilot cooperations with organizations with 100K consumers/users each and they may cancel if we can’t deliver sooner. What are our options?

1. After uploading, I got an email saying that the add-on, awaiting review, can be accessed and installed directly from its detail page. But when accessing the page, it says it can’t be installed on FF \>= V43
2. Would it be better to self-host the extension? Also gives an ugly warning but at least it installs. But I don’t like it.
3. Can we get it online immediately without it being visible in the addons directory? Kind of unlisted, un-reviewed version? People are invited by the organizations, so they don’t have to stumble upon us.
4. Our last option not to lose our clients and close shop, is pointing them to another browser, but that’s a hurdle and to nobody’s advantage.

Any suggestions to bridge the time to the review date are welcome.

---

<div class="post-metadata">

**Author:** ![Kenny\_D](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Kenny\_D](https://discourse.mozilla.org/u/Kenny_D)\
**Post date:** [April 12, 2017, 5:05pm UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002/2 "2017-04-12T17:05:55Z")

</div>

Upload a new version and make it unlisted. The extension will be signed automatically and then you can self-host it.

> **[Signing and distributing your add-on](https://developer.mozilla.org/en-US/Add-ons/Distribution#Self-distributed_(unlisted)_versions)**
>
> Once you have a first build of your add-on, you'll want to distribute it so others can give it a try. Whether you are distributing your add-on publicly or privately, through addons.mozilla.org (AMO) or elsewhere, you'll want to have your add-on...

---

<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:** [April 12, 2017, 7:57pm UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002/3 "2017-04-12T19:57:24Z")

</div>

Which addon is it?  
If you include addon’s link, we can see what is happening.

---

<div class="post-metadata">

**Author:** ![askoli.net](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@askoli.net](https://discourse.mozilla.org/u/askoli.net)\
**Post date:** [April 13, 2017, 3:44pm UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002/4 "2017-04-13T15:44:38Z")

</div>

Thanks for the suggestion. That’s what we will have to do if we really don’t have another option. But a self-hosted addon gives a security warning during installation that might scare off users. How many is to be seen, we’ll know that when we compare our Firefox and Chrome stats.

---

<div class="post-metadata">

**Author:** ![askoli.net](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@askoli.net](https://discourse.mozilla.org/u/askoli.net)\
**Post date:** [April 13, 2017, 3:47pm UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002/5 "2017-04-13T15:47:44Z")

</div>

Thanks for your reaction. It’s this one: [https://addons.mozilla.org/en-US/firefox/addon/askolinet/](https://addons.mozilla.org/en-US/firefox/addon/askolinet/)

We haven’t bothered uploading a description or screenshots yet, as long as we don’t know if it’s even going to be published.

---

<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:** [April 13, 2017, 4:17pm UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002/6 "2017-04-13T16:17:20Z")

</div>

The addon was uploaded April 10th.

---

<div class="post-metadata">

**Author:** ![Kenny\_D](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Kenny\_D](https://discourse.mozilla.org/u/Kenny_D)\
**Post date:** [April 13, 2017, 5:04pm UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002/7 "2017-04-13T17:04:52Z")

</div>

> [@askoli.net](#):
>
> self-hosted addon gives a security warning during installation that might scare off users

It doesn’t actually. If you make it unlisted on AMO, then it will give you the option of downloading a signed version that will just act like any other signed addon, and you can self host that version. You can even install it on release and beta versions.

---

<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:** [April 14, 2017, 4:29am UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002/8 "2017-04-14T04:29:57Z")

</div>

Please note that AFAIK self-hosted, unlisted addons don’t auto-update.

---

<div class="post-metadata">

**Author:** ![askoli.net](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@askoli.net](https://discourse.mozilla.org/u/askoli.net)\
**Post date:** [April 16, 2017, 7:56am UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002/9 "2017-04-16T07:56:51Z")

</div>

OK, we’ll give it a try. If it works like that, that would be very helpful.

When I last signed it and downloaded the signed version, then tried to install that, it did give a warning. But we’ll try to play with the settings.

---

<div class="post-metadata">

**Author:** ![askoli.net](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@askoli.net](https://discourse.mozilla.org/u/askoli.net)\
**Post date:** [April 16, 2017, 7:58am UTC](https://discourse.mozilla.org/t/approval-eta-2-months-what-can-we-do-until-our-addon-is-reviewed/15002/10 "2017-04-16T07:58:10Z")

</div>

There is a way to make them auto update, we did get that far already.