It’s 31, but effectively 32 
Ok I understand. This means that then the File component in particular will be adapted to the new file system (Scoped / Shared storage). And also all other components that can store something. Is that correct?
If so, then I really hope that the same bugs will not be present as with AI2, which I have reported countless times over the past few months.
1 Like
Obviously not. In addition, the bugs with the File component were not fixed. Among other things, it is not possible to copy or move files.
This hotfix is no longer in effect since Fenix 1.5.5. Full SDK 30 support has been added.
SDK 31 will arrive in a few weeks, to comply with Google Play Store deadlines.
1 Like
Have I misunderstood something here? → An update from Kodular Staff
At a glance, this update will bring Target SDK 32 , and will (finally) integrate the new Android file system, so all related bugs to that problem should be solved. It will also include new features and minor improvements as well.
But it will also finally deprecate Google Admob components, as they will no longer be available, even for existing apps. Thus, migration to Google Ad Manager shall be mandatory by that date if you want your app to target Android 12.
We are aiming to launch this update on the 26th of June 2022. We will keep the community up-to-date if this changes at any point.
1 Like
I tried to test the new file system. First of all with the File component. As soon as I drag it into the Designer, I get an error message (Firefox & Chrome):
Firefox:
Chrome:
4 Likes
It is also not possible to click on it (same error) and there are no Properties / permissions displayed at all. The same after reloading / refreshing (browser) multiple times.
1 Like