You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 28, 2021. It is now read-only.
and not specifying success andfail, Socket.io breaks entirely without any error for me.
The solution for me was to simply copy and paste in the sample code from the README.
It seems as though accept(err, result) instead of accept() may be the correct approach for Socket.io >= v2, since that is what it ends up running with the code copied from the README and left unmodified. Just my guess though.
The text was updated successfully, but these errors were encountered:
OK, the issue came back. It seems that something in the default for fail is not working. Putting in the following for fail fixes it, and commenting it out breaks it again:
(data, message, error, accept) => {
if (error) {
throw new Error(message);
} else {
accept(null, false);
}
}
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using deps
and not specifying
success
andfail
, Socket.io breaks entirely without any error for me.The solution for me was to simply copy and paste in the sample code from the README.
It seems as though
accept(err, result)
instead ofaccept()
may be the correct approach for Socket.io >= v2, since that is what it ends up running with the code copied from the README and left unmodified. Just my guess though.The text was updated successfully, but these errors were encountered: