Your API Is Up. Your App Still Gets Nothing. Here Is How I Debug It.

The ping succeeds. The health check is green. Postman returns JSON. And the mobile app? Empty lists, spinning loaders, silent failure.

If you build cross-platform products, you will live in this gap. I have — more than once — while shipping apps backed by Django REST APIs at Sybrix.

This is the checklist I use when the API is “up” but the product is broken.

1. Confirm which host the client actually calls

Sounds obvious. It is not.

I have seen production apps pointed at api.example.com while developers tested example.com/api. Different servers, different configs, different SSL certificates — same logo on the slide deck.

Fix: Log the base URL from a release build, not just debug. Compare it to the DNS and nginx config on the server.

2. Status code vs useful response

A 503 Service Unavailable from the edge is not the same as a 200 with an empty array. Clients often treat both as “no data” in the UI.

Fix: Inspect network traffic on a real device. Look at status, headers, and body — in that order.

3. Auth headers and token expiry

Mobile apps cache tokens. Refresh flows fail quietly. The API returns 401 or 403 and the UI shows nothing because error handling was “phase two.”

Fix: Force-logout and re-login on staging. Add temporary logging for auth failures in the client until the flow is solid.

4. Serialization surprises

Django REST serializers omit fields when permissions fail, nested relations are not prefetched, or pagination defaults change. The API “works” but the shape the app expects is gone.

Fix: Diff the JSON schema between environments. Version your API responses when mobile clients depend on them.

5. CORS is a web problem — mobile has different ones

Mobile apps do not care about CORS the way browsers do. They care about certificate pinning, cleartext HTTP blocks, and ATS on iOS. A “fixed” web API can still fail on device.

Fix: Test on physical hardware on cellular networks, not only Wi‑Fi simulators.

6. Caching layers lying to you

Cloudflare, nginx, WordPress object cache, API gateway caches — each can serve stale or error responses while you swear you deployed the fix.

Fix: Purge edge cache. Hit origin directly. Add a cache-busting query param once to prove the pipeline.

The mindset

Full stack cross-platform development means you do not stop at “the server is running.” You follow the request from button tap to database row and back to pixel.

That is unglamorous work. It is also why senior developers get paid: not because they know every flag, but because they know where to look next.

— Bashir Lucas Samson Lukman, Full Stack Cross-Platform Developer at Sybrix