From cfc9e07fe2ba33523b7b457ef309b5c67b3eedb7 Mon Sep 17 00:00:00 2001 From: Ananya Arun Date: Thu, 29 Jul 2021 04:55:38 -0700 Subject: [PATCH] Fix broken link Summary: Fixed a broken link in the troubleshooting page of flipper. Reviewed By: passy Differential Revision: D29986130 fbshipit-source-id: 2e771a511afa23e4c1e11aa3817c854eff56bcab --- docs/troubleshooting.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/troubleshooting.mdx b/docs/troubleshooting.mdx index 12e727c9a..6c7dc1902 100644 --- a/docs/troubleshooting.mdx +++ b/docs/troubleshooting.mdx @@ -145,7 +145,7 @@ implementation("com.facebook.react:react-native:+") { ## React Native -Make sure the project is using the [latest Flipper SDK](getting-started/react-native#using-the-latest-flipper-sdk). +Make sure the project is using the [latest Flipper SDK](getting-started/react-native.mdx#using-the-latest-flipper-sdk). When using Flipper with React Native, two devices should show up: @@ -187,10 +187,10 @@ That is correct, the dependencies won't be actually included in the release (whe The "Could not inspect element with id XXX" error will appear when selecting a specific element in the React DevTools, when the version of the DevTools shipped in Flipper is incompatible with the `react-devtools-core` package used by the React Native application. -Flipper supports using a globally installed `react-devtools` (after using `npm install -g react-devtools@x.x.x`) instead of the embedded one. +Flipper supports using a globally installed `react-devtools` (after using `npm install -g react-devtools@x.x.x`) instead of the embedded one. This should help with any compatibility issues. -Another way to fix this is to set the `resolutions` field in the `package.json` of the app to force a specific version and then run `yarn install`, for example: +Another way to fix this is to set the `resolutions` field in the `package.json` of the app to force a specific version and then run `yarn install`, for example: ```json "resolutions": {