08-04-2013 10:15 PM
I'm testing my app to see if it handles file writing to the shared directory when the app permission is set to denied.
With the Playbook, everything works as expected. The app is able to write to the file when the permission is allowed. When I go in to the settings and change the permission to denied, fopen() fails and I throw up a dialog box to let the user know.
If I do the same on the DAC, the app has no problem writing to the file. I've noticed that if I keep the permission as denied and restart the device, then things work as expected, fopen() fails. Set it to allowed and it writes fine. Set it back to denied and I can still write.
This isn't a problem for me but I'm just wondering if this is how it's supposed to work in BB10. I always thought that it shouldn't.
Using native SDK. 10.2 leak. It also was happening under 10.1.