This repository was archived by the owner on Sep 6, 2020. It is now read-only.
Fire onConnect event when connection established #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the SocketIOClient, `onConnect()` never called `mHandler.onConnect()`
koush
added a commit
that referenced
this pull request
Jan 3, 2013
Fire onConnect event when connection established
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for getting socket.io communications working with native android. This is really awesome.
Anyway, in the SocketIOClient,
onConnect()never calledmHandler.onConnect(), so the onConnect method in the SocketIOClient.Handler was never being called.