WAI
Status Update
No update yet.
Comments
sb...@opera.com
Hello,
Product team is working and evaluating this case. Once there will be information, it will be shared in this thread.
Kind Regards
vk...@google.com
na...@google.com
na...@google.com
Also in
sb...@opera.com
Yes, that's the section I was thinking about.
I guess this is part of the confusion. I've interpreted Scoped storage to mean "only allow access to predefined set of folders, and only by using the MediaStore", and that being enforced by the fact that "both the WRITE_EXTERNAL_STORAGE permission and the WRITE_MEDIA_STORAGE privileged permission no longer provide any additional access." But perhaps it is actually something like "application has access to specific folders (Downloads, Video, Music, Image) without the need to request broad storage permission, either via MediaStore or via direct file access."
I guess this is part of the confusion. I've interpreted Scoped storage to mean "only allow access to predefined set of folders, and only by using the MediaStore", and that being enforced by the fact that "both the WRITE_EXTERNAL_STORAGE permission and the WRITE_MEDIA_STORAGE privileged permission no longer provide any additional access." But perhaps it is actually something like "application has access to specific folders (Downloads, Video, Music, Image) without the need to request broad storage permission, either via MediaStore or via direct file access."
ti...@gmail.com
direct file access
na...@google.com
Regarding
sb...@opera.com
Thanks for clarifying, and great that it also reaches the docs team.
Description
Yes
* Which Android Developer Preview build are you using? See Settings > About phone > Build number (for example RPP1.200123.000).
RPP2.200227.014
* Is this a regression from Android 10 to 11?
Not applicable
* What device are you using? (for example, Pixel 3 XL)
Pixel 3a
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
1. Build an app defining READ and WRITE_EXTERNAL_STORAGE permission
2. Toggle ON FORCE_ENABLE_SCOPED_STORAGE for app
3. In the app, ask the user for storage permission. The dialog that pops up says "Allow App to read this device's media files?"
4. Grant the access
5. Now try to write a file to the directory from Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_DOWNLOADS) directory.
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Scoped storage
* What was the expected result?
Unclear, since it is not clear what limitations scoped storage in practice will actually incur given that the observed behavior (allowing write access to Downloads) seems to contradict what is documented at
* Can you provide the API document where this expected behavior is explained?
* What was the actual result?
Allowed write access to Downloads.
Note: from our point of view we don't actually mind the continued access to Downloads since it allows us to use existing code, but given the focus and how the platform is moving towards scoped storage we've been trying to get onboard early in this Developer Preview phase to be able to provide feedback/requests in case the behavior causes unavoidable issues. The confusing behavior seen makes it tricky to assess if we will be able to manage with the existing APIs.