Personally, I think I used too many extensions in trials. It may be residue or something clogging wherever they are stored. Anyway it's above my knowledge.
Does this Companion work for you?
Ok, take 5 whilst I do the job.
Hmmm. Now I tried again with Companion installed from the server, i.e. 2.73u, and the error no longer occurs... maybe something has been fixed...
If I remember correctly, the error was also not there the first day after updating Companion to 2.73. Then a few days of problems, and today it works again.
I installed your companion. Had to uninstall the one I had due to a conflict. Your one seemed to work ok, but came up with an error on the comp. Once dis missed it seemed to work ok.
You have the same issue as already reported here
Taifun
@Taifun well it gives me relief that it's not just me. Found an old phone, and companion 2.72 is working ok on it.
More weird behaviour from companion:
Environment: Google Pixel 8a, Android 15, Companion app 2.73u, AI2 nb199
I wanted to make a couple of small changes to my webviewextra extension, so made them and built the extension with RUSH, and imported it to a previously working in companion project that already had the working 1.8 release of the extension. The companion refused to load the extension, complaining about being unable to load the classes.jar. Exit Application.
I reverted the changes I made, so that the extension code was EXACTLY the same as the working 1.8 release. I built that, loaded it to the project, and this produced the same error.
I then tried building the 1.8 release code with FAST. This produced the same error.
I also tried with a new project and just the extension, same error.
occasionally, it doesn't get as far as the device:
The original version of 1.8 release built on 1st September 2024 works fine with the companion.
Compiling apps with all three works OK.
I also tested with a very small and simple extension I built just 2 days ago, this also generated the error from a new build of the extension.
I also built a completely new extension using the RUSH demo code and added it to a new project. This loaded OK in companion. Building the extension again and loading that version also worked ?
Nothing has changed with RUSH for a long time, FAST is pretty much up to date...
It seems that a newly built version of an extension is having a problem with the companion.
Anyone else seeing this?
As for me, there is no regular behavior here. It's just that the operation is unstable, it works once, it doesn't work twice. There is no rule. I don't know the principle of sending a project to asd companion, but the same ai2 source compiled locally has no problem sending projects to the phone. So the fault probably lies in the server. Maybe too low bandwidth or too low timeout somewhere.
All project resources and the jar file are sent to the ASD folder of the Companion application. This is where the problem arises because the files often do not end up in the ASD.
1 Like
I connected to companion on Android 14, the error appears, but on my Android 11 the error does not appear, everything is fine there, until I want to compile the apk it gives me the error.