Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
Votes
2
Found in
2018.1.4f1
2018.2.0b4
2018.2.0b6
Issue ID
1045497
Regression
Yes
"Opened" event of a WebSocket4Net.WebSocket does not get called when opening a web socket
How to reproduce:
1. Open the "SampleScene" scene in the attached project
2. Enter the Play mode
Expected result: In the Console window, "Opened" log message appears, as a result of the "Opened" event being called on the WebSocket.
Actual result: In the Console, there is no "Opened" log message.
Reproducible with - 2018.1.4f1, 2018.2.0b4, 2018.2.0b7, 2018.3.0a1
Not reproducible with - 2017.1.4f1, 2017.2.3p1, 2017.4.5f1, 2018.1.0a1, 2018.1.3f1, 2018.2.0b3
Fixed in 2018.3.0a8
Backported to 2018.2.3f1
Comments (3)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
RRickkert
Aug 27, 2018 09:41
Confirmed fixed in 2018.2.5f1, maybe some versions sooner as well, but that one works.
RRickkert
Jul 11, 2018 08:42
Currently not fixed in 2018.2.0f2
XRA
Jul 11, 2018 01:27
this is NOT fixed in 2018.2