Search Issue Tracker

Fixed in 2022.1.X



Found in






Issue ID




[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" ""

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" ""
(however, the port must be forwarded every time system after is restarted)

  1. Resolution Note (fix version 2022.1):

    Fixed in 2021.2.0b12 and 2022.1.0a8

Comments (7)

  1. BlackclawsK

    Aug 13, 2020 14:11

    Issue still exists in 2020.01

  2. mlea_unity

    Aug 03, 2019 14:14

    Still getting it on Ubuntu 18.04 with 2019.2

  3. senkal_

    Jan 11, 2019 11:58

    Thank you for clarification, makes sense.
    Looks like I need to read a little how does the issue tracker works in some areas.

  4. Yury-Habets

    Jan 04, 2019 13:05

    @senkal_ : that's almost correct. The issue you found was closed as fixed, but it was fixed for release builds only. Development builds still suffer from the forwarding issue. This is why we had to open another bug report.

  5. senkal_

    Jan 03, 2019 18:11

    I think this is a duplicate.

    Looks like issue was fixed in 2019, will check later to confirm.

  6. senkal_

    Jan 03, 2019 17:10

    Can confirm the issue.
    For me this happened on every version I tried since Unity 2018.2, currently on 2018.2.17f1 and 2018.3.0f2.
    I use Mint 18.3 with KDE so basically Ubuntu 16.04.

    On top of that, in both tested versions, I can't properly close Unity after deployment and reported error, have to manually kill it from task manager. But this issue maybe is not related.

  7. imarkroger

    Dec 14, 2018 02:07

    [deleted spam]

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.