Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.34f1
Issue ID
UUM-1927
Regression
No
[Backport] [Android] [Linux] "Unable to forward network traffic to device" when trying to Build and Run a Development build
Required: Unity configured to build to Android devices.
Repro steps:
1. Open the attached project
2. Build and run to Android device
3. Notice that the app is installed on the device but is not automatically opened
4. Check the console
Expected result: the app is installed and automatically opened on the device
Actual result: the app is installed but not opened; error thrown:
"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.
/home/unityqa/Android/Sdk/platform-tools/adb -s "efd3a563" forward "tcp:34999" "localabstract:Unity-com.foo.test"
stderr \[error: cannot bind listener: Address already in use]
..."
Reproducible with: 5.6.3f1, 2017.1.0b3, 2017.2.0f3, 2017.4.13f1, 2018.2.11f1, 2018.3.0b5, 2019.1.0a11
Tested on: Ubuntu 16.04, Ubuntu 18.04
Issue not specific to a device
Workaround: Close Unity Editor and type the following in terminal: adb -s "xxx" forward "tcp:34999" "localabstract:Unity-com.foo.test"
(however, the port must be forwarded every time system after is restarted)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2020.3.X):
There are no fixes planned for this Bug