Skip to content

Update part10a.md #2922

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/content/10/en/part10a.md
Original file line number Diff line number Diff line change
Expand Up @@ -210,6 +210,9 @@ That might actually be enough in most cases, but sometimes we need more.

**NB:** If the debugger can't connect to the application and you see the error message "Another debugger is already connected", make sure that <i><http://localhost:19000/debugger-ui></i> is not open in some browser tab.

Only after adding "expo": {....., "jsEngine": "jsc"} to app.config.js, React Native Debugger works. After that, add correct port to React Native Debugger, and click 'Debug Remote Js' button on emulator.
https://docs.expo.dev/guides/configuring-js-engines/

Next, we need to start our application and connect to the debugger. Start the application by running <em>npm start</em>. Once the application is running, open it with either an emulator or the Expo mobile app. Inside the emulator or the Expo mobile app, open the developer menu by following the [instructions](https://docs.expo.dev/debugging/tools/) in the Expo's documentation. From the developer menu, select <i>Debug remote JS</i> to connect to the debugger. Now, you should be able to see the application's component tree in the debugger:

![React Native Debugger](../../images/10/24.png)
Expand Down