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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment