vascome/vpsocketio

socket.io client objective-c

VPSocketIO

Socket.IO client for iOS. Supports socket.io 2.0+

It's based on a official Swift library from here: SocketIO-Client-Swift

It uses Jetfire Jetfire

Objective-C Example

#import <SocketIO-iOS/SocketIO-iOS.h>;
NSURL* url = [[NSURL alloc] initWithString:@"http://localhost:8080"];
SocketIOClient* socket = [[SocketIOClient alloc] initWithSocketURL:url config:@{@"log": @YES];

[socket on:@"connect" callback:^(NSArray* data, SocketAckEmitter* ack) {
    NSLog(@"socket connected");
}];

[socket connect];

Features

• Supports socket.io 2.0+
• Supports binary
• Supports Polling and WebSockets
• Supports TLS/SSL

Installation

Carthage

Add these line to your Cartfile:

github "vascome/vpsocketio" ~> 1.0.5 # Or latest version

Run carthage update --platform ios,macosx.

CocoaPods 1.0.0 or later

Create Podfile and add pod 'VPSocketIO' (pod files are case sensetive):

target 'MyApp' do
    pod 'VPSocketIO', '~> 1.0.5' # Or latest version
end

License

MIT

vpsocketio's Issues

A few too many non-error errors?

When testing on iOS with Developer -> Network Link Conditioner set to Very Bad Network, I see lots of these:

ERROR: Engine tried opening while connected. Assuming this was a reconnect

Maybe the server should know and not assume when it is a reconnect? In any case should it really be type ERROR?

Also lots of these:

SocketEngine ERROR: The operation couldn’t be completed. (JFRWebSocket error 1000.)

Which also don't look like errors.

Here is my config:

[[self alloc] initWithURL:[NSURL URLWithString:@"https://ws.blah.me"] options:@{@"secure": @YES, @"forceNew": @NO, @"forceWebsockets": @NO, @"forcePolling": @NO, @"reconnectWait": @30, @"logger":logger, @"log": @NO}];

We're connecting with:

self.defaultTimeout = 30;
[self.socket connectWithTimeoutAfter:self.defaultTimeout withHandler:^{
}];

CFNetwork SSLHandshake failed

CFNetwork SSLHandshake failed (-9806)
TCP Conn 0x600000165040 SSLHandshake failed (-9806)
SocketStream write error [0x600000165040]: 3 -9806
ClientSocket MESSAGE: Flushing probe wait

emitWithAck and timingOutAfter not working.

I can emit a message with args and it just sends fine:

[client emit:@"message" items:@[data]];

However, I need the ACK payload too, so I use:

[[client emit:@"message" items:@[data]] timingOutAfter:5 callback:^(NSArray *array) {
    //process response
}];

Though, neither my message is sent to the server, nor I receive a response/ACK.

What am I doing wrong? (my server is on socket.io 2.0)

deadlocks

We are seeing the occasional deadlock when developing. The only active thread is VPSocketIO stuff.

Any ideas how we could help debug this?

Can't get ssid

url = [[NSURL alloc] initWithString:@"http://localhost:3000"];

socket = [[VPSocketIOClient alloc] init:url withConfig:@{@"log": @false}];

[socket on:@"connect" callback:^(NSArray* data, VPSocketAckEmitter* ack) {
NSLog(@"socket connected: %@", [self->socket ssid]);
}];

But Log window show: socket connected: (null)
And urlRequest show: "<CFHTTPMessageRef 0x28365d5c0(0x28365d5d0)> { GET request, url ws://localhost:3000/socket.io/?transport=websocket&sid=vEquHExR-HYULOyPAAAE }"

CocoaPods can't find pod 'vpsocketio'

Before you ask, yes, I did pod update

In my podfile I have (with 20+ other perfectly working pods):
pod 'vpsocketio'

Though it says:

[!] Unable to find a specification for vpsocketio

'VPSocketPacket.h' file not found

I'm using it inside a framework with Objective-C.
After 'pod install', I build the framework and get 'VPSocketPacket.h' file not found, and it actually isn't there.
Then I have to 'pod install' again until the error is gone, but again after I change some pod and install I'm getting it again.
Am I missing something?

demo里面socket初始化方法中的config字典少个逗号~~

Namespace usage

I'm having trouble emitting messages (and getting responses) to a separate namespace.

I created two clients:

1. no namespace specified
2. namespace specified to be "/chat"

The url's for both are the same. The messages to 1 are working fine but not 2. Any ideas? Has the namespace stuff been extensively used?