Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fetch takes so much time to start #20728

Closed
msafayasar opened this issue Aug 18, 2018 · 4 comments
Closed

Fetch takes so much time to start #20728

msafayasar opened this issue Aug 18, 2018 · 4 comments
Labels
🌐Networking Related to a networking API. Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@msafayasar
Copy link

Environment

Environment:
OS: macOS High Sierra 10.13.6
Node: 8.9.1
Yarn: 1.3.2
npm: 5.5.1
Watchman: 4.9.0
Xcode: Xcode 9.4.1 Build version 9F2000
Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: ^0.55.4 => 0.55.4

Description

In both on Android (emulator and device) and IOS (simulator and device) sometimes fetch request does not start immediately. Most of the time I need to wait for 10-60 secs in order to start fetch. It happens at all of the fetch requests all over the app. I wrote a middleware to inform me when a request comes and most of the time it is about 10-60 seconds. But sometimes it works immediately. I am sure my server side code is not that slow. I tested it. But I cannot understand this behavior of fetch. Also my website is https, not http.

On the other hand, it happens more on Android than IOS. I think there is some kind of bug in fetch or maybe there is a conflict in node modules.

Reproducible Demo

I am not sure if we can reproduce this issue but I googled it for over 2 weeks and I nearly read all posts, comments about fetch in github and stackoverflow. I couldn't find any solution for it. Thus, I think there is some kind of bug or maybe there is a conflict in node modules but I am not sure.

@react-native-bot react-native-bot added 🌐Networking Related to a networking API. ⏪Old Version labels Aug 18, 2018
@react-native-bot
Copy link
Collaborator

Can you reproduce the issue on the latest release, v0.56?

@franzejr
Copy link

@msafayasar maybe if you create a simple example that it happens sometimes other person could try to reproduce it too ? I've been using fetch and I'm not seeing this issue.

@msafayasar
Copy link
Author

msafayasar commented Aug 19, 2018

Actually I am facing the same problem with #20405

Maybe not the same because @john-hu says that it never resolves. In my case it resolves but sometimes immediately, sometimes takes about 60 seconds and more

@react-native-bot
Copy link
Collaborator

I am closing this issue because it does not appear to have been verified on the latest release, and there has been no followup in a while.

If you found this thread after encountering the same issue in the latest release, please feel free to create a new issue with up-to-date information by clicking here.

@react-native-bot react-native-bot added the Ran Commands One of our bots successfully processed a command. label Sep 3, 2018
@facebook facebook locked as resolved and limited conversation to collaborators Sep 3, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Sep 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🌐Networking Related to a networking API. Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

3 participants