-
Notifications
You must be signed in to change notification settings - Fork 261
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
Known issues of Hermes debugging #1266
Comments
Is №1 still happening? In the linked issue it looks like the issue is resolved on the Hermes side. |
@EricCornelson, we tried React Native |
Still seems to be an issue on React Native 0.67.3 as of 2022. Attempting to debug crashes the app on Android, where as iOS fails to connect to dev tools. |
The no.1 issue is still existing on Chrome debugger and Flipper. Keep tracking. |
The second issue is not repro currently. |
I have also noticed that Hermes debugging seems to fail whenever the app is reloaded. You must detach the debugger and reattach it. That makes it impossible to hit breakpoints that happen on app load. |
I'm having the issue described in https://stackoverflow.com/questions/73362632/react-native-typescript-number-0-read-as-nan where |
With expo 50.0.6 and react-native 0.73.4 debugging hermes doesn't work at all. Breakpoints never bind. May not be this plugin's fault however, it seems there are a lot of bugs in hermes CDP implementation. |
Trying to set a breakpoint with verbose logging shows this
|
This issue continues that one #1099 in terms of debugging via js-debug extension.
The extension has experimental support for React Native Hermes debugging. At this moment we know about several issues related to Hermes debugging. Please see the list of known issues below.
The table of problems consists of two columns: the first one illustrates the problem when the extension is used for debugging an Hermes app , the second one - when Google Chrome is used for debugging an app.
If you faced new issues with React Native Hermes debugging via React Native Tools, please send them to the commentaries section of this issue.
The list of issues
Hermes engine doesn't support
Runtime.callFunctionOn
method. See the issue Runtime.callFunctionOn returns an empty value on debugging.[Android]:Hermes app crash when a second debugger tries to connect ([Android]:Hermes app crash when a second debugger tries to connect facebook/hermes#792)
The text was updated successfully, but these errors were encountered: