Testing the next release of MIT App Inventor (nb187)

[Anke]

@Taifun

the tests in the companion app did not result in any error... also the files could be copied and deleted as previously

1. If the file "foto.jpg" already exists in the folder /Download then it is possible to copy it to "foto.jpg" or → foto2.jpg:
   

   
   
   
   

2. If "foto.jpg" does not exists in the folder /Download:
   

   
   
   
   

@ewpatton

If you uninstall and reinstall the companion, it should lose the exception and behave similarly to the compiled APK.

No, un- / reinstalling Companion app doesn't change anything.
It behaves in exactly the same way - as described above.

But if I create the APK and run it, it is (of course) not possible to write (save, copy) to /Download (because on Android 11, targetSdk=30), WRITE permission is ignored - does no longer exists).

So for the Companion app WRITE permission might be declared this way (to avoid this issue with Companion):

<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="28" />

as I already I mentioned here:

File component - save (all types of) files in the Private dir (→ internal storage)

It is currently not possible to request READ or WRITE permissions, because the File component (incorrectly) no longer declares these permissions in Manifest. But it should do it like this: <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="28" /> I checked it on Android 9 after declaring the permissions in the Manifest.