Here is a new and important post from Evan Patton (MIT team) regarding the File
component that anyone on the Kodular team should take a closer look at:
→ @Diego @pavi2410 …
opened 02:44PM - 15 Sep 21 UTC
help wanted
issue: noted for future Work
status: forum
feature request
affects: ucr
priority: medium
**Describe the desired feature**
<!--
Describe the feature that you'd like t… o see implemented for App Inventor. More detail is useful as it allows us to better understand the complexity of the task.
-->
Newer Android versions lock down file access. There is a Storage Access Framework that allows the user to pick a file from the file system and grant the app access to that one file (or directory). It would be good if we implemented a new FilePicker, similar to ImagePicker, that uses the Storage Access Framework to prompt users to pick files for creation/editing/deletion in an app, in compliance with the latest best practices for file access in Android 11+.
**Give an example of how this feature would be used**
<!--
How would a teacher or student use this feature?
-->
An example app might include loading a CSV file for doing some mathematical analysis (or charting, once #1776 is merged). Picking the file from the filesystem is presently not available in core App Inventor.
**Why doesn't the current App Inventor system address this use case?**
<!--
Explain why the use case cannot be completed using the features of the current system.
-->
Previously, one might be able to provide a path directly to a file, but newer restrictions in Android make this no longer possible. The user must give explicit access to a file outside of the app's scoped storage.
**Why is this feature beneficial to App Inventor's educational mission?**
<!--
Because MIT App Inventor is aimed at educational use, we prioritize development of features with an educational benefit. Help us understand how your feature request relates to our mission.
-->
The inclusion of the new component alleviates some pressure around file access in newer versions of Android, and can also serve as a launching off point to discuss access control, security best practices, etc.
3 Likes
CyberPunk
(Cyber Punk)
September 15, 2021, 7:53pm
#62
How come are you using api30, it was supposed to release after 7 days in India. Please correct me if I am wrong.
Omar
(Omar)
September 15, 2021, 7:56pm
#63
No, it was a joke they just changed sdk target from 29 to 30 as we was doing but nothing changed.
CyberPunk
(Cyber Punk)
September 15, 2021, 7:58pm
#64
How nothing changed? Google play accepting it or not?
Omar
(Omar)
September 15, 2021, 8:05pm
#65
yes, google play accept it but still not really target API 30, this means all bugs are still existing.
AppyStudio
(Appy Studio)
September 16, 2021, 3:26am
#66
No update is already released.
Just check, apps are now targeting to api 30.
Anil_M
(Codal Inc.)
September 16, 2021, 5:25am
#67
Where is api30 only show api29
AppyStudio
(Appy Studio)
September 16, 2021, 5:28am
#68
Its showing Minimum Api Level not Maximum Target Api Level.
Please read the description carefully.
You can check your apps target api level by using any apk info tools app.
Like this
After exporting your app from kodular.
1 Like
dora_paz
(Dora)
September 16, 2021, 5:28am
#69
From there you set minimun SDK not targeting SDK.
1 Like
minSdkVersion = 19
(Android 4.4 - 4.4.4 / KitCat)
compileSdkVersion = 30
targetSdkVersion = 30
minSdkVersion = 19 (Android 4.4 - 4.4.4 - KitCat)
compileSdkVersion = 28
targetSdkVersion = 28
You can not change the last two, only the first one to set your lowest API level on which your App can be installed.
The error only occurs on devices with API>27 (Android 9).
4 Likes
HeyAveHey
(HeyAveHey)
September 16, 2021, 3:25pm
#71
I can’t see any update in google play for Companion 1.5.2 since for 2 days since the release.
Lollipop
(Rahul)
September 16, 2021, 3:36pm
#72
You can download directly, check pinned posts
CyberPunk
(Cyber Punk)
September 16, 2021, 8:09pm
#73
Yeah, I even published it successfully. Moreover, my app is working flawlessly.
Omar
(Omar)
September 16, 2021, 9:47pm
#74
Maybe you don’t use components that makes bugs because Kodular itself said there are bugs.
Didyme_Apps
(Didyme Apps)
September 16, 2021, 10:01pm
#75
This is boring and desperate. There are many bugs and their causes are difficult to find. Apps that worked very well, now have many fails. Better to wait for to Kodular release a more stable version similar to the last update. I hope that it will be as soon as possible.
pkdev585
(pk)
September 17, 2021, 3:25am
#76
Push notification component not working
1 Like
pavi2410
(Pavitra Golchha)
April 23, 2022, 10:20am
#80
New major update coming soon which targets API 30 (Android 11). And in later updates, we will target API 32.
6 Likes
I’m not sure if I understand that correctly. Kodular is already using targetSdkVersion = 30
(ie targeting Android 11).
Don’t you mean targetSdkVersion = 31
(Android 12) or Android 12L (SDK/API = 32
)?
Diego
(Diego Barreiro Pérez)
April 24, 2022, 2:15am
#82
Yes, but that Target SDK does not really support Android 10 (file system issues). We are finally fully implementing Target SDK 30 with its full support for the new file system in Android apps.
4 Likes