Unsolved Adroid Debugging Fail

[ebonnett]

And yet something else to stop me from debugging on Android. Has anyone seen this issue? Here are the specifics on my dev environment:

Qt Creator 4.6.2 using 5.11.0
SDK - API's 28 and 27
NDK - r10e
Phones used: Nexus 6P, Galaxy S7, Galaxy S9, Galaxy Note 4
OS - Windows 10

Failed to get process path. Reason: The command "C:\Users<myUserName>\AppData\Local\Android\Sdk\platform-tools\adb.exe" terminated with exit code -1..
Unexpected run control state RunControlState::Stopped when worker AndroidRunner started.

[mvuori]

If I remember right, people have complained about this for Qt 5.11. Anyway, it has serious bugs for Android, so you really should upgrade to 5.11.1 -- that's what bug fixing upgrades are for.

[ebonnett]

Yep, I'm aware of what bug fixing point releases are for. That didn't fix it. Still seems like there is something continuously blocking the ports Qt is going for. Is anyone familiar with a way to see who's got the port locked up?

[Vikas Pachdha]

Please check if the devices you are using supports "run-as" command. Some Samsung devices don't support the "run-as" command. QTC debugging workflow depends on "run-as" command and this might be the problem in your case. Just do "./adb shell run-as your_package_name pwd" and see if your device supports it.