SocketRocket: In debug mode. Allowing connection to any root cert

[mmilen]

Hi,

After losing out a user and then login the same user Simperium for Mac OS goes into a loop with Socket Error "Invalid Certificate"

To replicate all without restarting the App:

1. Connect with a user with call like [self.simperium authenticateWithAppID:@"paper-video-6fd" token:[notification object]]; the token is valid.
2. Logout user with [self.simperium signOutAndRemoveLocalData:NO completion: ^{
   }];
3. Connect the same a user with call like [self.simperium authenticateWithAppID:@"paper-video-6fd" token:[notification object]]; the token is valid.

The connection looks OK but the NSLOG keeps printing out : "SocketRocket: In debug mode. Allowing connection to any root cert".

• (void)webSocket:(SPWebSocket *)webSocket didFailWithError:(NSError *)error starts looping the error is #23556 (Invalid server cert) .

I'm I doing something wrong when disconnecting the client?

[jleandroperez]

@mmilen hello there!. There's nothing wrong with the sign out invocation. I'll try to reproduce this on my end.

I remember seeing this error in console... long ago, while testing Simplenote in the iOS Simulator. It got fixed on its own, after performing a fresh install (Simulator Reset, actually). Sadly, i never got to trigger it again.

Is it possible you're using a VPN / debugging software, such as Charles?

[mmilen]

Thanks for the immediate response ( rare occurrence nowadays ) !!!
I'm using stock Mac OS 10.8.5 with XCode 5.1.1 , both my project and
Simperium project targets are set to Mac OS 10.8 .

Milen Milkovski
CEO / Lead Developer
L'Atelier D'Ema
milen@emabridge.com
On 2015-08-12 3:01 PM, Jorge Leandro Perez wrote:

@mmilen https://github.com/mmilen hello there!. There's nothing
wrong with the |sign out| invocation. I'll try to reproduce this on my
end.

I remember seeing this error in console... long ago, while testing
Simplenote in the iOS Simulator. It got fixed on its own, after
performing a fresh install (Simulator Reset, actually). Sadly, i never
got to trigger it again.

Is it possible you're using a VPN / debugging software, such as Charles?

—
Reply to this email directly or view it on GitHub
#492 (comment).

[jleandroperez]

No problem sir!. I'll try to reproduce the same under Mountain Lion. Would it be possible to test the exact same code you're running in Yosemite?

[mmilen]

Will try in the next couple of days and will let you know.

Milen Milkovski
CEO / Lead Developer
L'Atelier D'Ema
milen@emabridge.com
On 2015-08-12 3:14 PM, Jorge Leandro Perez wrote:

No problem sir!. I'll try to reproduce the same under Mountain Lion.
Would it be possible to test the exact same code you're running in
Yosemite?

—
Reply to this email directly or view it on GitHub
#492 (comment).

[jleandroperez]

Perfect, thank you!

[mmilen]

Just build the project in Yosemite, and everything is working perfectly
fine .

Milen Milkovski
CEO / Lead Developer
L'Atelier D'Ema
milen@emabridge.com
On 2015-08-12 3:38 PM, Jorge Leandro Perez wrote:

Perfect, thank you!

—
Reply to this email directly or view it on GitHub
#492 (comment).

[jleandroperez]

Cool. Are you running 10.8 in a Virtual Machine? (i'll try that setup, since i'm already running Yosemite).

• Can you please verify if there's no proxy setting that might be interfering?
• Is the library effectively not sync'ing anything?

[jleandroperez]

@mmilen hello there!

May i ask you if you have some extra debug info // still experiencing this glitch?. I've been unable to reproduce on my end.

Thanks in advance!

[mmilen]

It is still there. With my game it would be extremely rare that the user
will logout, so no big deal. Let me know if I can test something to help
you out.

Milen Milkovski
CEO / Lead Developer
L'Atelier D'Ema
milen@emabridge.com
On 2015-09-01 11:43 AM, Jorge Leandro Perez wrote:

@mmilen https://github.com/mmilen hello there!

May i ask you if you have some extra debug info // still experiencing
this glitch?. I've been unable to reproduce on my end.

Thanks in advance!

—
Reply to this email directly or view it on GitHub
#492 (comment).