Skip to content
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

Debugger not working in react native with typescript #2276

Closed
arjunAbcd opened this issue Jan 14, 2025 · 4 comments
Closed

Debugger not working in react native with typescript #2276

arjunAbcd opened this issue Jan 14, 2025 · 4 comments

Comments

@arjunAbcd
Copy link

arjunAbcd commented Jan 14, 2025

Debugger Not Working.

When attempting to debug, breakpoints are displayed as grey circles. Hovering over them shows the message: Unbound breakpoint.

launch.json Configuration:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Attach to Hermes application",
      "request": "attach",
      "type": "reactnativedirect",
      "cwd": "${workspaceFolder}"
    }
  ]
}

Environment Details:
React Native Version: 0.76.3

Debug Console Output:

Attaching to the application  
Connecting to 8081 port  
NOTE: You are using an unsupported debugging client. Use the Dev Menu in your app (or type `j` in the Metro terminal) to open React Native DevTools.  
Bridgeless mode is enabled  ...

Added the following configuration to tsconfig.json:

{
  "compilerOptions": {
    "target": "ES5",
    "module": "es2015",
    "outDir": "out",
    "sourceMap": true
  }
}

Attempted Solution:

added launch.json with Attach to packager.

Despite this, the debugger issue persists. Looking for assistance or insights to resolve the problem.

@lexie011
Copy link
Collaborator

Hi @arjunAbcd, thanks for reaching us. Can you please try the solution provided by #2230 to see if it resolve your issue?

@EzioLi01
Copy link
Collaborator

RN 0.76 is switching to the new debug experience, we have updated it in master, but since ADO pipeline is in upgrading, the latest version is not released, please try above comment firstly.

@arjunAbcd
Copy link
Author

Hi @arjunAbcd, thanks for reaching us. Can you please try the solution provided by #2230 to see if it resolve your issue?

This is working fine now. Thanks @lexie011

@EzioLi01
Copy link
Collaborator

Cool, close issue as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants