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
- Dragging any draggable query block makes the query block background invisible until hovering on it again
- Alternating row background lines in table view are left over when clearing the search field
- Getting duplicate search query results for created scripts in search window
- There is no information or any visual indicator/response when some properties are set as inline value in the UI Builder
- Dialog Text during the Confirmation stage of Bug Report Submission is cut off when the Bug Reporter Window is resized to it's smallest possible size
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2020.3.X):
There are no fixes planned for this Bug