Skip to content

Instantly share code, notes, and snippets.

@bvaughn
Last active October 13, 2022 18:34
Show Gist options
  • Save bvaughn/4bc90775530873fdf8e7ade4a039e579 to your computer and use it in GitHub Desktop.
Save bvaughn/4bc90775530873fdf8e7ade4a039e579 to your computer and use it in GitHub Desktop.
React DevTools: Unsupported backend version

Unsupported DevTools backend version

This page contains instructions for updating a local React DevTools application to match a version embedded in a renderer such as React Native. Instructions below cover NPM, Flipper, and React Native Debugger. If you use React DevTools in a different way, please let us know.

If you are viewing this page, you have likely seen one of the dialogs below:

Dialog displaying downgrade instructions for the React DevTools frontend to connect to an older backend version

Dialog displaying upgrade instructions for the React DevTools frontend to connect to a newer backend version

These dialogs indicate that the version of the React DevTools UI you are using has connected to an incompatible version of the DevTools "backend" (generally embedded into a renderer like React Native). The fix for this is to upgrade or downgrade the version of React DevTools UI that you're using. Below are instructions for several common ways of doing this.

Global NPM install

If you have React DevTools installed globally, you can update it by copying and running the NPM command shown in the error dialog. For example, to downgrade DevTools for an older backend:

npm i -g react-devtools@"<4.11.0"

Or to upgrade it for a newer backend:

npm i -g react-devtools@^4.13.0

Local NPM install

If you have React DevTools installed locally, the best thing to do is to pin it to use the same version as React Native. The npm explain command can tell you which version that is. For example:

$ npm explain react-devtools-core

react-devtools-core@4.10.0
node_modules/react-devtools-core
  react-devtools-core@"4.10.0" from react-devtools@4.10.0
  node_modules/react-devtools
    react-devtools@"4.10.0" from the root project

react-devtools-core@4.12.4
node_modules/react-native/node_modules/react-devtools-core
  react-devtools-core@"^4.6.0" from react-native@0.63.2
  node_modules/react-native
    react-native@"https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz" from the root project
    peer react-native@"*" from react-native-safe-area-context@3.2.0
    node_modules/react-native-safe-area-context
      react-native-safe-area-context@"3.2.0" from expo@41.0.1
      node_modules/expo
        expo@"~41.0.1" from the root project
    peer react-native@">=0.62.0-rc.0 <0.64.0" from @react-native-community/cli@4.14.0
    node_modules/@react-native-community/cli
      @react-native-community/cli@"^4.14.0" from react-native@0.63.2

The DevTools "backend" embedded in React Native example above comes from react-devtools-core version 4.12.4 but the DevTools "frontend" comes from version 4.10.0. These versions are incompatible. To fix this, either upgrade the react-devtools dependency to the same version:

npm i -d react-devtools@4.12.4 

Or if you a Yarn user, you could use a "resolution" to ensure that both versions resolve to the same backend:

"resolutions": {
  "react-devtools-core": "4.12.4"
}

Flipper embeds a specific version of React DevTools (typically the latest version). The exact version will be shown in the error dialog. For example, the dialog below shows version 4.12.4:

Dialog displaying downgrade instructions for the React DevTools frontend to connect to an older backend version

We recommend locking the embedded backend in React Native to the same version as the frontend using a Yarn "resolution":

"resolutions": {
  "react-devtools-core": "4.12.4"
}

If this approach does not work, please open an issue in the Flipper repository to explain your setup.

The React Native Debugger embeds a specific version of React DevTools (typically the latest version). The exact version will be shown in the error dialog. For example, the dialog below shows version 4.12.4:

Dialog displaying downgrade instructions for the React DevTools frontend to connect to an older backend version

We recommend locking the embedded backend in React Native to the same version as the frontend using a Yarn "resolution":

"resolutions": {
  "react-devtools-core": "4.12.4"
}

If this approach does not work, please open an issue in the React Native Debugger repository to explain your setup.

Something else

If you use React DevTools in a way that was not covered above, please let us know.

@steenhansen
Copy link

steenhansen commented Aug 2, 2022

Using React Native Debugger 0.12.1 (github.com/jhen409) on Windows

Did NOT "npm i -g react-devtools@<4.22.0" (note 4.22.0 and 4.14.0 versions)

npm list -g
+-- corepack@0.10.0
+-- eas-cli@0.57.0
+-- expo-cli@6.0.1
+-- npm@8.11.0
`-- yarn@1.22.19

package.json (note "react-native/react-devtools-core" NOT "react-devtools-core")
"resolutions": {
"react-native/react-devtools-core": "4.14.0"
},
"dependencies": {
"@react-navigation/native": "^6.0.11",
"expo": "~45.0.0",
"expo-status-bar": "~1.3.0",
"react": "17.0.2",
"react-dom": "17.0.2",
"react-native": "0.68.2",
"react-redux": "^8.0.2",
"redux": "^4.2.0"
},

  1. delete node_modules
  2. "yarn install" as "npm install" does not work
  3. celebrate

@mateuszbaszaraba
Copy link

If you are struggling with this error
image

--Here is my solution--

in package.json file:

"dependencies": {
    "react-devtools": "4.14.0",
    "react-devtools-core": "4.14.0",
    ...
  },

"resolutions": {
    "react-devtools-core": "4.22.0"
  },

I had global react-devtools-core installed (4.25.0 version) but I uninstalled it. (npm uninstall -g react-devtools-core)
Result of my npm list -g:

├── corepack@x.x.x
├── expo-cli@y.y.y
└── npm@z.z.z

React Native Debugger: v0.12.1
React Native: v0.64.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment