Closed Bug 1012448 Opened 11 years ago Closed 11 years ago

public mini-manifest for packaged app is empty {}

Categories

(Marketplace Graveyard :: General, defect, P2)

Avenir
x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED
2014-06-03

People

(Reporter: lourcastillo, Assigned: robhudson)

References

Details

(Whiteboard: [qa-])

No description provided.
I saw on Firefox marketplace that the manifest's link is bad. https://marketplace.firefox.com/app/54403c95-2f64-4c4a-a0e3-37dedc1f224a/manifest.webapp (the manifest is invalid) packaged https://marketplace.firefox.com/app/transantiagoapp/
Assignee: nobody → lourdeslcastilloa
The META-INF folder (with ID) is created by marketplace server. The INVALID_MANIFEST error (by documentation) is by marketplace server, because the manifest.webapp JSON is clean in the server.
The bug will be reviewed by Marketplace Senior Reviewer.
Summary: I can't install from the Firefox Marketplace, when I try to install show me an error message invalid_manifest. → public mini-manifest for packaged app is empty {}
I see a valid mini manifest, it works for clouserw and andym.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
(In reply to Andy McKay [:andym] from comment #5) > I see a valid mini manifest, it works for clouserw and andym. yep same here today, maybe something got fixed in the push.
possible resurgence with a different app - bug 1016475
Reopening... This seems like it can happen when `get_cached_manifest` is called when there is not approved version. When a version is approved it should get updated but it appears that sometimes it doesn't. We need to find and fix that. We can also remove this conditional to avoid caching '{}': https://github.com/mozilla/zamboni/blob/master/mkt/webapps/models.py#L900
Assignee: lourdeslcastilloa → robhudson.mozbugs
Status: RESOLVED → REOPENED
Priority: -- → P2
Resolution: WORKSFORME → ---
https://github.com/mozilla/zamboni/commit/5825f51 This commit avoids setting the cached minifest to '{}' so when a valid version does come into play everything should get set and cached correctly w/o having to track down where to call `force=True`. Flagging as qa- as it's not clear how to create an app in this state.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
Target Milestone: --- → 2014-06-03
You need to log in before you can comment on or make changes to this bug.