Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2023.1.0a1
Issue ID
UUM-1385
Regression
Yes
Unity process are sometimes running on TCP in port range 5555 - 5585 which conflicts with adb
To reproduce:
- not consistently reproducible, retry steps if needed
1. Open terminal and execute "adb kill-server"
2. Open a new project
3. Open terminal and execute "sudo netstat -tulpn | grep "Unity""
4. Look for processes running on "0.0.0.0:5555"
5. Execute "adb devices"
6. Observe "emulator-5554 offline"
Reproducible with: 2018.3.0b5, 2018.4.0f1, 2019.1.1f1, 2019.3.0a2
Unable to reproduce with: 2017.4.27f1, 2018.2.21f1
Unable to reproduce on Windows, MacOS
Some Unity process (most often UnityShaderCompiler) uses TCP address 0.0.0.0:5555 which conflicts with ADB emulator port range (5555-5585) https://developer.android.com/studio/command-line/adb#howadbworks
When a user starts up an adb client with 'adb devices' command, adb sees port 5555 being used and thinks that there is an android device/emulator that is offline (see issue.png screenshot). The issue with this is that a user cannot build the project for Android player until the "offline emulator" is hanging.
Workarounds:
- kill the process that uses port 5555
- execute terminal commands "adb kill-server && adb devices" until the "emulator-5554 offline" no longer appears
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
As we are moving towards the deprecation of OpenRL, we are not going to invest any more of our resources into fixing issues like this. As we can see there are multiple workaround and the issue is not consistently reproducible, we have deprioritized this in favor of a dull reprecation of OpenRL in future releases.
Resolution Note (2023.1.X):
As we are moving towards the deprecation of OpenRL, we are not going to invest any more of our resources into fixing issues like this. As we can see there are multiple workaround and the issue is not consistently reproducible, we have deprioritized this in favor of a dull reprecation of OpenRL in future releases.