Update for Stage marketplace cannot be installed

VERIFIED FIXED in Firefox 35, Firefox OS v2.1

Status

Firefox OS
Gaia::Build
P1
blocker
VERIFIED FIXED
3 years ago
3 years ago

People

(Reporter: jlorenzo, Assigned: gerard)

Tracking

unspecified
2.1 S6 (10oct)
ARM
Gonk (Firefox OS)
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(blocking-b2g:2.1+, firefox33 wontfix, firefox34 wontfix, firefox35 fixed, b2g-v2.0 affected, b2g-v2.1 fixed, b2g-v2.2 verified)

Details

(Whiteboard: [systemsfe])

Attachments

(2 attachments, 2 obsolete attachments)

(Reporter)

Description

3 years ago
Build info
Gaia      d72f8ad53448aed577c01ff6e11d958463f261e7
Gecko     https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/2a18149b3ae8
BuildID   20140827000204
Version   32.0
ro.build.version.incremental=110
ro.build.date=Fri Jun 27 15:57:58 CST 2014
B1TC00011230

STR
1. Flash your device to the latest eng build
2. Open settings, Device info and check for update
3. When the update notification appears, download the stage update

Actual result:
The stage app shows the error icon and you get this single line in logcat:
> E/GeckoConsole( 291): Content JS INFO at app://system.gaiamobile.org/js/updatable.js:106 in AppUpdatable.prototype.errorCallBack: downloadError event, error code is NO_DOWNLOAD_AVAILABLE

Comment 1

3 years ago
This is blocking all testing on Marketplace. Fabrice, any ideas?
Severity: normal → blocker
Flags: needinfo?(fabrice)

Updated

3 years ago
Priority: -- → P1

Updated

3 years ago
Summary: [2.0] Cannot download the Stage Marketplace update: NO_DOWNLOAD_AVAILABLE → Cannot download the Stage Marketplace update: NO_DOWNLOAD_AVAILABLE

Updated

3 years ago
See Also: → bug 1059539

Updated

3 years ago
Blocks: 897156
(Assignee)

Updated

3 years ago
Assignee: nobody → lissyx+mozillians
(Assignee)

Comment 2

3 years ago
So, several things: NO_DOWNLOAD_AVAILABLE only comes after a first error and retrying. The first error I got doing the STRs was: INVALID_SIGNATURE. This was fixed by toggling the use of reviewers certificates in the developper options. Then, I got a new error: INSTALL_FROM_DENIED. This one is coming from: http://hg.mozilla.org/mozilla-central/annotate/5bd6e09f074e/dom/apps/Webapps.jsm#l3561

In this case, aIsSigned=true and isSignedAppOrigin=false
(Assignee)

Comment 3

3 years ago
With Marketplace reviewer certificates AND adding the pref:

> user_pref("dom.mozApps.signed_apps_installable_from", "https://marketplace.firefox.com,https://marketplace.allizom.org");

I can download and apply the update properly.
(Assignee)

Updated

3 years ago
Blocks: 1070932
(Reporter)

Comment 4

