Vorlonjs Websocket error after update iOS 10.3.1

Hi,

Everything was fine since yesterday. We upgrade our IOS device to version 10.3.1 and now we got "Websocket error" from vorlon.

We can see the console.log from the device on our cordova app, but are not enable for example to send command (like alert or whatever), and we cannot reach the device information anymore.

When the device's launch we got this (see screenshot).

Any idea? Everything work fine on Android.

Apr 09 '17 20:04 Anopetia

Uninstall; Reinstall the app,and the problem's gone.

Weird.

Apr 09 '17 21:04 Anopetia

Speaking too fast, probem came back.... Exactly the same.... Just after reload the app.

Apr 09 '17 21:04 Anopetia

Deactivating DomExplorer, And ObjectExplorer seems to remove the error. Interactive console is working fine, but we cannot explorer dom and object.

Apr 09 '17 23:04 Anopetia

I can reproduce the same error my iPhone and also my mac:

Here is the stack on Safari 10.1

When I put a break point here:

I see that it's throwing in json3 library.

Let us know how we can help to troubleshoot the issue

Apr 12 '17 04:04 phil-lgr

Hey guys!

Thanks for reporting this, I will have a look today :)

Apr 12 '17 15:04 etiennemargraff

Cool Merci :)

Apr 12 '17 15:04 Anopetia

Ok so I can reproduce it but it seems there is a racing condition here as it does not happen everytime. I am going to love fixing this... :) Keep you posted as soon as I know more

Apr 12 '17 17:04 etiennemargraff

Yes, it's like random, I cannot reproduce anytime too, but most part of the time.

Apr 12 '17 18:04 Anopetia

So i digged a little and apparently there is a regression in Safari in this build around websocket. Someone already created a bug issue in the webkit bugzilla: https://bugs.webkit.org/show_bug.cgi?id=170463

I will give them until next week to fix it and if they don't I will be forced to implement a workaround in Vorlon. I do not want to do it if I can avoid it.

Does it sound ok to you?

Apr 12 '17 23:04 etiennemargraff

Yep, for now we don't use dom explorer or object explorer.

Calling console.log(object) or console.log(DOMHtml), do the job anyway, even if it's less user friendly.

Thank you for your attention meulta.

Waiting for the fix so.

Apr 13 '17 15:04 Anopetia

@meulta Any update on this allready? :)