Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b2
2018.1.0f2
Issue ID
1036552
Regression
Yes
TcpClient.Client.LocalEndPoint is always null when Scripting RunTime is set to 4.x
How to reproduce:
1. Open given unity project
2. Make sure that scripting runtime version is set to 4.x
3. Enter play mode
4. Notice in the console that LocalEndPoint is null
5. Change scripting runtime version to 3.5
6. Enter play mode
7. Notice that LocalEndPoint is not null
Expected result: TcpClient.Client.LocalEndPoint should not be null in both ways
Actual result: TcpClient.Client.LocalEndPoint is null in 4.x
Regression first introduced in: 2017.2.0b2
Reproducible with: 2018.3.0a1, 2018.2.0b4, 2018.1.0f2, 2017.4.3f1,2017.3.2f1, 2017.2.2p2
Not reproducible with: 2017.1.4f1
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
Add comment