Jake Howard

Besides just using a load of conditionals to check, what you could do is change the way node requires js files, and check if there's a `.android.js` or `.ios.js` version...

@julien-rodrigues whilstt that is a nice solution, we already support something like this. You can use 'Platform.__setOS' to set the OS programatically during tests. This should make things much easier...

@SandroMachado I'm going to need a _lot_ more information than that. You have to re render you component completely after changing the OS. We also currently dont support using platforms...

I believe most of these changes are fixed in #120 ?

Huh, that could definitely help the project continue. Definitely something i'd be interested in discussing! https://theorangeone.net/contact/

@JPeer264 i believe so, however it hasn't been tested in a few months, and there have been many versions of `react-native` in that time. Please feel free to try out...

@JPeer264 Looks like an issue related to both dependencies, and `react-native` changing their api (somehow?). Which is strange, seeing as everything worked fine the last time I tested it

That sounds like quite an issue, and likely one end users will have too. Potentially experimenting with moving all react-* dependencies to peer might solve the issue? As people will...

@jasonfma that sounds like a great idea. I've been out of the `react-native` (and mobile) scene for a while. Pivoted my work rather heavily. Yes I completely agree breaking backwards...

Theoretically, it should be a simple case of stubbing out the native modules related to those APIs, and possibly make them return sane values if required. I'm hoping none of...