862775 - OTA Marketplace update tells me the download fails

Status: RESOLVED FIXED

(Marketplace Graveyard :: General, defect, P1)

Description

[Frederik Braun [:freddy] (OOO until April 28th)]

I just flashed an engineering build on an unagi test device that is a few days old.
Afterwards it did a successful OTA update for the system and HERE maps.
A bit later I was notified that there is a Marketplace update available.
I tried downloading it but I get a download failed message.

adb logcat has this here for us:
> E/GeckoConsole(  108): Content JS INFO at app://system.gaiamobile.org/js/updatable.js:102 in anonymous: downloadError event, error code is INVALID_SIGNATURE


If I can provide additional debug information, please needinfo me.

Comment 1

[Jason Smith [:jsmith]]

Chris - Any ideas?

Comment 2

[Wil Clouser [:clouserw]]

We'll need someone from the platform side to tell us what INVALID_SIGNATURE means.  Hopefully not more signing troubles..?

There are also similar reports via email about trouble upgrading (I know you've seen them Jason, not sure if they are related).

Comment 3

[Rob Hudson [:robhudson]]

I talked to cvan this morning and we're thinking it's because "yule log" isn't being signed since it's not flowing through the normal review channels. And all apps from our Marketplace, regardless of their type, are required to be signed.

Comment 4

[Wil Clouser [:clouserw]]

(In reply to Rob Hudson [:robhudson] from comment #3)
> I talked to cvan this morning and we're thinking it's because "yule log"
> isn't being signed since it's not flowing through the normal review
> channels. And all apps from our Marketplace, regardless of their type, are
> required to be signed.

As far as I know that has always been a marketplace requirement, not a device requirement.  Did that change?

Comment 5

[Rob Hudson [:robhudson]]

(In reply to Wil Clouser [:clouserw] from comment #4)
> As far as I know that has always been a marketplace requirement, not a
> device requirement.  Did that change?

Packaged apps with only web privileges technically don't need to be signed. But we chose to do it for Marketplace anyway and device side enforces that.

Comment 6

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

(In reply to Rob Hudson [:robhudson] from comment #5)
> (In reply to Wil Clouser [:clouserw] from comment #4)
> > As far as I know that has always been a marketplace requirement, not a
> > device requirement.  Did that change?
> 
> Packaged apps with only web privileges technically don't need to be signed.
> But we chose to do it for Marketplace anyway and device side enforces that.

Exactly right. See bug 821207.

Comment 8

[:gerard-majax]

Could it be the same issue as in bug 841569 ?

Comment 9

[Jason Smith [:jsmith]]

(In reply to Alexandre LISSY :gerard-majax from comment #8)
> Could it be the same issue as in bug 841569 ?

No. This is about the fact that marketplace isn't serving a signed packaged app.

Comment 10

[Christopher Van Wiemeersch [:cvan]]

(In reply to Jason Smith [:jsmith] from comment #9)
> (In reply to Alexandre LISSY :gerard-majax from comment #8)
> > Could it be the same issue as in bug 841569 ?
> 
> No. This is about the fact that marketplace isn't serving a signed packaged
> app.

This is fixed on -dev, will be working on prod on Thursday at 2:00 PM PDT.

Comment 11

[Christopher Van Wiemeersch [:cvan]]

Fixed now. The Marketplace package is now always signed.