-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when using emitWithAck #42
Comments
OK found the origin of the issue. Bytheway, The emitBuffered function is bugged also. It should be:
Same fix should also probably be applied to other 'Function.apply' calls (I didn't inspect the whole lib code, only the socket.dart file so the same issue can potentially afect other functions in other files) where function argument type are not known (=are dynamic) and can potentially be a List |
@ramsestom |
Thanks. I have seen you fix and it is pretty much the changes I have done in my local copy so it should work ;) |
okay, thanks. |
@ramsestom After I take some times to test this issue, the original implementation works well with our |
I refix it again for both nodejs and dart server version. |
Thanks. I am using the node.js (feathersjs) version for my server |
I'm using 0.9.11.
error
And as same as ramsestom, it was totally ok with just emit(). |
Ok, I found the problem. In the ack parameter function, you need to set the right parameter you wish to get from server, and it can't be omitted.
|
I am trying to use this lib but it doesn't seem to work
I tried with a really simple example like this:
but it is throwing an error. Here is the exception call stack:
and the Log from the lib is as follow:
Strange thing is that even if I call a simple emit function instead of emitWithAck, like this:
_socket.emit("authenticate", {"strategy":"local", "email":"test@yahoo.fr", "password":"test69"});
no error is thrown by the app but the log still hang on after the "readyState opening" message and the rest of the log is only printed when the app is killed...
So here is the log I have in this case:
any idea of what might be the issue and how to solve it?
The text was updated successfully, but these errors were encountered: