well, it is working on my Samsung A51 device running Android 10 and your device (what do you have and which Android version?) using this path to the assets /storage/emulated/0/Makeroid/assets
and as @Boban pointed out, there is a big mess concerning the path to the assets for the companion app depending on Android version and probably more, see the different paths for Android 10…
it would be good to know, which rule to follow to get a working solution for all devices and Android versions…
And version 13a now uses only this path, because as of today this was the path I got for my Android 10 device… /storage/emulated/0/Makeroid/assets/
Taifun
PS: I’m aware, that this will not be the final solution… still trying to understand the correct rule to be able to provide a solution for all devices and Android versions
I wanted to import TaifunFile and it tells me an error on TaifunZip!?! If I delete the extension before importing the new one, all the blocks of this extension are deleted. How to do. thank you in advance
Yes, good question.
But it would be just as good to ask why not leave it at “Makeroid” for Android < 10, instead of changing this for the second time and causing confusion (not least with regard to extensions).
The assets are stored just like App Inventor now, except that “AppInventor” in the path has been replaced by “Kodular” in order to prevent conflicts with the MIT App Inventor companion.
Edit:
Every occurrences of “Makeroid” has now been replaced with “Kodular”
@Boban@bodymindpower@Taifun Could you please test the asset path behaviour with the beta server? I need to ensure that changes made for Android 11 requirement don’t break the functionality.
@pavi2410 please first describe, what exactly has been changed and for which Android versions @bodymindpower it seems to be, you are testing with a device older than Android 10? it might be easier to understand your test results if you could add, whether the result of a test was as expected or not…
