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.

Sign up for GitHub

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

Jump to bottom

Can't continue debugging React Native TypeScript app once breakpoint is hit #1041

Closed
lukaspechar opened this issue Jun 22, 2021 · 1 comment
Closed

Can't continue debugging React Native TypeScript app once breakpoint is hit #1041

lukaspechar opened this issue Jun 22, 2021 · 1 comment
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@lukaspechar
Copy link

@lukaspechar After some more investigation, we noticed that the hang occurs while processing the result of the Debugger.getScriptSource method. Based on the CDP Proxy logs, this method was not called in vscode v1.56.2.

image

It seems that the problem caused by updating js-debug version, which React Native Tools uses to debug applications. You may open an issue in the js-debug repository. For now, there is a workaround to downgrade the version of your vscode up to version v1.56.2. Feel free to contact us if you have any other questions or need our help in solving this problem.

Originally posted by @JiglioNero in microsoft/vscode-react-native#1598 (comment)
@lukaspechar lukaspechar changed the title @lukaspechar After some more investigation, we noticed that the hang occurs while processing the result of the Debugger.getScriptSource method. Based on the CDP Proxy logs, this method was not called in vscode v1.56.2. Can't continue debugging React Native TypeScript app once breakpoint is hit Jun 22, 2021
@connor4312
Copy link
Member

Duplicates #1033

@connor4312 connor4312 added the *duplicate Issue identified as a duplicate of another issue(s) label Jun 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lukaspechar @connor4312