Closed Bug 779740 Opened 12 years ago Closed 12 years ago

"Description already exists" error is displayed on the Additional Information field when submitting a new app


(Marketplace Graveyard :: Developer Pages, defect, P2)

Windows 7


(Not tracked)



(Reporter: cboldan.mozbugs, Unassigned)



(Keywords: regression)

Steps to reproduce:
1. Load My Submissions page and submit a new app ( )
2. Enter a valid manifest and get to step 3 (Edit App Details page)
3. Complete all the required fields and click Continue.

Expected results:
There are no errors displayed, user is able to continue the submission process.

Actual results:
"Addon with this Description already exists." error is displayed on the Additional Information field, even if the field is not edited at all.

Verified in FF17 (Win 7).Issue is not reproducing in production.
Screencast for this issue
I don't get this on -dev.
Closed: 12 years ago
Resolution: --- → WORKSFORME
Issue is reproducing in on FF14 (Win 7)
Please see attached screencast
Resolution: WORKSFORME → ---
Cristian reopened this bug for AMO but I want to specify that I am able to reproduce it on MP too :

Please fix for both AMO and MP
Assignee: nobody → robhudson.mozbugs
Priority: -- → P2
Target Milestone: --- → 2012-08-16
Assignee: robhudson.mozbugs → mattbasta
Depends on: 784109
Target Milestone: 2012-08-16 → 2012-08-30
This was fixed when we turned on mixed mode replication.
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Verified as fixed in FF18 and on FF15 (Win 7)
Postfix screencast for MP and AMO
Closing bug.
Reproduced again when tried to submit a packaged app on MP dev :
Resolution: FIXED → ---
:cvan This seems similar to the AMO/Collections bug we were discussing and I'm not really comfortable with accepting it's a 'dev only' problem.

These issues are difficult for us QA team to debug in more detail because it looks like the validation is failing at db level and we don't have db access to query for duplicate records and report the IDs (or something like that).

This would help us provide more information but as it is we can only treat it a bit like a black box. We can only really report circumstances in which it worked or failed and even then these are a bit sporadic.

Is there anything we can do or information we can provide to help you debug these issues?
I'm convinced that this is some kind of race condition. I've manually connected to the database and stepped through query-by-query when this is happening "every time" and in that case, the bug doesn't present itself.

Perhaps we should loop Sheeri in on this to give some advice on how to debug this sort of thing more sanely. Maybe we can get access to the raw MySQL query logs to compare the order of the queries or maybe we're performing some kind of operation asynchronously that we should be performing synchronously.
I agree this is unacceptable. I've asked our team if we can do a DB refresh (last one was roughly over two months ago), which I'm hoping will fix this.
That stacktrace doesn't mean much to a developer. Can you supply the screenshot at the point of the failure?

Include the application name or id that it was trying to create and also include the description that is supposedly the duplicate?

Then the developers have something to work with - they can search the database for the affected records.
More information for comment 12

Screenshot at the point of failure:

Application name that was trying to be created: Mock Application 1351643063

In "Additional Information" field, the description that is supposedly the duplicate: more details of marble app 1351643063
Wil tells me that the update in 799168 means you don't need a DB refresh. Is that true?

I can get you query logs but I have to turn them on, and they get large quickly, so it would have to have an end time (e.g. logs for one day or one week or something like that).
Assignee: mattbasta → nobody
Basta, anything to do here? No?
Target Milestone: 2012-08-30 → ---
Guys what's the status of this bug? because it's no longer reproducible on marketplace developers pages
I will close it then.  From the above comments we were having difficulty reproducing it.
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
QA Verified!
You need to log in before you can comment on or make changes to this bug.