Closed Bug 823224 Opened 13 years ago Closed 13 years ago

Process adnormal termination when running enumerateEditable/enumerate on device storage for pictures/music/sdcard/videos in a privileged signed packaged app

Categories

(Core :: DOM: Device Interfaces, defect)

ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 823397
blocking-basecamp +

People

(Reporter: jsmith, Assigned: gwagner)

References

Details

(Keywords: testcase)

Attachments

(3 files)

Attached file Test App
Build: B2G 18 12/19/2012 Device: Unagi Steps: 1. Install the privileged app here - https://marketplace-dev.allizom.org/app/privileged-app-test/?src=mkt-search 2. Launch the app 3. Select device storage test 4. When the perm prompt appears, select to accept perms Expected: An alert dialog should appear with an object name. Actual: An alert dialog flashes quickly with the object name, but the process crashes without a crash reporter dialog. 100% reproducible.
Severity: normal → critical
blocking-basecamp: --- → ?
Keywords: crash, testcase
Attached file Logcat
Comment on attachment 694031 [details] Logcat The interesting part is : 12-19 15:53:41.746: I/IdleService(2627): Reset idle timeout: tell observer 48447510 user is back 12-19 15:53:41.846: I/GeckoDump(2627): XXX FIXME : Got a mozContentEvent: permission-allow 12-19 15:53:41.886: I/Gecko(2627): Security problem: Content process does not have `device-storage:pictures-read' permission. It will be killed. Can you post the app manifest?
{ "version": "1.1", "name": "New Privileged App", "description": "A different privileged app", "launch_path": "/privilegedapp.html", "icons": { "126": "/qalogo.png" }, "type": "privileged", "permissions": { "device-storage:pictures": { "access": "readwrite", "description": "Come see my device storage" }, "contacts": { "access": "readwrite", "description": "Come see my contacts" } }, "developer": { "name": "Mozilla QA", "url": "http://quality.mozilla.org" } }
Wait a second. That's not the right one. Let me find the right one...
{ "version": "1.1", "name": "Privileged App Test", "description": "Testing a privileged app", "launch_path": "/privilegedapp.html", "icons": { "126": "/qalogo.png" }, "type": "privileged", "permissions": { "device-storage:pictures": { "access": "readwrite", "description": "Come see my device storage" }, "contacts": { "access": "readwrite", "description": "Come see my contacts" } }, "developer": { "name": "Mozilla QA", "url": "http://quality.mozilla.org" } }
Keywords: crash
Summary: Crash when running enumerateEditable on device storage for pictures in a privileged signed packaged app → Process adnormal termination when running enumerateEditable on device storage for pictures in a privileged signed packaged app
Is this happening with enumerate() too? We should really just remove enumerateEditable and getEditable since they don't really work right now anyway (since we don't have FileHandle support yet)
(In reply to Jonas Sicking (:sicking) from comment #6) > Is this happening with enumerate() too? We should really just remove > enumerateEditable and getEditable since they don't really work right now > anyway (since we don't have FileHandle support yet) Yes. I just tested it with: https://marketplace-dev.allizom.org/app/test-privileged-webapi It fails with pictures, music, sdcard, and videos. Which gets me the feeling it's not really working at all.
Summary: Process adnormal termination when running enumerateEditable on device storage for pictures in a privileged signed packaged app → Process adnormal termination when running enumerateEditable/enumerate on device storage for pictures/music/sdcard/videos in a privileged signed packaged app
Attached file Second Test App
This is probably a symptom of bug 823397
(In reply to Fabrice Desré [:fabrice] from comment #9) > This is probably a symptom of bug 823397 Makes sense. Let's retest when that lands.
Depends on: 823397
Hopefully this is simply a dupe of bug 823397. Definitely a blocker though.
Assignee: nobody → anygregor
blocking-basecamp: ? → +
I confirm that bug 823397 fixed this.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: