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

Debug "out of sync" for web extensions using pwa-extensionhost approach #140218

Closed
alefragnani opened this issue Jan 6, 2022 · 2 comments
Closed
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)

Comments

@alefragnani
Copy link

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.63.2
  • OS Version: macOS Big Sur 11.6.1

Steps to Reproduce:

  1. Create a brand new web-extension, using yo code
  2. Open in VS Code
  3. Add a breakpoint on any line of code
  4. Build and Start Debugging (which means the pwa-extensionhost approach)
  5. Try to run the Hello World command
  6. You will notice the breakpoints are out of sync

Kapture WebExtension Debug Out of Sync - Short

I'm trying to update my extensions to be web ready, but even being apparently able to produce the web-ready portion of an extension, the debugging process is not working correctly (and I really like to debug stuff on each scenario).

I tried to skip the debugging process and test the extension using the Sideload approach explained in the documentation, but had no success either, as commented here #138623 (comment). In this case, I'm not sure it is an issue in the tooling or my machine.

Thank you

@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label Jan 6, 2022
@weinand
Copy link
Contributor

weinand commented Jan 6, 2022

I can reproduce this.

@weinand weinand assigned connor4312 and unassigned weinand Jan 6, 2022
@connor4312
Copy link
Member

Duplicates #136242

@connor4312 connor4312 added the *duplicate Issue identified as a duplicate of another issue(s) label Jan 6, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Feb 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants