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)
Tracking
()
RESOLVED
DUPLICATE
of bug 823397
| blocking-basecamp | + |
People
(Reporter: jsmith, Assigned: gwagner)
References
Details
(Keywords: testcase)
Attachments
(3 files)
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.
| Reporter | ||
Updated•13 years ago
|
| Reporter | ||
Comment 1•13 years ago
|
||
Comment 2•13 years ago
|
||
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?
| Reporter | ||
Comment 3•13 years ago
|
||
{
"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"
}
}
| Reporter | ||
Comment 4•13 years ago
|
||
Wait a second. That's not the right one. Let me find the right one...
| Reporter | ||
Comment 5•13 years ago
|
||
{
"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"
}
}
| Reporter | ||
Updated•13 years ago
|
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)
| Reporter | ||
Comment 7•13 years ago
|
||
(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.
| Reporter | ||
Updated•13 years ago
|
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
| Reporter | ||
Comment 8•13 years ago
|
||
Comment 9•13 years ago
|
||
This is probably a symptom of bug 823397
| Reporter | ||
Comment 10•13 years ago
|
||
(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: ? → +
Comment 12•13 years ago
|
||
I confirm that bug 823397 fixed this.
| Reporter | ||
Updated•13 years ago
|
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.
Description
•