Testing the next release of MIT App Inventor (nb187)

It appears MIT has taken the build for the test server offline in anticipation of releasing nb187 . nb187 will be able to build an aab. The normal build server works for nb186.

MIT indicated late yesterday it intended to release nb187 following the passing of hurricane Henri . MIT facilities are near the path of the storm. Sometime after the storm passes, MIT will upload nb187. When exactly? Be patient. When the new version is released will depend whether storm damage affects App Inventor operations. :slight_smile:

3 Likes

Yes, maybe, but we should have been given the opportunity to test it on the test server until the very end.

I'm pretty sure that there will be issues / bugs with the File component and also with READ / WRITE permissions after the targetSdkVersion = 30 update. I have done a number of tests with Niotron and (also) found some serious issues / bugs there.

I don't think there was a release yet that would not have even the slightest mistake. If there are any, I think a bugfix version will be released soon.

I'm not talking about a "slightest mistake" but serious bugs.

its released..

As I suspected:

See also here:

Note that you can still use Legacy mode in these situations while we work on fixing the issues with shared scope storage.

At least the apps will be safer for users :grin:

See here:

A post was split to a new topic: How to store and share a text file in new release?

A post was split to a new topic: To upload an AAB you must be registered on Play App Signing."

how can i see nb187 source code??

@Salman_Dev Probably https://github.com/mit-cml/appinventor-sources

1 Like

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

2 Likes

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

3 Likes

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.

3 Likes

:heart_eyes: :heart_eyes: :heart_eyes:

Thank you very much for the info MIT Team :kissing_heart:

I :heart: MIT

3 Likes

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

Tested on Android 11 (Pixel 2XL).

Bugs:

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

  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.

1 Like

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.