207

I'd like to view my network requests in React Native to help me debug - ideally in the 'Network' tab of Chrome's devtools.

There are some closed issues about this on GitHub (https://github.com/facebook/react-native/issues/4122 and https://github.com/facebook/react-native/issues/934) but I don't entirely understand them. It sounds like I need to undo some of React Native's polyfills and then run some commands with extra debugging flags, and maybe modify some Chrome security settings? And apparently there are some security issues involved in doing this that might make it a terrible idea, but nobody involved in the thread has explicitly stated what they are.

Could somebody provide a step-by-step guide to getting the Network tab working with React Native, as well as an explanation of the security issues involved in doing so?

17 Answers 17

268

I'm not sure why no one has pointed out this solution so far. Use React Native Debugger - https://github.com/jhen0409/react-native-debugger! It is the best debugging tool for React Native in my opinion and it gives Network Inspection out of the box.

Take a look at these screenshots.

Right click and select 'Enable Network Inspect' Enabling Network Inspect

Right click and select 'Enable Network Inspect' Enabling Network Inspect

Debug away! Network Inspect in action

14
  • 40
    If you're skimming and see this answer, note that you MUST right-click and Enable Network Inspect for it to work. By default, it does not. Commented Jun 24, 2019 at 16:38
  • 6
    Wow, why is this feature hidden by a right click on the main panel. Never knew that existed. Game changer. Json responses weren't showing up...show up straight away on toggle. Thanks!
    – Matt
    Commented Apr 27, 2020 at 17:19
  • 5
    More like why isn't this the default behaviour whenever we visit the Network tab or mark as a setting (checkbox or some sorts) inside that tab!
    – CyberMew
    Commented Aug 2, 2020 at 9:02
  • 2
    You can make it a default by setting the config file: github.com/jhen0409/react-native-debugger/blob/master/docs/…
    – nicholascm
    Commented Sep 25, 2020 at 3:09
  • 2
    Doesn't seem to work with RN Firebase queries. Possibly because they are made from inside a native plugin. Otherwise, this is pretty cool, and yes - should be enabled by default. Commented May 5, 2022 at 23:22
114

This is what I've been using in the entry point of my app

const _XHR = GLOBAL.originalXMLHttpRequest ?  
    GLOBAL.originalXMLHttpRequest :           
    GLOBAL.XMLHttpRequest                     

XMLHttpRequest = _XHR

EDIT: frevib linked to more concise syntax below. Thanks frevib!

GLOBAL.XMLHttpRequest = GLOBAL.originalXMLHttpRequest || GLOBAL.XMLHttpRequest;

Explanation:

GLOBAL.originalXMLHttpRequest refers the Chrome Dev Tools copy of XHR. It is provided by RN as an escape hatch. Shvetusya's solution will only work if the dev tools are open and thus providing XMLHttpRequest.

EDIT: You will need to allow cross origin requests when in debugger mode. With chrome you can use this handy plugin.

EDIT: Read about the RN github issue that lead me to this solution

7
  • 5
    After I put that piece of code I am able to see the request in the Developer Console but all my request fail with a 404 status. Anyone has any idea why that might happen? Commented Jan 24, 2017 at 9:09
  • 1
    This works. Took this from Github
    – frevib
    Commented Jul 28, 2017 at 8:33
  • 1
    This doesn't work for me. I use android emulator, and the network tab shows empty even requests are being sent Commented Aug 27, 2017 at 12:37
  • 22
    This doesn't work any more, following error comes up in the console (not sure what change caused this): Uncaught Error: unsupported BodyInit type at Response.Body._initBody (fetch.js:231) at new Response (fetch.js:390) at XMLHttpRequest.xhr.onload (fetch.js:437) Commented Mar 23, 2018 at 23:30
  • 2
    Works on my side on React Native Debugger with this one-liner set-up. Thanks a million times, @tryangul Commented May 30, 2019 at 15:44
54

I use the following in my app ( Add this in your main app.js entry point file ) :

// To see all the requests in the chrome Dev tools in the network tab.
XMLHttpRequest = GLOBAL.originalXMLHttpRequest ?
    GLOBAL.originalXMLHttpRequest :
    GLOBAL.XMLHttpRequest;

  // fetch logger
global._fetch = fetch;
global.fetch = function (uri, options, ...args) {
  return global._fetch(uri, options, ...args).then((response) => {
    console.log('Fetch', { request: { uri, options, ...args }, response });
    return response;
  });
};

The best thing is that it also shows the fetch logs in the console as well which are well formatted.

Screenshot:

enter image description here

On the network tab:

enter image description here

4
  • At which point of the original request is this fired on? I am actually thinking of using this as a mechanism to fire refresh tokens if a response has a 401. Is there an issue with that?
    – tushar747
    Commented Jul 19, 2018 at 9:07
  • FANTASTIC Sankalp! I have had trouble getting Reacotron working without crashing my Metro builder. Your solution works great. Even works in React Native Debugger.
    – mediaguru
    Commented Jul 30, 2018 at 11:34
  • The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'localhost:8081' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute. Commented Nov 14, 2018 at 6:28
  • 4
    Where exactly am I supposed to add it in app.js? I added this at the top and I get a render error "GLOBAL is not defined" Commented Mar 21, 2023 at 12:54
40

I use Reactotron for tracking network request.

enter image description here

4
  • 3
    this is actually the best solution out of all answers here (for me).. super easy to set up and don't have all the side effects of using chrome
    – Blue Bot
    Commented Sep 29, 2018 at 10:08
  • What are the side effects of using chrome you're worried about? Reactotron uses the Chromium Embedded Framework. Commented Nov 14, 2019 at 15:11
  • Mine is connected to device but not catching every requests, only on first load. Why is that? Commented Oct 14, 2020 at 5:55
  • As react-native-reanimated-2 doesn't work in debug mode, this is the only solution that allows me to view the network requests.
    – bonniss
    Commented Oct 8, 2021 at 6:04
29

If you are looking to debug network requests on a release version of your app you can use the library react-native-network-logger. It lets you monitor and view network requests within the app from a custom debug screen.

List of all requests Single request details
react-native-network-logger list react-native-network-logger details

You can then put this behind a build flag or a network flag to disable it for users in the production app.

Just install it with yarn add react-native-network-logger then add this at the entry point of your app:

import { startNetworkLogging } from 'react-native-network-logger';

startNetworkLogging();
AppRegistry.registerComponent('App', () => App);

And this on a debug screen:

import NetworkLogger from 'react-native-network-logger';

const MyScreen = () => <NetworkLogger />;

Disclaimer: I'm the package author.

4
  • This is awesome. I want these info in json whenever application send request. I found getRequests method which return all request in json but how can i get whenever application send request? Commented Jun 8, 2021 at 9:01
  • import NetworkLogger from 'react-native-network-logger'; const MyScreen = () => <NetworkLogger />; where shold i place these codes
    – vivek kn
    Commented Dec 10, 2022 at 7:39
  • You can put it in any one of your view either as it's own screen or a sub component. Have a look at the example here github.com/alexbrazier/react-native-network-logger/blob/master/…
    – braza
    Commented Dec 11, 2022 at 11:24
  • What sort of user permissions are required?
    – Umair A.
    Commented Feb 26 at 19:27
12

I know this is an old question, but there's a much safer way to do this now that does not require disabling CORS or altering the React Native source code. You can use a third party library called Reactotron that not only tracks API calls (using the network plugin), but also can track your Redux store, and Sagas with additional setup:

https://github.com/infinitered/reactotron https://github.com/infinitered/reactotron/blob/master/docs/plugin-networking.md

4
  • Reactotron seemed to work only if you used external library called apisauce. It doesn't work for normal fetch. So if you want to monitor requests send by external libraries in your app, reactotron is no good. Commented Aug 27, 2017 at 12:35
  • 1
    @VilleMiekk-oja in fact reactotron supports Networking with Fetch since March, it's just the documentation was outdated. I tried it myself, and corrected it on the readme :) Commented Nov 3, 2017 at 14:07
  • this works excellent; I've seen so many issues with: GLOBAL.XMLHttpRequest = GLOBAL.originalXMLHttpRequest || GLOBAL.XMLHttpRequest;
    – Petrogad
    Commented Mar 21, 2018 at 15:05
  • 1
    reactotron is really easy to configure and useful to track network calls of react-native applications
    – Ram
    Commented Jun 5, 2018 at 18:19
11

Please be careful with this code.

XMLHttpRequest = GLOBAL.originalXMLHttpRequest ?
   GLOBAL.originalXMLHttpRequest : GLOBAL.XMLHttpRequest;

It helps and it's great but it destroys upload. I spend 2 days trying to figure out why uploaded files are sending [object Object] instead of the real file. The reason is a code above.

Use it for regular calls not but for multipart/form-data calls

1
  • 2
    Dawid I have had a major problem trying to figure out why my image uploads from react native produced [object Object]. Just about gave up. I ran across this comment while trying to get network activity in the debugger on another app. I have yet to test out what you said, but I THANK YOU anyway. It's the first decent clue I've gotten on why my uploads were broken.
    – mediaguru
    Commented Mar 10, 2021 at 0:18
10

If you have an android phone or emulator,

  • npx react-native start

Then open the Android Studio.

Open the android folder of your project as a Android Studio Project.

enter image description here

Click that blue icon which it is Android Profiler

After the Android Profiler start, you can add your app via grey plus icon near the SESSIONS label enter image description here

Now you can inspect networking via this tool. You can see triangles that shows your network activity.

Please check this for more info about inspecting network traffic.

1
  • UPDATE: Network logs has its own separate tab now "Network Inspector", just of the right side of profiler Commented Apr 4, 2023 at 12:27
9

I was able to debug my requests in Chrome by deleting polyfill that React Native provides after importing React Native.

var React = require('react-native');
delete GLOBAL.XMLHttpRequest;

This worked for me for same origin requests. Not sure if you need to disable CORS in Chrome to make it work for cross origin.

3
  • What's a "same origin" request, in the context of requests made from a React Native app? One that's on the same domain as the debugger (i.e. probably localhost)?
    – Mark Amery
    Commented Dec 16, 2015 at 15:11
  • for my case you have to disable CORS in Chrome to make it work for cross origin. check this chrome plugin :chrome.google.com/webstore/detail/allow-control-allow-origi/… Commented Jan 29, 2016 at 8:57
  • @MouhamedHalloul can you explain how did you use this plugin?
    – alexmngn
    Commented Jun 12, 2016 at 19:08
6
  1. Open Android Studio → App Inspection → Select a process to connect to → Network Inspector
  2. Use the app and execute some requests
  3. Click on Network Inspector Visualization
  4. Observe the new panel of Connection View and Overview with request and response.

enter image description here

GL

1
  • thanks, this is the first time i notice the app inspector in android studio. In the response body, sometimes it returns it and other times not. if anyone knows why this is happening , I'd highly appreciate it 🙏 Commented Aug 6, 2024 at 10:35
5

In the past I used GLOBAL.XMLHttpRequest hack to track my API requests but sometimes it is very slow and didn't work for assets requests. I decided to use Postman’s proxy feature to inspect HTTP communication going out from phone. For details look at the official documentation, but basically, there are three easy steps:

  • Set up the proxy in Postman
  • Check your computer’s IP address($ ifconfig)
  • Configure HTTP proxy on your mobile device in wifi settings
5

these days, Flipper is the move.
https://fbflipper.com/

official announcement about this here:
https://reactnative.dev/blog/2020/03/26/version-0.62

3

I suggest using Charles to inspect your network requests. It's really good and provide more visibility and allows you to do advanced stuff.

http://charlesproxy.com

3
  • 1
    Just tried Charles and it seems to only capture http://localhost:8081/index.android.bundle?platform=android&dev=true .. how to make it capture ALL requests? (I am hitting an external api) Commented Jan 6, 2016 at 20:09
  • Is your external API uses HTTPS? If so, you need to configure Charles a little bit to catch those as well.
    – Ran Yefet
    Commented Jan 9, 2016 at 11:24
  • when using android, charles can be a bit problematic to capture outgoing requests. you need to 'manually' configure your simulator to access charles (and last time i tried, going in the config panel wouldnt do the job -- proxy ip needed to be passed in from a command line instantiation).
    – joe
    Commented Apr 4, 2019 at 17:02
1

At the time I'm answering, the react native inspector has this network section that you can see all the requests, but I recommend using other react native debugger client, because with this one is not that good to debug the requests at a tiny phone screen. (You can open the inspector by shaking your phone or pressing Shift + d or Ctrl + m, and pressing "Toggle Inspector" or "Show Inspector".

react native inspector with opened network tab

1

Step-by-Step Guide to Set Up Flipper for React Native

Flipper, a DevTool Platform for React Native, has been available since React Native version 0.62. After generating a project with react-native init, Flipper integration is ready for debug builds.

  • For a detailed guide on setting up Flipper for React Native, please refer to the official Flipper documentation: Flipper React Native Getting Started.

  • Once installed, open Flipper on your computer.

  • Run Your Application:

    npm run android or npm run ios

  • Enable Network Plugin in Flipper: In the Flipper application on your computer, go to the Network section. Ensure that the Network plugin is enabled. If not, you can enable it from the plugin management section in Flipper.

  • Debug Network Requests: With your application running and connected to Flipper, you should now see all network requests in the Network section. You can inspect requests, responses, and other network details directly from Flipper.

-1

[edit] you can easily integrate flipper with react native apps and get all the logs like device logs, react native logs, the network inspector, etc. You can install plugins to monitor the redux actions also, there are several other plugins available for flipper. Please make use of this, very handy and user friendly dev tool for react native. https://fbflipper.com/docs/getting-started/react-native/ [10 Jan 2023]

[old answer] have you guys tried the react-native debugger which comes with the react-native itself? you can enable this by pressing ctrl + M then you can select the open show inspector / toggle inspector

ios emulator android emulator

1
  • At least at the time I wrote this question, that was only an element inspector, with no support for viewing network requests. Has that changed? This answer doesn't say.
    – Mark Amery
    Commented Jun 13, 2021 at 17:07
-28

Add Debugger in the js where you can see the req or response

1
  • lol why this answer is downvoted so much. i used to do this before I know any devtools is existed. put console.log on response, console.error on catch block, and console.time to estimate request time, and there you go Commented Mar 17, 2021 at 5:50

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.