Yes that's right. But why shouldn't it still be possible to access (read / list) files* from the external storage (outside the ASD)?
→ (* btw, on Android 10+ you can only access media files)
However, this is only possible if DefaultFileScope = Legacy.
Same answer / question as before.
What does this exactly mean?
(Of course READ can be requested on any Android version.)
Apparently, it is implicitly assumed that if DefaultFileScope is NOT set to Legacy, only files in the ASD (or, if applicable, the shared storage) should be accessed. So again: Why shouldn't it also be possible to access the external storage on devices with Android 4.4 and up? (e.g. with DefaultFileScope = App) The big disadvantage would then be that from Android 4.4 (API 19) onwards, READ / WRITE permissions can no longer be requested. However, this should be possible.
It is not clear to me where the advantage / sense should be to set maxSdkVersion = 18. Because READ permission can be requested on all Android versions (independent of and therefore also with targetSdkVersion = 30). Of course WRITE permission does no longer exist on Android 29+ and is therefore ignored on Android 29+ devices.
The only disadvantage (not setting maxSdk=18) would be that on devices between Android 4.4 (API 19) and Android 5.x (API 22) READ / WRITE is requested at install-time (which hardly anyone will notice and which was also the case before).
In my opinion, the permissions for all DefaultFileScopes should be declared like this (btw, also with Companion):
Specifies the default scope for file operations by different components. For the File component, the File's DefaultScope property overrides this property. For all other components, their paths are resolved based on the value of this property. The default value of this property will be App.
You still want to be able to decide, if for example the camera component stores its taken images in the ASD or a shared directory...
Yes, I already understood that (from the idea). But unfortunately that doesn't work for most scopes (only for Legacy). So I thought you should use the same way as before (namely Legacy) for all components (except the File component) that can write and / or read.
Apart from that, if DefaultFileScope was NOT set to Legacy in the Designer, READ permission can no longer be requested from API 19+. So you can no longer access e.g. any image or audio file from the external storage. This should / must be possible in principle (on all Android versions).
However, if it were possible (and it should actually be possible) to store / read media files in shared storage, then there should actually be a way to select this option. But even in this case there should still be the possibility to access / read all (media) files - also from the external storage, outside the ASD - (note: from Android 10+ devices can only access media files).
I did a lot of tests with different scopes (Android 11, APK). Try e.g. these blocks after varying the DefaultFileScope in the designer. Build the APKs and check ...
Maybe add some menu to the designer, in which the user would decide what permissions to add to the manifest? Also for Internet permissions etc. I noticed that some people don't want these permissions and as Google suggests, they only want to use the permissions they need.
When we talk about permissions, we basically mean dangerous permissions. Not dangerous permissions (like Internet etc.) are always declared and granted. As of API 23 (Android 6), the user does not notice that Internet permission etc. has been granted. These "not dangerous" permissions are only displayed on devices with an API < 23, since all permissions there are granted at install-time.
At DefaultFileScope, we're only talking about READ / WRITE permissions. And as I said several times, it should be possible to request READ permission on all Android versions (i.e. on Android 10+). WRITE permission only up to Android 9.
A positive note:
I was able to copy an audio file from the assets into the privateDir (with the File component) and play it from there with the Player component (of course without READ / WRITE permissions). Therefore it should also be possible to first download (audio) files to the ASD, then move them to the privateDir (copy / delete) and play them from there.
This could circumvent the problem of the AIA limitation to 30 MB and thus save sensitive files in the internal storage, which users would only have access to with a rooted device.
Note: I haven't found a way to decompile an AAB yet. This would be very helpful for adding (large, many) assets later ... as has been possible with the APK so far (see here).
Unless I have missed the discussion somewhere, webviewer cannot read / access files in media/storage on Android 11 device - specifically the /Download folder. Webviewer returns net::ERR_ACCESS_DENIED. Tested with companion and compiled from the test server.
if I understand it correctly, then theoretically it would be possible to use the Storage Access Framework to access documents and other files... see also here
I do not see an issue using mp3 files which are stored in a subfolder of /Music. These are read only and work fine in my AI2 mp3 player app. I also understood that "other" files could be stored in Documents or Downloads and that these too would be read only for apps...
Q: I can put non-media files into other folders, such as Downloads, without any permission. Is this a bug?
A: No. Apps may contribute files to these collections, and the use of both Downloads and Documents collections for non-media files is a best practice. However, keep in mind that only the app that created the files can access them by default.
which means, the webviewer can or should be able to read/access files in the /Downloads folder, but only if the app created those files... but it should be /Downloads and not /Download ... maybe you can test that again @TIMAI2...
This where it gets interesting...I only have a physical Download folder. This does, however, show up in the "media" folder Downloads when I use the "Files" app. I can see the files I placed...
The first was created on the AI2 build server (targetSdk = 29).
The second on the AI2 test server (targetSdk = 30).
Steps:
First install saveTestFile_API30.apk and test.
Now install saveTestFile_API29.apk and test.
Now install saveTestFile_API30.apk and test.
Then you will probably understand. The aha moment should come at step 3.
Note: I have to decompile the APK from the test server (to get the correct keystore because the AI2 test server does not use the same keystore as the AI2 server).
