Closed
Bug 850498
Opened 11 years ago
Closed 11 years ago
Packaged app is incorrectly set to "incomplete" status
Categories
(Marketplace Graveyard :: Developer Pages, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-04-18
People
(Reporter: krupa.mozbugs, Unassigned)
References
()
Details
steps to reproduce: 1. Load https://marketplace.firefox.com/developers/app/tu-me/status 2. Notice that the app status is set to "incomplete" observed behavior: If the app was truly incomplete, the/status page would not be accessible. Please look into why this app is incorrectly in this state. Note that the app version 1.0 is in pending approval state.
Updated•11 years ago
|
Summary: App is incorrectly set to "incomplete" status → Packaged app is incorrectly set to "incomplete" status
Updated•11 years ago
|
Priority: -- → P3
Comment 1•11 years ago
|
||
Hey we need this app submitted for a build by this Friday (3/15/13) ...or there will be blood!
Comment 2•11 years ago
|
||
fyi, I used an admin tool to change the state to pending. So this particular app is 'fixed', assuming there weren't actually any missing details to cause breakage later.
Comment 3•11 years ago
|
||
Verified that the app is pending, thanks! Disaster averted. ;)
Comment 4•11 years ago
|
||
Does anyone know if this app was submitted through the devhub or through the API?
Comment 5•11 years ago
|
||
I sent the dev a link to the marketplace submission page, so I doubt he used the API.
Comment 6•11 years ago
|
||
Is tu-me a packaged app? I can't view the status link.
Comment 7•11 years ago
|
||
Duh, says so in the title :/
Comment 8•11 years ago
|
||
Packaged. Try https://marketplace.firefox.com/app/tu-me/
I am the dev that uploaded the app to the marketplace using the web. I completed all steps (uploaded the bundle, and provided all app information) but the app ended up in "payment information" pending. Let me know how can I help to troubleshoot this.
Updated•11 years ago
|
Assignee: robhudson.mozbugs → mattbasta
Comment 10•11 years ago
|
||
Are there reliable steps to reproduce this issue? The app in the bad state aside, can this issue actually be reproduced in a deterministic way?
Comment 11•11 years ago
|
||
When I first saw this I tried but could not reproduce it.
Comment 12•11 years ago
|
||
closing this bug in the absence of any reported re-occurrences or steps to reproduce.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee: mattbasta → nobody
Target Milestone: --- → 2013-04-18
You need to log in
before you can comment on or make changes to this bug.
Description
•