Testing the next release of MIT App Inventor (nb187)

[BeksOmega]

I think specifically this tag: https://github.com/mit-cml/appinventor-sources/tree/v187

[TIMAI2]

Mere mortals cannot see that "branch" - probably for good reason

[ewpatton]

The v187 tag (as linked by @BeksOmega) is the closest you can get to seeing the nb187 sources. When we do a release, we tag the open source version with the v### tag and then apply our private branding (Terms of Service, private keys, etc.), and that becomes the corresponding version put on ai2.appinventor.mit.edu.

[Salman_Dev]

@ewpatton

is the closest you can get to seeing the nb187 sources.

Thank you very much for the info MIT Team

I MIT

[Anke]

Here is a test APK that only works with the File component (no extension is used):

copyMoveASDtoShared_2.apk

Tested on Android 11 (Pixel 2XL).

Bugs:

1. File.Exists from assets does not work with the APK (Companion works).
   

2. WRITE permission must be declared in the Manifest so that it works after the automatic request of storage permission.
   If the permission is denied:
   "Error 908: The permission READ_/WRITE_EXTERNAL_STORAGE permission has been denied. Please ..." depending on which action is carried out.
   If the permission is granted, however, it works, although WRITE permission can of course no longer be granted under Android 11, since it no longer exists there.

3. All shared folders work without problems, except /Documents.
   The folder /Download works with all file types (txt, jpg, mp3, ogg, mp4, ...).
   Non-media files (like .txt) should only work with /Download and /Documents.
   

   
   

[Anke]

[Patryk_F]

I don't have an android11 device. Should android10 also allow writing to shared folders without write permission? I wanted to test the write, but components that write anything ask for write permission.

[Taifun]

@Patryk_F

Should android10 also allow writing to shared folders without write permission?

yes...
therefore the permission should be defined like this

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

see also @Anke's tests, for example this one

Release nb187: Copy a text file / image from assets to shared storage (→ Android 10+)

Here is a test app (→ Designer: DefaultFileScope = Shared) with which a text file and an image can be copied from the assets to the shared storage (for devices with Android ≥ 10). This works neither for the text file nor for the image (regardless of whether storage permission was granted beforehand): "Error 908: The permission WRITE_EXTERNAL_STORAGE has been denied. Please enable ...". Note: With → Niotron the text file is copied to shared storage (without permission), but you need READ p…

Taifun

[Patryk_F]

This should have been the first easy fix to nb187 to facilitate further testing on all devices.

[Anke]

@Patryk_F

Should android10 also allow writing to shared folders without write permission?

The point here is not whether or not WRITE permission is granted, just whether WRITE is declared in the Manifest. As I said several times, WRITE can no longer be granted under Android 11.

@Taifun

therefore the permission should be defined like this

Yes, see also here:

Release nb187: Copy a text file / image from assets to shared storage (→ Android 10+)

By the way, I've already mentioned that several times before:

If requestLegacyExternalStorage for Android 10 is not used, then set maxSdkVersion to 28, otherwise to 29.

Android 11 and Storage-File

On Android 10 devices requestLegacyExternalStorage will continue to work regardless of targetSdk On Android 11 devices for new apps targeting SDK 30 requestLegacyExternalStorage is ignored / false.

[Patryk_F]

My question is, does android10 allow writing to shared folders without write permission? Same as in ASD.

[Taifun]

short answer yes
long answer: see again here Testing the next release of MIT App Inventor (nb187)

Taifun

[Patryk_F]

OK thanks. So we should also remember about android 10 during corrections, so that the app does not ask for permissions when we do not have the scope set on Legancy.

[SRIKAR_B.S.S]

@ewpatton
With this nb187 release can we edit our package name for our app ??

[Taifun]

@SRIKAR_B.S.S

can we edit our package name for our app

no... why do you think so?
see also the release notes Release Notes for MIT App Inventor 2

Taifun

[SRIKAR_B.S.S]

hmm, that is a quite not nice
it would be very better if they would add this.
I thought because every other app builder except AI2

---

if anyone wants this feature then like this post
so that MIT Team can add it very soon in the next release(nb188)

[Patryk_F]

From what I can see it's not. Jarlisson did not make the appropriate corrections, and it seems he is no longer an active user / developer in ai2.

[Know_About_IT]

Sad to know aar support and native libraries support wont be added in nb187

We extension devs know pain of aar libraries

~ Sed lyf

[AkshatRana]

I don't know much about this that how hard it is but i think MIT should focus on their extension developers too as aar support can make a revolutionary effect on extension development history also in latest release of Niotron they had added AAR support so it won't be difficult for either MIT to add aar support... This was my opinion on this .

~ Akshat

[Know_About_IT]

Seriously, wont lie, my almost 15+ aixs are done, ready but, just because of lack of aar suport,

it doesnt work