309697 - "Name for your extension or theme already exists" when uploading previously deleted extension

Status: RESOLVED FIXED

(addons.mozilla.org Graveyard :: Public Pages, defect, P1)

Description

[spam.mozilla.org]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4

I get an error message: "Error! The Name for your extension or theme already
exists in the Update database. Cannot Continue, aborting." when I try to upload
my extension. The name of my extenstion is "Master Password Timeout". I
previously uploaded this extension but then deleted it (and got this error next
time i tried to add it) then i deleted my entire account (and still got the same
error).

Reproducible: Always

Steps to Reproduce:
1.Upload my extension "Master Password Reset"

Actual Results:  
Error! The Name for your extension or theme already exists in the Update database.
Cannot Continue, aborting.

Expected Results:  
Should have added the extension to "my extensions"

Please fix this in the db so I can upload my extension asap, then we can work on
a solution.

Comment 1

[Jayson Harshbarger]

I have the same issue with my extension Xinha Here.  I uploaded a new version of my extension.  When I noticed that it created a new extension rather then updating the old one (used the wrong GUID) I deleted it and tried again.  I get this error every time.  Completely locked out of the system.  Very frustrating!

Comment 2

[Jayson Harshbarger]

Same as bug #314029 (https://bugzilla.mozilla.org/show_bug.cgi?id=314029)

Comment 3

[Michael Morgan [:morgamic]]

*** Bug 314029 has been marked as a duplicate of this bug. ***

Comment 4

[Michael Morgan [:morgamic]]

Will look into this bug this afternoon.  Sorry about the frustration.

Comment 5

[Jayson Harshbarger]

I noticed that there was a second entry for my plugin (Xinha Here) that had no files.  I was able to delete this entry for my plugin and then my uploads work as expected.  So at least in my case this issue is resolved.

Comment 6

[Christopher Finke]

I can confirm that this bug also affects my extension, GoogleTabs. I am unable to upload a new version.

Comment 7

[Christopher Finke]

Are there any plans to actually fix this bug?  I have been unable to upload a new version of my extension since FF 1.5 came out, so no one running the latest Firefox can install it.

Comment 8

[Michael Morgan [:morgamic]]

Chris, I intend to actually fix this.  I'll be working on it this week, now that I'm settled back in.

Comment 9

[Michael Morgan [:morgamic]]

To be honest, I'm a little unclear about how this is happening.  From what I can see, in the GoogleTabs case there is actually only one record in `main` containing the same guid and name.  What were the exact steps that got you to this point?  Did you create anything then delete it, or enter any mismatching GUIDs?

Comment 10

[Michael Morgan [:morgamic]]

mysql> select guid from main where name='googletabs';
+---------------------------------------+
| guid                                  |
+---------------------------------------+
| {2e4e84fc-ebb9-f71a-770a-7654c6f488b} |
+---------------------------------------+
1 row in set (0.69 sec)

mysql> select name from main where guid = '{2e4e84fc-ebb9-f71a-770a-7654c6f488b}';
+------------+
| name       |
+------------+
| GoogleTabs |
+------------+
1 row in set (0.01 sec)

Comment 11

[Christopher Finke]

Somehow, that GUID didn't match what I had on file for GoogleTabs. I changed it in the new version and was able to upload it.  Sorry about that hassle.

Comment 12

[Michael Morgan [:morgamic]]

Ok, no problem.  There are a couple of things we can do to make this better:
1. make the error message say that the GUIDs don't match
2. make an FAQ entry that talks about this particular situation

I'll work on those.

Comment 13

[Michael Morgan [:morgamic]]

I added an FAQ to cover this, and also improved the error message to be more descriptive -- pointing out the mismatching GUIDs as a possible cause, or a duplicate record.  This should help reduce confusion and explain what's going on better.

If anyone else has an outstanding issue with this bug, please reopen it and ping me so we can figure out what's going on.  Thanks.  :)

Comment 14

[Michael Morgan [:morgamic]]

AMO BUGSPAM FOR COMPONENT MOVE AND DELETE (FILTER ME)

Comment 15

[Reed Loden [:reed]]

AMO BUGSPAM FOR QACONTACT FIX (FILTER ME)