Closed AlexeyDunin closed 11 months ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you'd like this issue to stay open please leave a comment indicating how this issue is affecting you. Thank you.
Description
This is a common bug that happens when you use Pusher with WebSockets. What happens is that when your connection drops, the WebSocket object gets disposed of and set to null. But then when the pusher tries to reconnect, it doesn't check if the WebSocket is null or not. It just tries to dispose of it again, and that causes a null reference error.
CHANGELOG