830913 - The manifestURL for the maps packaged app points to a non-existent URL - updates will not work for this preloaded app

Status: VERIFIED FIXED

(Firefox OS Graveyard :: Gaia, defect)

Description

[Jason Smith [:jsmith]]

The manifestURL for the maps packaged app preloaded on device points to a non-existent URL. That's a problem - we won't be able to update this preloaded packaged apps. We need to fix this for v1 obviously.

Comment 1

[Donovan Preston [:fzzzy]]

To fix this, we first need to get the packaged maps app into the marketplace, then we need to switch the manifest url of the external app in gaia to the marketplace's copy of the packaged app mini manifest.

Comment 3

[Alex Keybl [:akeybl]]

Julien - can you resolve this bug and bug 830775?

Comment 4

[Julien Wajsberg [:julienw]]

Problem is: I don't know what the correct update manifest is for Maps ;-) Or it may be correct and it need to be on the server along with the new zip.

Handing over to Fabrice for this one, he probably knows.

Fabrice, if you like, feels free to reassign to myself with the necessary information.

Comment 5

[Donovan Preston [:fzzzy]]

The marketplace code for accepting packaged apps is not yet rolled out to production, so there is no suitable url available yet until this happens.

We probably needinfo from a marketplace folk about when this will be rolled out.

Comment 6

[Jason Smith [:jsmith]]

Wil - Do you know when we'll know the manifestURL for the maps packaged app on marketplace prod?

Comment 7

[Donovan Preston [:fzzzy]]

Andy from Nokia suggested in an email that they could just host the zip on here.com. I don't really see a problem with this because it does not require advanced permissions and thus may not need signing.

Comment 8

[Wil Clouser [:clouserw]]

I replied on IRC, but all I said is I don't know a schedule for hosting the app.  If the app exists (as comment 7 suggests) they should upload it to the marketplace.  If you need help, let me know, but there's no reason not to.

Comment 9

[Donovan Preston [:fzzzy]]

(In reply to Wil Clouser [:clouserw] from comment #8)
> I replied on IRC, but all I said is I don't know a schedule for hosting the
> app.  If the app exists (as comment 7 suggests) they should upload it to the
> marketplace.  If you need help, let me know, but there's no reason not to.

Hey Wil,

I didn't see the Packaged App UI on the production marketplace site when I looked earlier today, though? Did I not look in the right place?

Comment 10

[Wil Clouser [:clouserw]]

(In reply to Donovan Preston from comment #9)
> (In reply to Wil Clouser [:clouserw] from comment #8)
> > I replied on IRC, but all I said is I don't know a schedule for hosting the
> > app.  If the app exists (as comment 7 suggests) they should upload it to the
> > marketplace.  If you need help, let me know, but there's no reason not to.
> 
> Hey Wil,
> 
> I didn't see the Packaged App UI on the production marketplace site when I
> looked earlier today, though? Did I not look in the right place?

It's a questionable UX.  You have to choose FirefoxOS (and only FxOS) on https://marketplace.firefox.com/developers/submit/app/manifest and the tab will appear.

Comment 11

[Donovan Preston [:fzzzy]]

Awesome. Thank you.

Comment 12

[AndyT]

I wanted to try it out in the Marketplace, but once an app is submitted you cannot change this anymore. It says "Manifest URLs cannot be changed after your app has been submitted. Please email [e-mail] if there is a reason you need to modify your manifest URL."

What would be the best strategy to upload to the Marketplace now? Should we create a second app, test with that one and delete the old one once we know everything is working with the packaged app?

Comment 13

[Donovan Preston [:fzzzy]]

(In reply to AndyT from comment #12)
> I wanted to try it out in the Marketplace, but once an app is submitted you
> cannot change this anymore. It says "Manifest URLs cannot be changed after
> your app has been submitted. Please email [e-mail] if there
> is a reason you need to modify your manifest URL."
> 
> What would be the best strategy to upload to the Marketplace now? Should we
> create a second app, test with that one and delete the old one once we know
> everything is working with the packaged app?

Hi Andy... I think submitting a second app is the only solution available at the moment. Thanks.

Comment 14

[AndyT]

But can we do that without publishing the second app, or hiding from search? It would be confusing to have two apps out there to the consumers at the same time. That would be a good reason not to publish the packaged app to the marketplace (comment #8)

Comment 15

[Wil Clouser [:clouserw]]

(In reply to AndyT from comment #14)
> But can we do that without publishing the second app, or hiding from search?
> It would be confusing to have two apps out there to the consumers at the
> same time. That would be a good reason not to publish the packaged app to
> the marketplace (comment #8)

The app can be inactive and won't show up.  It depends on what you're trying to do.  If just reserve a namespace or something, uploading it and marking it inactive would work.

Comment 18

[Donovan Preston [:fzzzy]]

This was fixed by the 833940 fix

Comment 19

[Jason Smith [:jsmith]]

Donovan - Are both of these bugs fixed now? If so, can we close this?

Comment 20

[Donovan Preston [:fzzzy]]

Yep this is fixed.

Comment 21

[John Ford [:jhford] CET/CEST Berlin Time]

Is there anything that actually landed in this bug?  If not, can we set status-b2g18 to fixed?

Comment 22

[Donovan Preston [:fzzzy]]

Nothing landed specifically for this, the fix for this was landed as part of 833940.

Set away.

Comment 23

[Jason Smith [:jsmith]]

Verified through testing the update goes through now.