Means the path to the assets on Android 11 with Companion is still:
/storage/emulated/0/Makeroid/assets/
Means the path to the assets on Android 11 with Companion is still:
/storage/emulated/0/Makeroid/assets/
It works. thank you very much
/storage/emulated/0/Kodular/assets/
This is the path to the assets on Beta
server for API < 29 (→ Companion).
So this path is changed for the second time:
One thing to note in this update is that the assets when using companion are now saved at /sdcard/Makeroid/ dir, instead of /sdcard/AppInventor/ dir. Your WebViewer’s GoToUrl function will work even when AppInventor dir is specified as it is replaced internally to use Makeroid dir. This only breaks @Taifun’s PathToAssets block with Makeroid well, that’s a bad idea to rename that directory Makeroid is an App Inventor distribution, isn’t it? so why renaming the directory? it does not make se…
The path to assets for API ≥ 29 (→ Beta
server) is:
/storage/emulated/0/Android/data/io.makeroid.companion/files/assets/
This is the path to the assets on
Beta
server for API < 29 (→ Companion).
thank you… good to know…
I will do another update as soon as the new version goes in production…
The path to assets for API ≥ 29 (→
Beta
server) is:/storage/emulated/0/Android/data/io.makeroid.companion/files/assets/
still some makeroid inside…
@Kodular why not publishing the companion app as io.kodular.companion ?
Taifun
@Kodular why not publishing the companion app as io.kodular.companion ?
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).
why not publishing the companion app as io.kodular.companion ?
Likely because they’d have to republish it.
See also here:
This seems to work on Android < 10 (but it doesn’t make sence). Yes, of course … (and it works on Android 11): [grafik]
@Kodular why not publishing the companion app as io.kodular.companion ?
Exactly what @hammerhai said:
Likely because they’d have to republish it.
and where exactly is the problem to republish it?
Taifun
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.
Could you please test the asset path behaviour with the beta server?
@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…
Taifun
To be precise:
/Android/data/io.makeroid.companion/files/assets/
as found out by @bodymindpower
/Kodular/assets/
directory.Is there an asset named abc.txt
already there?
@bodymindpower I have fixed the bug with Exists block failing to check asset files. I will push it to the beta server soon.
I will push it to the beta server soon.
Let me know when it’s done. I will then test it …
Beta server has been updated along with the companion app on the Play Store.