Results
2
comments of
鬼谷
This bug is very strange. It only exists for the first message after the websocket connection. As long as the first message is successful, this bug will not occur again....