"document is not defined" error upon debug JS

[spotsadmin]

This is the only socket.io-client I found to be actually working so far. I ran into one issue though. That is when I try to "Debug JS Remotely" I get this error.

I tried passing {jsonp: false} option into connect as suggested here. With that option I don't get the error. But it fails to establish connection and emit messages when that option is set.

[spotsadmin]

I want to add that I do have this code in the constructor of a root component.

    if (global.navigator && global.navigator.product === 'ReactNative') {
      global.navigator.mimeTypes = '';
      try {
        global.navigator.userAgent = 'ReactNative';
      }
      catch (e) {
        console.log('Tried to fake useragent, but failed. This is normal on some devices, you may ignore this error: ' + e.message);
      }
    }

[anjali14garg]

any updates on this issue

[spotsadmin]

The workaround that I am using is passing {jsonp:false} to io().
i.e., socket = new io(url, {jsonp:false});

With that, it doesn't error on debug. However, at least for me the socket.io-client doesn't function during debug. But I can debug the rest of the code. Not ideal.. but can survive :)

[hilkeheremans]

This is a little odd since we are not having any of these issues across three of our apps that are using this. It might be that we are doing some obscure magic there I can't immediately think of, and thus isn't documented. We are definitely not passing { jsonp: false}.

Regardless, this fork deserves a bit of an update (for, amongst others, a few security fixes in socket.io 1.x) as well as a check if it is still needed for socket.io 2.0, which switches to the much more efficient uwebsocket library.

I'll try to get a look at this soon, but I'm sure you can understand if I mention that we are a tiny company and thus don't really have the time to commit to support. It might take a while. Sorry!