search

robinpowered / react-native-fetch-polyfill

Exposes options to React Native's XMLHttpRequest that are not accessible by `whatwg-fetch`
71 stars 23 forks source link

Not working in android emulator #6

Open vijayst opened 7 years ago

vijayst commented 7 years ago

I created a minimum example for react-native-fetch-polyfill. I set a timeout of 5 seconds. The timeout worked in iOS simulator but not working in Android emulator. In Android emulator, fetch times out only after 60 seconds.

vijayst commented 7 years ago

Looks like it is a problem with react-native android. Opened an issue in react-native repo: https://github.com/facebook/react-native/issues/14134

techrah commented 7 years ago

What about on Android devices (not simulator)? Also broken?

vijayst commented 7 years ago

@ryanhomer It is working fine on Android devices.

pstanton commented 6 years ago

not working on android device over adb. tried with chrome debugger on and off.

atticoos commented 6 years ago

@pstanton what version of React Native are you running, and what device are you using that reproduced this problem?

pstanton commented 6 years ago

https://github.com/robinpowered/react-native-fetch-polyfill/issues/7#issuecomment-364006398

terreb commented 6 years ago

Wow, the issue was created quite some time ago, but still not fixed! Any update?

joeythelantern commented 6 years ago

Still doesn't work on Android Simulator. +1

zachdunn commented 6 years ago

Wow, the issue was created quite some time ago, but still not fixed! Any update?

@terreb + @joeythelantern Appreciate the attentiveness. This is one of our "Help Wanted" tagged issues, and we'd be happy to review any pull requests you'd like to submit for this one.

ktownsend-cbre commented 6 years ago

I just ran into this problem. I'm hoping this isn't broken on device, but can't confirm that behavior until tomorrow.

TuurDutoit commented 5 years ago

As per my comment on another issue in this repo, this makes sense. The discrepancy between the Android and iOS implementations is probably the culprit.