tns device and wifi adb connection. Device gets disconnected

[adisoftbn]

Please, provide the details below:

I'm trying to deploy app builds over wifi, to not break my phone battery by keeping my phone connected all the time to USB. I can do anything over wifi with ADB, and it stays connected hours without any problem, but when i run tns device it gets disconnected automatically and it shows no devices.

If i run tns run android it starts the emulator automatically even if i previously connected the device using tcpip(wifi). Next time when i use adb devices it shows me that no devices are connected.

Did you verify this is a real problem by searching [Stack Overflow]

Yes I checked all of them

Tell us about the problem

tns device automatically disconnects any device connected with adb over wifi

Which platform(s) does your issue occur on?

Android

Please provide the following version numbers that your issue occurs with:

• CLI: 2.3
• Cross-platform modules: 2.3
• Runtime(s): 2.3

Please tell us how to recreate the issue in as much detail as possible.

connect the phone using usb.

run adb tcpip 5555

disconnect the phone from usb

run adb connect phone_ip:5555

run adb shell or anything you want like install apk and so on, and everything works perfect. No issue.

run tns device and everything gets disconnected

[tsonevn]

Hi @adisoftbn,

I reviewed the given case and was unable to reproduce problem while using android device connected via WiFi. I follow the described steps from this thread in StackOverflow. Regarding to that when you run adb devices verify whether the device Status is Connected. Otherwise if the status is Unreachable, tns device command will not list your device as available and will not be able to deploy your app using WiFi connection.

Regards,
@tsonevn

[adisoftbn]

Hello,

I have attached a screenshoot with the command prompt showing that everything works forever or until tns is called to search for devices. Every time i run tns, the device is automatically disconnected.

By the way, i'm on windows, and I have a Galaxy S7, and never had any problem with it. Tested also with a Galaxy Note 10.1 and I have the same problem. I use the original Samsung drivers.

png link

As a workaround i'm using the following script to get it done using wifi, but i can't see the console log for debugging sadly...

tns build android
adb uninstall com.application.id
adb install platforms\android\build\outputs\apk\apk-debug.apk
adb shell am start -n com.application.id/com.tns.NativeScriptActivity

If I use this script I never get my device disconnected... I will try to take a wider look this weekend into the tns issue.

Best regards,
Adrian

[tsonevn]

Hi @adisoftbn,
Thank you for the reply.
At the moment I am still not able to reproduce such a problem on my local PC, We will investigate further and will provide additional info about the issue.

Regards,
@tsonevn

[adisoftbn]

I don't know if it helps but, from time to time i get also this, and I need to install the APK manually on the phone.

This is on USB. Same PC/Phone

[adisoftbn]

It seems that I fixed the issue :D by removing all adb.exe files and folder:

*%%appdata%%\Roaming\npm\node_modules\nativescript\lib\common\resources\platform-tools\android\win32*

It was a conflict(for adb.exe) between android sdk tools, nativescript android tools, and other tools like genymotion. Some of them where in the PATH list.

Sometimes I still get "The new package is assigned a different UID than it previously held."

[lanette46]

I have the same issue, I have my android device connected via IP address and tns devices make adb devices server out of date, and start daemon again with my device disconnected.

[elisaado]

Same here.

I think this happens because tns probably (I'm not sure) restarts the ADB server.
When I reconnect after tns disconnects the device, ADB says: adb server version (39) doesn't match this client (40); killing...

[elisaado]

Fixed! For anyone on (Arch) Linux having the same issue, check if your $ANDROID_HOME is different from the /platform-tools in your $PATH.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.