React Native apps make network calls through fetch, Axios, or native modules — all of which ultimately send standard HTTPS requests. That means you can debug them by capturing the device's traffic, seeing exactly what your app sent and what the server returned, without wiring up a desktop proxy.

Why Capture on the Device?

Remote debuggers and in-app network loggers are useful, but they only show what your JavaScript layer sees. Capturing on the device with Moni Proxy shows the real wire traffic, including requests from native modules and third-party SDKs, and works the same way on iOS and Android.

  • API debugging: inspect the exact request and response for any fetch/Axios call.
  • Auth troubleshooting: confirm tokens and headers are attached correctly.
  • Backend issues: read decrypted responses to isolate client vs server bugs.
  • SDK auditing: see what bundled native SDKs send over the network.

How It Works

Moni Proxy runs an on-device proxy with a local certificate authority. Each HTTPS request is captured, decrypted, and displayed with full detail, grouped by domain. There is no Wi-Fi proxy to configure and no requirement that your phone and computer share a network.

Step-by-Step

  1. Install Moni Proxy and finish the one-time certificate trust setup.
  2. Start a capture session.
  3. Run your React Native app and trigger the requests you want to inspect.
  4. Open any entry to view headers, query parameters, and the decrypted body.
  5. Mock or rewrite responses to test error handling and edge cases.

A Note on Certificate Pinning

If your app pins certificates (for example via a TrustKit-based native module), pinned connections will not be decryptable by design. Disable pinning in debug builds for apps you control; production pinned traffic will stay opaque, which is intended.