# You cannot update a WebExtensions add-on with a legacy add-on

**URL:** https://discourse.mozilla.org/t/you-cannot-update-a-webextensions-add-on-with-a-legacy-add-on/14801
**Category:** Development
**Created:** [April 4, 2017, 6:58am UTC](https://discourse.mozilla.org/t/you-cannot-update-a-webextensions-add-on-with-a-legacy-add-on/14801 "2017-04-04T06:58:12Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![tentacles](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@tentacles](https://discourse.mozilla.org/u/tentacles)
#### Post date: [April 5, 2017, 5:52am UTC](https://discourse.mozilla.org/t/you-cannot-update-a-webextensions-add-on-with-a-legacy-add-on/14801/5 "2017-04-05T05:52:09Z")

</div>

Example:  
(1) you uploaded version 1.0, which was based on the Add-on SDK  
(2) you uploaded version 2.0, which was based on WebExtension  
(3) you uploaded version 3.0, which appears to be using the Add-on SDK again

From DaveRo’s link:

> [@About upgrading a profile to Web-Extensions](https://discourse.mozilla.org/t/about-upgrading-a-profile-to-web-extensions/13585/2):
>
> You, as the dev, cannot upload a non-webxt again to that listing.

In other words: Make sure that version 3.0 in the above example is also a WebExtension Add-on. In case it really/already is a WebExtension, try to figure out what makes AMO think that it isn’t.

@jorgev  
I didn’t upgrade my SDK Add-on to WebExtension yet. But it looks like AMO should display a warning when you upload a WebExtension version to a legacy/SDK Add-on the first time: Just to make it abundantly clear that all future versions must also use WebExtension.

---

_[View the full topic](https://discourse.mozilla.org/t/you-cannot-update-a-webextensions-add-on-with-a-legacy-add-on/14801)._