I also attempted connecting via USB, just gave me a white screen on device, and runtime error about not being able to set properties for the extension (so it got somewhere but obviously did not load the classes.jar file...)
You got the no such class error, which sometimes appeared also in the past... therefore on the extensions directory webpage I have this chapter for that kind of error
How to avoid runtime errors with the companion app
After importing an extension, please restart the companion app.
If you like to use an extension on a different screen, in Screen1 additionally drag the extension into the working area.
While starting the companion app, all necessary assets and also the imported extensions of your project will be copied to your device. So in case the no such class error shows up, the extension code to run the extension is not available on your device. Without that code the companion app is not able to execute methods from the extension.
In case restarting the companion app does not work for you after trying several times, then as it looks like the only way for you to test you app will be after building it using the apk file.
I get the same error for almost every other extension. I always delete the Companion folder and reload the browser before testing an extension. That doesn't change anything.
As everyone knows, it also worked with Companion before. If we can basically only test with the compiled app, we don't need Companion anymore.
And as you can see from my example, it works without any problems with Niotron.
I have the same problem using KIO4_base64 and ClickZ, when i try to lunch the app on companion it gives me this error:
"Unable to load extensions.java.lang.StringIndexOutOfBoundsException:
String index out of range: -1"
companion version: 2.73 (from app store)
Phone: Samsung A30s
Android version: 11
So I was able to reproduce the problem. That means it's only a matter of time until I have it fixed. I'll probably post a binary of a fixed companion within the next 24 hours.
Strange because I had this problem for a few days on Android 14. In addition, I read in PR that on Android14 the jar file has the same name as the extension. In my case, it was still classes.jar in the error.
Ran tests on three devices, using both the ai2test server and ai2 server, with companion 2.73tu.
For me this has fixed the "String IndexOutOfBounds" error on Android 12 (genymotion) and Android 13 (Pixel 4a)
Well done Jeff !!
What remains is a continuing issue with Android 14/15 in loading a project with an updated extension which is returning the error of being unable to load the classes.jar. This is with tests on Android 15 Pixel 8a. This failed to load to the two projects I tested, which loaded just fine with Android 12 & 13.
Working fine on android 11 (Samsung A30s) Emulator v2.73t2u
The only "problem" when you launch it on the companion shows to update the version of the companion skippable pressing "not now"
Tested on a Pixel 7 Pro (Android 14):
