nitro-fetch

Call prefetchOnAppStart with a URL and prefetchKey after sign-in; the request is persisted and replayed natively on the next cold start. On Android you must also add AutoPrefetcher.prefetchOnStart(this) in Application.onCreate, while iOS bootstraps automatically.

Create a custom axios adapter that calls the fetch export from react-native-nitro-fetch and pass it to axios.create. A correct adapter must handle baseURL, params, timeout, signal, responseType, and validateStatus rather than just JSON-parsing every response.

Replace new WebSocket with new NitroWebSocket, convert numeric readyState checks to strings like 'OPEN', replace addEventListener with property assignment, drop binaryType in favor of e.isBinary, and send only string or ArrayBuffer payloads.

No. React Native DevTools hooks XMLHttpRequest, and nitro-fetch bypasses XHR entirely via Nitro and JSI. Use the built-in NetworkInspector for JS-level visibility or Perfetto and Instruments traces for native DNS, TLS, and TTFB breakdowns.

The most common causes are a missing or mismatched prefetchKey between the prefetch and the consuming fetch, the entry expiring past the default 5-second TTL, or the missing AutoPrefetcher.prefetchOnStart line in Android's Application.onCreate.

Yes. Call prewarmOnAppStart with the wss URL, protocols, and headers; native code opens the socket before React Native loads and buffers messages. Your screen adopts the warm connection by constructing NitroWebSocket with the exact same URL.