Skip to content
This repository was archived by the owner on May 14, 2024. It is now read-only.

Conversation

@jnoring
Copy link

@jnoring jnoring commented Sep 18, 2014

sendEvent assumes the incoming data isn't an NSArray already; this causes it to double-wrap NSArray objects (so instead of [data], you end up with [[data]]. Check if the incoming objet is of type NSArray, and if so pass it along verbatim.

sendEvent assumes the incoming data isn't an NSArray already; this causes it to double-wrap NSArray objects (so instead of [data], you end up with [[data]].  Check if the incoming objet is of type NSArray, and if so pass it along verbatim.
@jnoring
Copy link
Author

jnoring commented Sep 18, 2014

It's possible I'm not understanding how this code works, but I have some server communication using socket-io that expects the args argument to be something like "[NSDictionary_, NSString_]" (which is likely bogus, but nonetheless, what I have to work with). If there's another way to do this, I'm all ears.

@aldevet
Copy link

aldevet commented Apr 18, 2015

I was having issues with multiple parameters like:

socket.on('publish', function (options, sdp, callback) {

Because of the double-wrap all data will go to first parameter. This pull request solves it, hope it merges!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants