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

Current Issues with Hermes Direct Debugging #12982

Open
1 of 10 tasks
TatianaKapos opened this issue Apr 25, 2024 · 1 comment
Open
1 of 10 tasks

Current Issues with Hermes Direct Debugging #12982

TatianaKapos opened this issue Apr 25, 2024 · 1 comment

Comments

@TatianaKapos
Copy link
Contributor

TatianaKapos commented Apr 25, 2024

Problem Description

In React Native Windows, we've observed a regression in Hermes Direct Debugging across versions 0.72.x, 0.73.x, 0.74.x, 0.75x, and 0.76x. While we're actively working on a patch for these versions, we recommend using Web Debugging as an alternative while this issue is still open. You can find instructions for Web Debugging here. Thank you for your patience as we work to get a fix out!

Current Open Issues

  1. Area: Debug Infrastructure Area: Developer Experience Area: JavaScript Engine External Scenario: VSCode Scenario: Visual Studio Workstream: Developer Experience bug
    vmoroz
  2. Area: Debug Infrastructure Area: JavaScript Engine Scenario: NuGet Workstream: Developer Experience bug
    vmoroz
  3. Area: JavaScript Engine Needs: Dev Design Workstream: Developer Experience enhancement
    aeulitz
  4. Area: Debug Infrastructure Area: Fabric Developer First Experience New Architecture Parity: Fabric vs. Paper Workstream: Developer Experience bug
    acoates-ms
  5. Area: Debug Infrastructure Area: Developer Experience Developer First Experience Scenario: Visual Studio Workstream: Developer Experience bug
    vmoroz
  6. Area: Debug Infrastructure Area: Developer Experience Area: JavaScript Engine Workstream: Developer Experience bug
    vmoroz
  7. Area: Debug Infrastructure Workstream: Developer Experience bug
    vmoroz
  8. bug
  9. Area: Debug Infrastructure Area: Tests Integration Follow-up Workstream: Test Coverage bug
    Yajur-Grover
  10. Area: Developer Experience Area: JavaScript Engine Scenario: Upgrade bug
    vmoroz
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Apr 25, 2024
@TatianaKapos TatianaKapos pinned this issue Apr 26, 2024
@chrisglein chrisglein added Area: Debug Infrastructure Area: JavaScript Engine Area: Developer Experience and removed Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) labels Apr 29, 2024
@chrisglein chrisglein added this to the Next milestone Apr 29, 2024
@gabor-seres-sap
Copy link

Unfortunately, Web Debugging is not an option for those who want to use synchronous calls to native module methods according to https://microsoft.github.io/react-native-windows/docs/debugging-javascript#web-debugging

Furthermore, some parts of RN, such as synchronous calls to native module methods, only work when running on the embedded JS engine. Such native methods won't work when using Web Debugging.

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

No branches or pull requests

5 participants