Only the first parameter is passed to the event's callback

[Anislav]

On one hand, it is possible to emit an event by including any other parameters:

[socket emit: @"event_name", @1, @2, nil];

On the other hand, when an event and is received by a callback, only the first parameter is passed to it:

[socket on: @"event_name" callback: ^(id data) {}];

The expected behavior is all of the parameters to be passed to the callback as NSArray.

Note that this is supported by the JavaScript client:

socket.on('event_name', function (first, second)  {});

[rgajrawala]

You must convert id data into the object you know for sure you are receiving. Examples:

1. Dictionary

• Server: socket.emit('test',{name:'usandfriends',age:16});
• Client: NSLog(@"name: %@, age:%@", [data objectForKey:@"name"], [data objectForKey:@"age"]);
• Output: name: usandfriends, age:16

2. Array

• Server: socket.emit('test',[1,2,3]);
• Client: NSLog(@"index 2: %@", [(NSArray*)data objectAtIndex:1]);
• Output: index 2: 2