Closed
Bug 960601
Opened 11 years ago
Closed 11 years ago
Installing privileged app with origin in the manifest doesn't work
Categories
(Core Graveyard :: DOM: Apps, defect)
Core Graveyard
DOM: Apps
Tracking
(blocking-b2g:1.3+, firefox27 wontfix, firefox28 fixed, firefox29 fixed, b2g-v1.3 fixed, b2g-v1.3T fixed, b2g-v1.4 verified)
People
(Reporter: macajc, Assigned: macajc)
References
Details
(Keywords: regression, Whiteboard: [systemsfe])
Attachments
(1 file, 1 obsolete file)
(deleted),
patch
|
fabrice
:
review+
|
Details | Diff | Splinter Review |
STR:
1. Install any priviledged app from the marketplaces that specifies an origin on the manifest. For example the own marketplace app has that field on the manifest.
Expected:
The app is correctly installed and it has the correct origin
Actual:
The app isn't installed and there is an exception on the logcat:
E/GeckoConsole( 7224): [JavaScript Error: "Error while reading package:ReferenceError: app is not defined" {file: "resource://gre/modules/Webapps.jsm" line: 2981}]
This is a regression from bug 910815.
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #8361196 -
Flags: review?(fabrice)
Assignee | ||
Comment 2•11 years ago
|
||
Requesting block because this is a regression that landed in 1.3 and without this patch it would not be possible to install any priviledged apps with a custom origin on 1.3.
blocking-b2g: --- → 1.3?
Updated•11 years ago
|
Whiteboard: [systemsfe]
Comment 3•11 years ago
|
||
Comment on attachment 8361196 [details] [diff] [review]
Proposed patch - v1
Review of attachment 8361196 [details] [diff] [review]:
-----------------------------------------------------------------
lgtm, but we need tests to not regress that again.
Attachment #8361196 -
Flags: review?(fabrice) → feedback+
Comment 4•11 years ago
|
||
(In reply to Fabrice Desré [:fabrice] from comment #3)
> Comment on attachment 8361196 [details] [diff] [review]
> Proposed patch - v1
>
> Review of attachment 8361196 [details] [diff] [review]:
> -----------------------------------------------------------------
>
> lgtm, but we need tests to not regress that again.
Shouldn't those tests be part of bug 880043? (Or they can be added after bug 880043 lands, since they're also signed packaged apps).
The other way to test this would be cheating a little bit... and testing it for Operator Single Variant Apps (aka locally installed apps) for which the signature verification is relaxed.
Updated•11 years ago
|
blocking-b2g: 1.3? → 1.3+
Comment 5•11 years ago
|
||
(In reply to Antonio Manuel Amaya Calvo (:amac) from comment #4)
> The other way to test this would be cheating a little bit... and testing it
> for Operator Single Variant Apps (aka locally installed apps) for which the
> signature verification is relaxed.
That would be better to have than having no tests at all. Can we add tests following this approach then?
Updated•11 years ago
|
Comment 6•11 years ago
|
||
I have added a test case for this on bug 880043 (on review now). As such, that bug depends on this being fixed now (since that test fails --correctly-- if this isn't fixed).
Assignee | ||
Comment 7•11 years ago
|
||
Resubmiting for review as per comment 6
Attachment #8361196 -
Attachment is obsolete: true
Attachment #8363702 -
Flags: review?(fabrice)
Updated•11 years ago
|
Target Milestone: --- → 1.3 C3/1.4 S3(31jan)
Updated•11 years ago
|
Attachment #8363702 -
Flags: review?(fabrice) → review+
Assignee | ||
Comment 8•11 years ago
|
||
There is a green try run which included this patch and the unit test written at bug 880043 for it at:
https://tbpl.mozilla.org/?tree=Try&rev=e9cc593d8df8
Requesting checkin
Keywords: checkin-needed
Comment 9•11 years ago
|
||
Keywords: checkin-needed
Comment 10•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 11•11 years ago
|
||
status-b2g-v1.3:
--- → fixed
status-b2g-v1.4:
--- → fixed
status-firefox27:
--- → wontfix
status-firefox28:
--- → fixed
status-firefox29:
--- → fixed
Comment 12•11 years ago
|
||
I downloaded and installed a variety of apps on my device that have origins in the manifests, and they all worked fine for me. Are there any specific apps that should be tested?
Tests run on todays master build: (2014/2/19)
Environmental Variables:
Device: Buri v1.4 Moz RIL
BuildID: 20140219040204
Gaia: ac06cfbd2baf6494ffbb668cc599e3892cd5e17b
Gecko: bf0e76f2a7d4
Version: 30.0a1
Firmware Version: v1.2-device.cfg
Status: RESOLVED → VERIFIED
Updated•11 years ago
|
Comment 13•11 years ago
|
||
(In reply to rkuhlman from comment #12)
> I downloaded and installed a variety of apps on my device that have origins
> in the manifests, and they all worked fine for me. Are there any specific
> apps that should be tested?
>
> Tests run on todays master build: (2014/2/19)
> Environmental Variables:
> Device: Buri v1.4 Moz RIL
> BuildID: 20140219040204
> Gaia: ac06cfbd2baf6494ffbb668cc599e3892cd5e17b
> Gecko: bf0e76f2a7d4
> Version: 30.0a1
> Firmware Version: v1.2-device.cfg
This is not right - you need to install an app that supports the origin property. Installing random packaged apps isn't going to allow you to verify this bug.
Status: VERIFIED → RESOLVED
Closed: 11 years ago → 11 years ago
Comment 14•11 years ago
|
||
Can you provide a specific example of an app that supports this property? No apps are indicated in the comments, and the marketplace does not appear to provide this info.
Flags: needinfo?(jsmith)
Comment 15•11 years ago
|
||
(In reply to rkuhlman from comment #14)
> Can you provide a specific example of an app that supports this property? No
> apps are indicated in the comments, and the marketplace does not appear to
> provide this info.
I'll look into this - don't worry about this.
Flags: needinfo?(jsmith)
Updated•11 years ago
|
status-b2g-v1.3T:
--- → fixed
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•