Yes, once the bugs have been resolved to MIT's satisfaction.
1 Like
Can you post the aia file for the project that fails?
Normally, Chromebooks can only load apps from the Play Store. There is a way to side-load apps, but it is complicated and I doubt schools will allow it.
1 Like
I'm hoping to have the fixed Companion uploaded for review to the Play Store tomorrow. Google then has to do their review, which can be a random amount of time ranging from an hour to 5 days...
1 Like
It also fails on a Google Pixel 2XL (Android 11).
Unfortunately, it is not completely fixed. It works on some phones, but not all. It does not apply to a specific project, but to any with extension. On my old Samsung S8 with Android 9, the external_comps folder in ASD is empty.
More precisely, it is not fixed at all.
Hy guys, i am come back here to give you some feedback about the patch version 2.73d1u on Samsung A30s (Android version: 11) without using the test server, everything seems fine, all components works, screens, blocks, extensions, connection, etc... How expected giving the notification to update it, but doesn't have any problem with it in this week!
Another update, can confirm downgrading to version 2.71u works but 2.73 is broken, had to downgrade from an APK from here
1 Like
I have modded my personal chromebook to be able to sideload apk's so thats how i tested version 2.71u
You can try and hack your chromebook from this guide here but if linux is disabled on your school chromebook, it will not work. Same goes for the android debugging setting in the linux settings.
1 Like
Have you tried Niotron? I have no problems there with any of my test devices (including my 5 Samsung devices).
Have they (Niotron) updated with App Inventor? I'd be weary of using any derivative of App Inventor that hasn't updated with App Inventor given the Google Play Store rules...
What rules are meant by this?
In Android 14, any executable code (e.g., extensions) must be marked read-only in the file system. This is the inherent problem caused by 2.73 that it works on some devices and not others. If they (Niotron) are still targeting Android 13 or lower, then they won't be affected by the change yet.
They target SDK 34.
But, Niotron does not publish its companion app in the Play Store, but only provides a download link (like AI2 does with the "u" version).
Now everything is clear.
Is it?
Yes.
That explains everything
Ok, so where is then the problem to do it the same way?