3 years ago
(In reply to Alexandre LISSY :gerard-majax from comment #3)
These prefs work for me. I am able to download the lastest Marketplace and go to the new homepage.

Krupa, do you know who we should ping to make this kind of changes? Thanks!
Flags: needinfo?(krupa.mozbugs)

Comment 5

3 years ago
If the pref fixes it, we can add it to the add-on we use for testing already: https://addons.mozilla.org/en-US/firefox/addon/dev-marketplace/

Comment 6

3 years ago
(In reply to Andy McKay [:andym] from comment #5)
> If the pref fixes it, we can add it to the add-on we use for testing
> already: https://addons.mozilla.org/en-US/firefox/addon/dev-marketplace/

We don't use the add-on on FirefoxOS. We should have that pref automatically set for eng builds.
Flags: needinfo?(krupa.mozbugs)
(Assignee)

Comment 7

3 years ago
This will make all eng build allowing signed apps from the dev instance of marketplace.
Flags: needinfo?(krupa.mozbugs)
(Reporter)

Comment 8

3 years ago
Would setting the prefs in comment 3 in the engineering build be a security issue?
Flags: needinfo?(ptheriault)
(In reply to Johan Lorenzo [:jlorenzo] from comment #8)
> Would setting the prefs in comment 3 in the engineering build be a security
> issue?

The only risk would be that if someone compromised apps on the marketplace.allizom.org, they could issue compromised updates to phones with engineering builds. This would only affect eng phones which apps installed from https://marketplace.allizom.org, and only if they enabled the reviewer certificate (iiuc the above comments correctly). So seems like low risk for what is essential functionality - i.e I don't see any reason not to enable the prefs in comment 3 by default for eng builds.
Flags: needinfo?(ptheriault)
(Assignee)

Comment 10

3 years ago
Thanks paul, I'll implement this.
Flags: needinfo?(krupa.mozbugs)
Flags: needinfo?(fabrice)
(Assignee)

Updated

3 years ago
Summary: Cannot download the Stage Marketplace update: NO_DOWNLOAD_AVAILABLE → Update for Stage marketplace cannot be installed
(Assignee)

Comment 11

3 years ago
Created attachment 8496764 [details] [diff] [review]
Add settings/pref mapping for signed apps origins

For testing purpose, we need to add the stage marketplace instance as a
valid source for signed apps. We do this by setting the pref value when
building the Gaia engineering profile.
(Assignee)

Comment 12

3 years ago
Created attachment 8496765 [details] [diff] [review]
Add settings/pref mapping for signed apps origins r=fabrice

For testing purpose, we need to add the stage marketplace instance as a
valid source for signed apps. We do this by setting the pref value when
building the Gaia engineering profile.
(Assignee)

Updated

3 years ago
Attachment #8496764 - Attachment is obsolete: true
(Assignee)

Comment 13

3 years ago
Created attachment 8496767 [details] [review]
Gaia build system PR
Attachment #8496767 - Flags: review?(ricky060709)
(Assignee)

Updated

3 years ago
Attachment #8496765 - Flags: review?(fabrice)
(Assignee)

Updated

3 years ago
Component: Integration → Gaia::Build
Product: Marketplace → Firefox OS
Version: Avenir → unspecified
(Assignee)

Comment 14

3 years ago
Created attachment 8496808 [details] [diff] [review]
Add settings/pref mapping for signed apps origins r=fabrice

For testing purpose, we need to add the stage marketplace instance as a
valid source for signed apps. We do this by setting the pref value when
building the Gaia engineering profile.
(Assignee)

Updated

3 years ago
Attachment #8496765 - Attachment is obsolete: true
Attachment #8496765 - Flags: review?(fabrice)
(Assignee)

Updated

3 years ago
Attachment #8496808 - Flags: review?(fabrice)
Attachment #8496808 - Flags: review?(fabrice) → review+
Comment on attachment 8496767 [details] [review]
Gaia build system PR

It looks good to me. r=@RickyChien thanks!
Attachment #8496767 - Flags: review?(ricky060709) → review+
(Assignee)

Comment 16

3 years ago
Flagging for cross checking by QA once landed. Please note that we will first checkin the Gecko patch and then merge the Gaia code.
Flags: needinfo?(jlorenzo)
Keywords: checkin-needed
(In reply to Alexandre LISSY :gerard-majax from comment #16)
> Flagging for cross checking by QA once landed. Please note that we will
> first checkin the Gecko patch and then merge the Gaia code.

also gaia pr has landed now in https://github.com/mozilla-b2g/gaia/commit/b9d5e5cda6e9fe38fd2b6c25699b3d249e2ea8a7
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Reporter)

Comment 20

3 years ago
Verified (Stage app can now be update if you check the option "Use Marketplace reviewer certs") on:
Gaia-Rev        0e280591881d44b80f456bc27e12d9114c218868
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/14665b1de5ee
Build-ID        20141001040205
Version         35.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141001.071459
FW-Date         Wed Oct  1 07:15:10 EDT 2014
Bootloader      L1TC10011800

When it was found on 2.0, Krupa, you marked that bug as blocker. I don't think we can uplift to that branch anymore. Do you still want an uplift to 2.1? If so, please toggle the blocking-b2g flag.
Status: RESOLVED → VERIFIED
status-b2g-v2.0: --- → affected
status-b2g-v2.1: --- → affected
status-b2g-v2.2: --- → verified
Flags: needinfo?(jlorenzo) → needinfo?(krupa.mozbugs)

Comment 21

3 years ago
[Blocking Requested - why for this release]: we can't test for updates to 2.1 devices, which means QA can't sign off on the update mechanism for the Marketplace.
blocking-b2g: --- → 2.1?

Comment 22

3 years ago
(In reply to Andy McKay [:andym] from comment #21)
> [Blocking Requested - why for this release]: we can't test for updates to
> 2.1 devices, which means QA can't sign off on the update mechanism for the
> Marketplace.

agreed. This needs to be uplifted for 2.1
Flags: needinfo?(krupa.mozbugs)
How did we test this on 2.0 given 2.0 is affected?
blocking-b2g: 2.1? → 2.1+
(In reply to krupa raj[:krupa] from comment #22)
> (In reply to Andy McKay [:andym] from comment #21)
> > [Blocking Requested - why for this release]: we can't test for updates to
> > 2.1 devices, which means QA can't sign off on the update mechanism for the
> > Marketplace.
> 
> agreed. This needs to be uplifted for 2.1

Please seek aurora approval on this to get this landed on 2.1
status-firefox33: --- → wontfix
status-firefox34: --- → affected
status-firefox35: --- → fixed
Target Milestone: --- → 2.1 S6 (10oct)
Whiteboard: [systemsfe]
(In reply to bhavana bajaj [:bajaj] from comment #24)
> Please seek aurora approval on this to get this landed on 2.1

b2g34 now
status-firefox34: affected → wontfix
Flags: needinfo?(lissyx+mozillians)
(Assignee)

Comment 26

3 years ago
Comment on attachment 8496767 [details] [review]
Gaia build system PR

[Approval Request Comment]
[Bug caused by] (feature/regressing bug #):
[User impact] if declined: QA cannot update the Stage Marketplace app
[Testing completed]: verified by QA, landed on master for two weeks and not regressing
[Risk to taking this patch] (and alternatives if risky): low, it just set a pref for PRODUCTION=0 builds used by QA
[String changes made]: none
Flags: needinfo?(lissyx+mozillians)
Attachment #8496767 - Flags: approval-gaia-v2.1?
(Assignee)

Comment 27

3 years ago
Comment on attachment 8496808 [details] [diff] [review]
Add settings/pref mapping for signed apps origins r=fabrice

NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): 
User impact if declined: QA cannot apply Stage marketplace update
Testing completed: landed on master for two weeks, no regression
Risk to taking this patch (and alternatives if risky): low, we just add a new pref/setting mapping that is being used by PRODUCTION=0 gaia builds to add new origin from which we allow signed apps
String or UUID changes made by this patch: none
Attachment #8496808 - Flags: approval-mozilla-b2g34?
Attachment #8496808 - Flags: approval-mozilla-b2g34? → approval-mozilla-b2g34+
Attachment #8496767 - Flags: approval-gaia-v2.1? → approval-gaia-v2.1+
The build test covers this IMO.
Flags: in-testsuite+
You need to log in before you can comment on or make changes to this bug.