Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
0
Found in
2018.1.6f1
2018.3.6f1
Issue ID
1133587
Regression
No
[Windows][IL2CPP] Standalone Player does not throw an Error when initializing multiple TcpListeners with the same Port Number
To reproduce:
1. Download attached project "TestSocket2018.3.zip" and open in Unity
2. Open "SampleScene" scene
3. Enter to Play mode
4. Observe that UI.Text GameObject and Console throws Error:
SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted.
5. Exit Play mode
6. Set Scripting Backend to IL2CPP and build Standalone Player
7. Launch Standalone Build
Expected results: Like in Unity Editor, Standalone also throws same Error
Actual results: Standalone Build does not throw any Errors
Notes:
- This issue only occurs in Windows Standalone
- On macOS Standalone, iOS and other Platforms everything works as expected
- On macOS Standalone and iOS I get different Error:
SocketException: Address already in use
Reproduced on Unity 2018.1.6f1, 2018.1.9f2, 2018.2.21f1, 2018.3.8f1, 2019.1.0b6 and 2019.2.0a7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Add comment