# What happens when I don't make the WebExtensions migration in time?

**URL:** <https://discourse.mozilla.org/t/what-happens-when-i-dont-make-the-webextensions-migration-in-time/20922>\
**Category:** Development\
**Created:** [October 27, 2017, 1:35pm UTC](https://discourse.mozilla.org/t/what-happens-when-i-dont-make-the-webextensions-migration-in-time/20922 "2017-10-27T13:35:23Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon31560143](https://avatars.discourse-cdn.com/v4/letter/a/7bcc69/32.png) [@anon31560143](https://discourse.mozilla.org/u/anon31560143)\
**Post date:** [October 27, 2017, 1:35pm UTC](https://discourse.mozilla.org/t/what-happens-when-i-dont-make-the-webextensions-migration-in-time/20922/1 "2017-10-27T13:35:23Z")

</div>

For my FF extension I’m currently working on the migration process to **WebExtensions**.

The **release date for FF 57 is Nov 14th**?

What happens when I can’t finish the migration till the release date?

Is there a **transitional period for SDK-addons** even after the release of FF 57?

---

<div class="post-metadata">

**Author:** ![amyt](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/amyt/32/20624_2.png) [@amyt](https://discourse.mozilla.org/u/amyt)\
**Post date:** [October 27, 2017, 5:54pm UTC](https://discourse.mozilla.org/t/what-happens-when-i-dont-make-the-webextensions-migration-in-time/20922/2 "2017-10-27T17:54:06Z")

</div>

You can still migrate after Firefox 57–when you update the code, your users will automatically get the new version. In the meantime, there is a [function](https://blog.mozilla.org/addons/2017/10/26/helping-find-compatible-extensions/) in version 57 on AMO that directs people with legacy extensions to a recommended alternative (and the featured collection, if no alternative has been identified). Once you update, your users will no longer be redirected. Would you mind me asking which add-on you are working on?

---

<div class="post-metadata">

**Author:** ![amyt](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/amyt/32/20624_2.png) [@amyt](https://discourse.mozilla.org/u/amyt)\
**Post date:** [October 27, 2017, 6:25pm UTC](https://discourse.mozilla.org/t/what-happens-when-i-dont-make-the-webextensions-migration-in-time/20922/4 "2017-10-27T18:25:46Z")

</div>

Cool, thanks. Is there a particular replacement you want us to redirect users to temporarily, or are you alright with people landing on the featured collection?

---

<div class="post-metadata">

**Author:** ![anon31560143](https://avatars.discourse-cdn.com/v4/letter/a/7bcc69/32.png) [@anon31560143](https://discourse.mozilla.org/u/anon31560143)\
**Post date:** [October 27, 2017, 6:31pm UTC](https://discourse.mozilla.org/t/what-happens-when-i-dont-make-the-webextensions-migration-in-time/20922/5 "2017-10-27T18:31:17Z")

</div>

There is no good replacement I think, so featured collection would be fine.  
But I will search tomorrow if I can find a temp replacement…  
Perfect would be if the users of my extension could be informed about the delayed release of my FF-57-compatible version of Textmarker, so that they know they will be able to use it in the near future

---

<div class="post-metadata">

**Author:** ![amyt](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/amyt/32/20624_2.png) [@amyt](https://discourse.mozilla.org/u/amyt)\
**Post date:** [October 30, 2017, 4:36pm UTC](https://discourse.mozilla.org/t/what-happens-when-i-dont-make-the-webextensions-migration-in-time/20922/6 "2017-10-30T16:36:13Z")

</div>

You can push an update that shows a notification for users. That would  
be the most effective approach. Alternatively, you can change your AMO  
description or summary, which are visible in the Add-ons Manager.

---

<div class="post-metadata">

**Author:** ![anon31560143](https://avatars.discourse-cdn.com/v4/letter/a/7bcc69/32.png) [@anon31560143](https://discourse.mozilla.org/u/anon31560143)\
**Post date:** [October 31, 2017, 1:38pm UTC](https://discourse.mozilla.org/t/what-happens-when-i-dont-make-the-webextensions-migration-in-time/20922/7 "2017-10-31T13:38:07Z")

</div>

@amyt I would like to take both approaches but unfortunately I cannot test a new version anymore using `jpm run -b nightly` with the new version of Nightly i upgraded to (the xpi is being disabled), and I don’t see any good way to test.  
Also, considering that the approval of the last release of my addon took more than 3 months I doubt that publishing a new version with some notification or AMO description update will reach my users in time (before Nov 14th that is).

---

<div class="post-metadata">

**Author:** ![amyt](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/amyt/32/20624_2.png) [@amyt](https://discourse.mozilla.org/u/amyt)\
**Post date:** [October 31, 2017, 7:35pm UTC](https://discourse.mozilla.org/t/what-happens-when-i-dont-make-the-webextensions-migration-in-time/20922/8 "2017-10-31T19:35:33Z")

</div>

Right, the SDK is no longer supported. :-/ The review queues, however, are much [faster](https://blog.mozilla.org/addons/2017/09/21/review-wait-times-get-shorter/) now that we’ve moved to a post-review model for add-ons built with the WebExtensions API. So you should not experience any delays when you update to your WebExtensions version.