Test 1) Uploaded the files to assets, compiled and installed the app: Using the Total Commander I can not get access to the assets. Good, but it has some disadvantages.
Test 2) Defined a web component to download the files, compiled and installed the app: Using the Total Commander I can get access to the files under /storage/emulated/0/Android/data/appinventor.ai_myusername.AppName/files
Test 3) Defined a web component to download a ZIP file which will be unzipped using Taifun's ZIP extension and then delete the ZIP file, so I compiled and installed the app: Using Total Commander I can get access to the files under /storage/emulated/0/Android/data/appinventor.ai_myusername.AppName/filesFTP
Since I have almost 100 files which occupies more than 200MB in total I understand that uploading these to the assets is not an option.
I can not test this with Android 10 since Total Commander is allowing me to access to just to storage/emulated/0/Android/data/
Am I missing something?, I just want to have my files available for my App and not avaible for any other 3rd party app nor the user via USB connection.
you are using file scope App... try file scope Private
see also Storage
Below we briefly describe each scope type:
App: Files will be read from and written to app-specific storage on Android 2.2 and higher. On earlier versions of Android, files will be written to legacy storage.
Asset: Files will be read from the app assets. It is an error to attempt to write to app assets as they are contained in read-only storage.
Cache: Files will be read from and written to the app’s cache directory. Cache is useful for temporary files that can be recreated as it allows the user to clear temporary files to get back storage space.
Legacy: Files will be read from and written to the file system using the App Inventor rules prior to release nb187. That is, file names starting with a single / will be read from and written to the root of the external storage directory, e.g., /sdcard/. Legacy functionality will not work on Android 11 or later.
Private: Files will be read from and written to the app’s private directory. Use this scope to store information that shouldn’t be visible to other applications, such as file management apps.
Shared: Files will be read from and written to the device’s shared media directories, such as Pictures.
if you want the web component to store something in the private storage, then you have to set the default file scope in the Screen1 properties also to Private
the correct path to the app's private directory would be as @Anke mentioned
there is no such path as file:///data/data/AI2...
I never tried this myself, so probably only the filename is required (in your case googlelogo.gif), because the path will be added automatically after setting the correct default file scope and file scope
just try the 3 different variants and let us know what you find out
I'm trying to understand how to accomplish that, in the post you mention it says without any slash, if I understood it properly then these are the results:
DefaultAppScope: App & FileScope: Private: File is accesible
DefaultAppScope: Private & FileScope: Private: File is not accesible
Download to the ASD and move it to the PrivateDir using my DownloadToASD extension and the File component or use the Fetch extension (search in @Taifun 's extension list).
