Support For React Native Android

[skellock]

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.

[skellock]

Everything I just said was a lie.

Here it is working on android with version 0.4.0.

I'm happy this is working, but I'm so confused why it stumped me before. Was it that I forgot to adb port forward to reactotron's port? Did i have a borked copy of socket.io in my node_modules (i was playing around at one point).

I'll leave this issue open to both shame myself and see if I can get to the bottom of this later.

[skellock]

This was a self-imposed bug which was caused by the crazy merging of a default UserAgent for React Native. Overthinking it.

Android is good to go!

(don't forget to $ANDROID_HOME/platform-tools/adb reverse tcp:3334 tcp:3334 to get that port forwarding working -- only supports android 5+)