XUL to Webextension = Add-on ID doesn’t match add-on

Add-ons addons.mozilla.org
#1

Hi,

I’m trying to submit an updae for an add-on that was using old XUL and firefox APIs. It’s been rewritten to use webextensions.
However when i submit it, the tests are okay but i get the following message :

Add-on ID doesn’t match add-on

I’ve put in my manifest .json the same id i used to have in my install.rdf :

Manifest.json :

“applications”: {
“gecko” : {
“id”: "toolbar@capitalkoala.com"
}

Install.rdf :

<RDF …
em:id="toolbar@capitalkoala.com"
…

Do you know where the problem could come from ?
Maybe i should create a new whole Add-On but i would be forced to change the Add-on 's name and i’d rather not.

Thanks
}

1 Like
#2

You should be able to submit the new version if you use the same ID. Can you point to the new XPI and to the add-on page, so we can look into it?

#3

Hi jorgev,

Thanks for your answer.
The addon page is at https://addons.mozilla.org/fr/firefox/addon/capital-koala/?src=search

The xpi can be downloaded at http://www.capitalkoala.com/project/public/media/capital-koala_v6.0.0.0_webext.xpi

Please let me know if you need anything else.
This xpi contains a manifest with no id at all. From what i’ve read recently it should be accepted by AMO.
However i keep getting the same error message.

#4

The problem is that you have a package.json file in your XPI, which confuses the validation process. Removing it should fix the ID problem. I should add I’m not sure if submitting a file without an ID is fully functional at the moment.

#5

Oh god. I should’ve thought of that.
It makes sense.

I’m going to remove it and test again.

Thank you Jorgev

#6

I seem to have the same problem. I do not have any jason and this extension has been around for many years and I just updated for ff45.0 What other things might cause this error?
https://addons.mozilla.org/en-US/firefox/addon/read2me-speechify-the-web/

#7

Can you share the update you’re trying to upload?

#8

Sure http://stlouis-shopper.com/read2me.xpi

#9

jorgev I’m sure you are busy but do you any thoughts on this issue?

#10

Sorry for the slow response, I missed your other messages. In this case the error is correct. You can find the add-on ID in the add-on management page, which is definitely a different ID than the one in the XPI you point to.

#11

That was dumb, thanks jorgev. Not excusing my error but what stopped me from looking for my error was that the validation page said the xpi passed all tests despite the fact there was clearly an error. And this was the only reference to this that i found.

Thanks again.