Network request failed using fetch
See original GitHub issueš Bug Report
Summary of Issue
Network request failed
- node_modules/whatwg-fetch/dist/fetch.umd.js:527:17 in setTimeout$argument_0
- node_modules/react-native/Libraries/Core/Timers/JSTimers.js:130:14 in _callTimer
- node_modules/react-native/Libraries/Core/Timers/JSTimers.js:383:16 in callTimers
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:416:4 in __callFunction
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:109:6 in __guard$argument_0
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:364:10 in __guard
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:108:4 in callFunctionReturnFlushedQueue
* [native code]:null in callFunctionReturnFlushedQueue
Iāve no idea why but recently no fetching works and I get this error above. Itās so frustrating because I have no clue what the actual problem is. Iāve looked at similar bug reports and many of them say itās because of https
vs http
or LAN issues.
But I am using an external API with https
so it canāt be that. I am using useSWR but I am pretty sure it has nothing to do with that specific library. Itās either React Native/Expo or some problem with the whatwg-fetch
polyfill.
Environment - output of expo diagnostics
& the platform(s) youāre targeting
Expo CLI 3.28.0 environment info:
System:
OS: macOS 10.15.7
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.5.0 - ~/.nvm/versions/node/v14.5.0/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.5 - ~/.nvm/versions/node/v14.5.0/bin/npm
Managers:
CocoaPods: 1.9.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.1, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.6858069
Xcode: 12.1/12A7403 - /usr/bin/xcodebuild
npmPackages:
expo: ~39.0.2 => 39.0.3
react: 16.13.1 => 16.13.1
react-dom: 16.13.1 => 16.13.1
react-native: ~0.63.3 => 0.63.3
react-native-web: ~0.13.12 => 0.13.18
npmGlobalPackages:
expo-cli: 3.28.0
Expo Workflow: bare
Reproducible Demo
This one is actually difficult to demo as I donāt know how to reproduce.
Steps to Reproduce
I am using useSWR if thatās any good info. Other than that Iāve honestly no idea. I just am using fetch.
fetch(url, {
headers: {
Accept: 'application/json',
Authorization: `Bearer ${token}`,
},
}).then((res) => res.json())
Expected Behavior vs Actual Behavior
I shouldnāt get a Network request failed
error.
Issue Analytics
- State:
- Created 3 years ago
- Comments:18 (2 by maintainers)
Top Results From Across the Web
React Native fetch() Network Request Failed - Stack Overflow
1) To find out the exact error in the logs, I first enabled 'Debug JS Remotely' using Cmd + M on the app...
Read more >HTTP Fetch fails with "TypeError: Network request ... - GitHub
Using fetch to get/post on a HTTPS web server which is using a valid and trusted but not public CA. Using Chrome and...
Read more >Fetch Error : [TypeError: Network request failed] : r/reactnative
Fetch Error : [TypeError: Network request failed] ... The error FETCH 1 and FETCH 3 are the same except for FETCH1 I put...
Read more >Networking - React Native
Many mobile apps need to load resources from a remote URL. You may want to make a POST request to a REST API,...
Read more >Improve "TypeError: Network request failed" error message
Network request failed, this error occurs usually when api call failed or you have some internet issue. In android emulator, sometimes this error...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I found that by setting the āContent-Typeā header on the fetch request (in my case to āapplication/jsonā) fixes this issue.
I have the same issue ā¦ It was working previously ā¦ Here my code :
and here the result