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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment