Android: adb won't install to wifi connected devices?

it looks to me as if the “Android Build & Run” command is using the sequence
adb usb
adb install foo.apk
rather than just
adb install foo.apk
to trigger the installation step to a connected android device. this is a problem because if you have established a device as debugging over wifi, unity will upset the wifi adb connection and disconnect the device, leaving you with Unity’s “no device found” state.

is there a setting or script file somewhere to trigger only using existing connected device(s) rather than doing a full reset and only choosing the first USB-connected device?

1 Like

Probably fine on Windows though? (I think I’ve deployed via WiFi on Windows.)

Can you file a bug maybe? It would be nice to enable WiFi debugging for OSX peeps as well.

I would love for this to get fixed. Wifi Build & Run doesn’t work on Windows either. It seems like the device always disconnects when running through Unity. Running the “adb usb” command will do that.

After filing a bug report I was asked to make a feature request. I posted the feature request here - http://feedback.unity3d.com/suggestions/wifi-android-builds

1 Like