Skip to content
This repository has been archived by the owner on Oct 2, 2021. It is now read-only.

Redundant inline breakpoints on Expo app debugging in VS Codeย #531

Open
@RedMickey

Description

Hi, we are the development team of VS Code extension for debugging React Native apps (vscode-react-native). We implemented inline breakpoint support in our extension and this approach works without problems, but we found out a feature on Expo apps debugging in VS Code Insiders. It seems that inline breakpoints are set on React components markup, besides JS code.
So I describe our steps for VS Code Insiders and Google Chrome:

  1. Launch Expo debugging in VS Code Insiders / attach to Expo app in Google Chrome
  2. Set the first breakpoints
Debugging Expo in Google Chrome Debugging Expo in VS Code
Screen Shot 2019-10-08 at 12 44 56
In Google Chrome inline breakpoints aren't set automatically at all.
Screen Shot 2019-10-08 at 12 21 11
Inactive breakpoints are set automatically.
  1. Set more breakpoints, including inline ones and try to debug
Debugging Expo in Google Chrome Debugging Expo in VS Code
Screen Shot 2019-10-08 at 12 32 30 There aren't inline breakpoints. Screen Shot 2019-10-08 at 12 25 54As seen some of breakpoints are set on React components markup and they can't be reached.
I marked unreachable breakpoints (red check mark).

I attached Expo app debugging logs.

We suppose that inline breakpoints functional should work in VS Code Insiders the same way as in Google Chrome. Could you please help us to understand what could cause such a behavior?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions