Stuck on "Installing application" and nothing happens

[DeViL-CU]

Hello, I present the same problem, every time I select an APK to install, it stays stuck in the installation of the package and does not pass, I have version 0.2.5 of WSATools installed

I have the Android subsystem and the development tools are enabled...
Thanks in advance

[Simizfo]

This is finally fixed in the next version. It's coming... hopefully soon

Thanks for reporting!

[DeViL-CU]

Esto finalmente se soluciona en la próxima versión. Ya viene... Esperemos que pronto

¡Gracias por informar!

Thank you very much for answering, I look forward to the next version. Thanks again

[Simizfo]

If you have the Subsystem set to run "As needed" in the WSA Settings app, please try setting it to "Continuous", this should fix the issue for now!

[DeViL-CU]

Si tiene el Subsistema configurado para ejecutarse "Según sea necesario" en la aplicación Configuración de WSA, intente configurarlo en "Continuo", ¡esto debería solucionar el problema por ahora!

I have it configured as it tells me but the same error continues to happen to me, I have no choice but to wait for the next version.

[bigplayer-ai]

same wsatools is stuck on installing application and never installs.
I am using win11 22h2 version 22621.1265

[Simizfo]

@DeViL-CU @bigplayer-ai
WSATools 1.0.0 is coming next week. Totally rewritten! Please wait for the next version as it very likely solves this issue.

Thanks for your patience!

[exeizim]

same in 4.03

also i want to translate the tool to another language if developers want

[DeViL-CU]

With the last update my problem was solved, thank you very much!!

[Simizfo]

@DeViL-CU 😍 this is fantastic, I forgot to mention of the new release, thanks for reporting! I'll reopen this and wait for more feedback

@exeizim @bigplayer-ai if you want to try and let me know, thanks!

[Stephan-P]

So, is Subsystem resources CONTINUOUS still a requirement in the latest release (v 1.0)?

[Stephan-P]

I too had trouble getting adb, WSA and WSAtools to connect. It took a while for me to find out that adb was not talking on the same port as WSA.
Use the following command to assign the right port:
adb connect 127.0.0.1:58526

[Stephan-P]

So, is Subsystem resources CONTINUOUS still a requirement in the latest release (v 1.0)?

I get the impression that Subsystem resources AS NEEDED is working just fine now

[Simizfo]

I too had trouble getting adb, WSA and WSAtools to connect. It took a while for me to find out that adb was not talking on the same port as WSA. Use the following command to assign the right port: adb connect 127.0.0.1:58526

Weird! This is the same address for localhost, which I use to connect by default. The port looks like it's the correct one too.

So, is Subsystem resources CONTINUOUS still a requirement in the latest release (v 1.0)?

I get the impression that Subsystem resources AS NEEDED is working just fine now

Correct! :) it works better with "continuous" mode, but now it works fine with "as needed" too

[Stephan-P]

Somehow my adb was connecting to another address:port. So, an explicit connection to localhost:58526 was the necessary trick