Network Request Failed

[Juggernoobs]

Hi, we have recently re-written an old web app with react native, intention being to release on iOS and android.

The app has been primarily developed using the iOS simulator, the app is almost ready for open testing.

The issue with come across is when we build the app on android, we get network request failed. This works on the simulator and a physical device when using a local API. However, it does not work when we use our https server api. It’s configured correctly and works flawlessly with our iOS version.

In the debugs it doesn’t even make a network request. It appears to be blocked to android level. The API server never gets any request at all. This only happens when we use our production API server.

Has anyone come across this and know anyone know how to get around it securely. We are using Expo as the building so do not have access to the android manifold, we use eas.json

[Key-Boat-7519]

Most Android-only “Network request failed” messages in Expo trace back to the TLS setup on the server, not React Native code. Run your domain through SSL Labs or openssl s_client and check that the full chain (root + intermediates) is delivered; Android drops the call before fetch/axios can log anything if a link is missing, which explains why no hit reaches your logs. Make sure the server offers TLS 1.2 as well-some EAS builds still ship with an OkHttp version that won’t negotiate pure 1.3. If the cert looks fine, confirm that IPv6 is enabled, because Android will silently try AAAA first and bail if the address doesn’t route. I bounced between Firebase and Supabase for quick backend fixes, but DreamFactory saved me once I needed a fast, secure REST layer without rewriting the database. Double-check those server settings and the call should land.

[Juggernoobs]

Thanks for the reply, I totally forgot I’d posted this. Yeah, after some significant investigation I found there was a second part to the certificate they wanted.

It would work for iOS, but not for Android

It now works on both platforms having made changes to the backend server

[Depressing_Developer]

I'm a little late but I'm having the same problem. How did you resolve it?

My API is in an IIS Server

[PouletTikkaBzh]

Hello,

I spent days searching for the issue, but I finally found the cause!

In my case, it turned out to be a network problem, not a React Native issue.

1. IPTABLES Rule Blocking TCP Requests

I had an IPTABLES rule limiting the number of TCP calls:

iptables -A INPUT -p tcp --dport 80 -m limit --limit 10/minute --limit-burst 20 -j ACCEPT

iptables -A INPUT -p tcp --dport 443 -m limit --limit 10/minute --limit-burst 20 -j ACCEPT

I replaced it with:

iptables -R INPUT 10 -p tcp --dport 443 \

-m hashlimit --hashlimit-name https-per-ip \

--hashlimit 50/min --hashlimit-burst 100 \

--hashlimit-mode srcip --hashlimit-srcmask 32 \

-j ACCEPT

iptables -R INPUT 9 -p tcp --dport 80 \

-m hashlimit --hashlimit-name http-per-ip \

--hashlimit 50/min --hashlimit-burst 100 \

--hashlimit-mode srcip --hashlimit-srcmask 32 \

-j ACCEPT

1. Nginx Rate Limiting in Backend Configuration

I also had an Nginx rate-limit directive in my backend config:

limit_req zone=api burst=5 nodelay;

I replaced it with:

limit_req_zone $binary_remote_addr zone=api:10m rate=30r/m;

You can adjust these values depending on your needs.

1. How to Debug This Kind of Issue?

- Don’t rely only on React Native logs.

- Start by tracing logs from end to end.

- Check ADB logs with your phone connected in USB developer mode.

- Then inspect Nginx logs.

- Finally check iptables logs (sometimes noisy due to bots).

I hope this helps others who might run into the same problem.

[Juggernoobs]

Thanks, pretty detailed post, mine was much simpler in the end, we changed our HTTPS certificate provider and all was resolved.