Right now, socket.io isn't working too well on Android.
There's a whole series of errors around globals not being setup in the right way. For example, it expects navigator to be in the global scope AND in the window scope. Strange.
It also expects String, Object, and Date properties on window.
So after all that gets fixed, it still doesn't work 100% with websockets.
We can fall back to Long Polling, but that relies on arraybuffer support in XMLHttpRequest. React Native doesn't support that yet.
facebook/react-native#6870 will be arriving in 0.25. So i'll revisit then.
Right now,
socket.ioisn't working too well on Android.There's a whole series of errors around globals not being setup in the right way. For example, it expects
navigatorto be in the global scope AND in thewindowscope. Strange.It also expects
String,Object, andDateproperties onwindow.So after all that gets fixed, it still doesn't work 100% with websockets.
We can fall back to Long Polling, but that relies on
arraybuffersupport in XMLHttpRequest. React Native doesn't support that yet.facebook/react-native#6870 will be arriving in 0.25. So i'll revisit then.