Search Issue Tracker
Fixed in 5.4.1
Votes
1
Found in
5.4.0b15
Issue ID
791721
Regression
No
[il2cpp] Socket.AsyncConnect doesn't work on IL2CPP backend
Users would like to use tcp socket client/server communication on WSA Universal 10 (UWP10), but they have some blocker issue with Socket.ConnectAsync method. They are not able to connect from the client to their server. Without blocking socket the completed event is not called and the communication is in connecting state, with blocking socket they received error result "Would block".
The issue is reproducible on Windows Standalone x64 (il2cpp) and Windows Store Apps (il2cpp).
Step to reproduce:
1. Open project "AsyncConnect.zip".
2. Make build for Windows Standalone x64 development build.
4. Tap on connect and see the result.
Note: For some reason when building to Windows Standalone x86 build, everything works fine and the behavior is the same as Editor. So the issue is only with 64 bit player.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
- Shader Graph Import Settings documentation leads to "Sorry... that page seems to be missing!" page when opened through the documentation button in the Inspector window
- Unexpected Material change/transparency when switching between ShaderGraph and material at runtime in HDRP
Add comment