When creating a Development Build for Android I get the following error:
Error building Player: CommandInvokationFailure: Unable to forward network traffic to device. Please make sure the Android SDK is installed and is properly configured in the Editor. See the Console for more details.
[Path to Android SDK]/platform-tools/adb -s [Device ID] forward "tcp:54999" "localabstract:Unity-com.[Company Name].[App Name]"
stderr[
error: cannot bind to socket
error: cannot bind to socket
]
stdout[
]
Via netstat no other application had control of that port. Disabling development builds fixes the issue. Development builds for Linux x86_64 didn’t have this issue. Confirmed this issue existed with the default Unity scene with nothing added.
I am getting this error as well, my android project stopped building when I updated to 5.2.
Log:
CommandInvokationFailure: Unable to forward network traffic to device. Please make sure the Android SDK is installed and is properly configured in the Editor. See the Console for more details.
Z:/AndroidStudio_SDK\platform-tools\adb.exe -s [DeviceID] forward “tcp:54999” “localabstract:Unity-com.stewart.dndhelperapp”
stderr[
error: cannot bind to socket: No error
error: cannot bind to socket: No error
]
stdout[
+1
[On a side note: unity remote works almost flawlessly :)]
[Edit 2] The profiler correctly works, so the problem is only in the binding after the build. Manually connecting the Profiler to Android works fine.
Hi guys!
Does somebody know the fix for this error when buillding in development build? I need development build checked to connect the profiler to my device, but i can’t - this error occurs.
I get this error, but the game is deploying, it’s as if it just can’t start it remotely. Now, I had it deployed from Windows so I had the launcher icon showing already, I’m not sure if that’s part of the process that’s failing. Are any of you seeing the launcher icon? The APK should still be on your device, maybe have a go at installing it manually.
I had the same problem on Windows. It seems strange, but removing Temp and Library folders helped (Unity recreates both, but make backup before you apply this solution).
Temp and Library can both be deleted without backup; it’s standard practice to ignore them in version control.
That said the actual issue is probably that Unity has zombie processes which aren’t releasing files which later are trying to be reopened. I would bet that the actual issue is in Temp, not Library.
You might be able to isolate the zombie process in a terminal, type “lsof +D Temp” see which process IDs have hold of several files, then “kill [1st process id] [2nd…”.
