jens/flipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix broken link

Browse Source 
Summary: Fixed a broken link in the troubleshooting page of flipper.

Reviewed By: passy

Differential Revision: D29986130

fbshipit-source-id: 2e771a511afa23e4c1e11aa3817c854eff56bcab
This commit is contained in:
Ananya Arun
2021-07-29 04:55:38 -07:00
committed by Facebook GitHub Bot
parent 6c72e78d04
commit cfc9e07fe2
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/troubleshooting.mdx
View File

@@ -145,7 +145,7 @@ implementation("com.facebook.react:react-native:+") {
## 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: 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. 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. 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 ```json
"resolutions": { "resolutions": {