Closed Bug 1170976 Opened 10 years ago Closed 10 years ago

Cannot submit addon for review: "Duplicate UUID found"

Categories

(addons.mozilla.org Graveyard :: Add-on Validation, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: david.stark, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Steps to reproduce: I'm attempting to validate the addon seleniumbuilder@saucelabs.com for external distribution. Actual results: Your add-on failed validation with 1 error. Duplicate UUID found. (Builder is not currently listed on addons, and my account doesn't have a listing for it.) Expected results: It should have allowed me to continue validation.
Here's the listing that corresponds to that ID: https://addons.mozilla.org/addon/se-builder/ Were you aware of the listing, or the owner account?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Right, that's the previous main developer of the plugin. I note that the listing states the add-on has been removed. Can you completely delete the listing, or can admc remove it entirely?
The easiest solution in this case would be for admc to give you access to the listing. Then you can enable it and submit a new version.
OK, done that. I'm afraid now I got another blocker. When I submit the new version of the addon, I get the following error: Banned element in install.rdf Error: The element "updateURL" was found in the add-on's install.rdf file. It is not allowed in add-ons under the current configuration. install.rdf I assume this is because it's set to be distributed from mozilla? I don't need it to be distributed from there, I just need it validated. I haven't found a way to change this setting.
When you say you need it "validated", you mean "signed"? The "updateURL" element is only allowed in unlisted (non-AMO) addons. If you don't want your addon to be listed on AMO, then when you submit a (new) addon, you can uncheck the appropriate checkbox (on the second step of the submission). You can also unlist your addon from the "manage status & versions" page of the devhub page for this addon. There's a radio button that you can select, and your addon will be unlisted from AMO. Please note though that this will unlist the addon itself, not a specific version, and this manipulation is not reversible.
This seems to happen for extensions that were submitted for review and have been rejected for any reason in the past. the error message should provide information how to fix this: # generate new uuid (how? cfx init + copy from new install rdf) (what about updates / existing installations?) # a link to the extension that seems to have the uuid, so the collision can be investigated, ownership transfer can be requested etc the uuid that causes this for me is jid1-q4cqHvcL3sC4vQ and the addon can be aquired from https://download.refeus.de/files/public/release/addons/refeus-webcollect-firefox.xpi
Yeah, what worked for me (I think) is the following sequence: * Get admin access to the addon from the guy who submitted it originally. * Delete the old version entirely. * Upload new version. Now I'm just waiting for a verdict.
Okay, so it sounds like this bug is resolved now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
(In reply to firefox-marketplace from comment #6) solved with the help of jorgev on irc: * the addon was indeed managed by a different login. the login could only be identified with the help of the irc. * i was urged not to delete the addon because of https://bugzilla.mozilla.org/show_bug.cgi?id=1176697 the issue is solved for me
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.