Short answer
Check the URL first. If it starts with http://, iOS (App Transport Security) and Android 9 and later block it by default; use HTTPS, or add a narrow exception for your development host. If it says localhost, a phone or emulator cannot reach your computer that way: use your computer’s LAN IP, 10.0.2.2 on the Android emulator, or a tunnel. If it is HTTPS and still fails on Android, check that the server sends its full certificate chain. For uploads, do not set the multipart Content-Type header yourself.
Why the request never completed, and the fix
01
An http:// URL blocked by the operating system
“By default, iOS enforces App Transport Security (ATS), requiring any HTTP connection to use HTTPS.” React Native, Networking
Both platforms block plain HTTP by default. Use HTTPS for anything real. For a development server, add an exception only for that host (on Android as below, on iOS an NSExceptionDomains entry in Info.plist), not for every domain.
<!-- android/app/src/main/res/xml/network_security_config.xml --> <network-security-config> <domain-config cleartextTrafficPermitted="true"> <domain includeSubdomains="true">192.168.1.20</domain> </domain-config> </network-security-config> <!-- AndroidManifest.xml, on the application tag --> <application android:networkSecurityConfig="@xml/network_security_config">02
localhost on a phone or emulator
On a device, localhost is the device itself. The Android emulator reaches your computer at 10.0.2.2; a real phone needs your computer’s LAN IP on the same Wi-Fi, or a tunnel. The iOS simulator shares your Mac’s network, so localhost works there.
const API_URL = __DEV__ ? 'http://192.168.1.20:3000' : 'https://api.example.com';03
Android 9 and later block cleartext too
“On Android, as of API Level 28, clear text traffic is also blocked by default.” React Native, Networking
An app that works on iOS with an ATS exception can still fail on Android, which needs its own opt-in through a network security config or usesCleartextTraffic. In Expo, set android.usesCleartextTraffic with the expo-build-properties plugin in a development or production build (not Expo Go) rather than editing native files.
04
HTTPS that fails on Android, or a broken upload
Android rejects servers that do not send their intermediate certificate, even when browsers accept them; fix the chain on the server. For file uploads with FormData, leave Content-Type unset so the boundary is added for you.
const body = new FormData(); body.append('file', { uri, name: 'photo.jpg', type: 'image/jpeg' }); await fetch(url, { method: 'POST', body }); // no Content-Type header
Checked against the vendor’s docs on : React Native: Networking; Android: Network security configuration.
Rather hand it over?
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start
- from $450AI-Built App RescueA Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.See scope and start
Related: Axios “Network Error” · JavaScript “TypeError: Failed to fetch” · Firebase Auth “network-request-failed” · React Native text strings must be rendered within <Text>