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
Hermes debugger can't connect in Windows 10/11 #4
Comments
EDIT You can find the current recommended practices here: #4 (comment) If you're on windows, it looks a lot like facebook/flipper#1520. Can you try launching with your host in localhost mode? If you're not in Windows, can you pass along the RN version and your plugin config? |
Hi @jakobo. Thanks for the help! Not sure if I got closer or further away. 😀 Flipper now shows the app & phone correctly but none of the plugins enable and I get more items in the log. The |
P.S. - What hardware setup do you use? If you're using Mac and an iPhone I can take the time to switch over knowing it will work. I recently got a 16' Macbook M1 Pro to play with but keep coming back to my Windows machine because of the OLED display. 😀 I'd love to get Windows debugging working but I'd like get this memory leak in the app debugged even more. 😝 |
EDIT You can find the current recommended practices here: #4 (comment) My current setup is Windows 10 + WSL, with Android Emulator and iOS Device (SDK 44). However, I'm not currently running Hermes. This is most likely an issue with networking to WSL and networking at this point. I did a writeup about the networking woes here: https://codedrift.com/thunked/running-expo-in-windows-subsystem-for-linux-wsl2 The tl;dr of the piece is go get WSLHostPatcher https://github.com/CzBiX/WSLHostPatcher which will allow your WSL instances to listen to the parent host IP. You can then launch with |
Same problem here, when using package.json
environment
|
@gloredo |
EDIT You can find the current recommended practices here: #4 (comment) Getting some more bandwidth to dig into what's going on here. Do you mind sharing the Podfile (with redactions if needed) generated in Specifically, we should see:
If we have those lines, then we should see if v8 can connect to Hermes outside of Flipper. Instructions. If we can connect using Chrome, then it is likely something about our Podfile setup that's needed for WSL compatibility. If we can't connect, then it's very likely a networking issue caused by WSL running in a NAT instead of a proper bridged network. |
Hey @jakobo. Thanks for the response. |
EDIT You can find the current recommended practices here: #4 (comment) That's helpful information! Since all we're doing is modifying the Podfile, I think trying to connect the chrome debugger to hermes will be a good next step as it takes Flipper out of the picture completely and we can figure out if this is a windows networking issue or a Flipper/RN issue. |
Hi, I have the same issue. I on Win 10 Pro, Android simulator, Expo 44, Flipper client 140. If I select any of them, it opens the DevTools but I get this error in the console:
Something is working though, because if I pause the debugger the application stay frozen until I resume script execution. |
EDIT You can find the current recommended practices here: #4 (comment) @obasille I believe that's unrelated. The error in console is probably because in Chrome you've got automatic sourcemaps turned on. ( |
Thanks! I'm running with I'm not sure I understand about |
Sorry, the WSL UsersYou need to install and run WSLHostPatcher, as Windows is awful at forwarding everything along to the WSL instance. This app uses the Windows Detours framework to enable WSL listening on The majority of connection problems related to WSL come from expo (and react-native) binding to the local IP. When using Non WSL Windows UsersThere appears to be a few related issues for Flipper in Windows 10 and 11, which I've linked below for visibility.
If we've exhausted these, we should either open or 👍🏻 a related issue in the Flipper repository. I'm also happy to modify the README about potential issues when using Win 10/11. |
Thank you @jakobo! |
were you able to make it work on windows? |
Nope (without using WSL) |
Also not connecting on:
|
@mitramejia do you mind sharing your |
Same issue on Windows 7/SDK 45/Android. |
@slapbox, as mentioned above, can you share your edit with SDK 45 out now, I've added an explicit note to the readme about windows + hermes. Advanced thanks to those who also reported it upstream on the fbflipper thread: facebook/flipper#3433 |
For others in this thread, SDK 46 now has a better way to initialize flipper in the Podfile, and some daring souls have figured out how to launch Flipper so it can find metro (!!!) and find Hermes (!!!x2). #19 for details. I'm going to close this as fixed, but lets open a new issue if in SDK 46 people are having issues w/ the Hermes configuration. |
Just crediting folks for their hard work on this. @all-contributors please add @GollyJer for bugs (and thank you for helping work through these issues) |
I've put up a pull request to add @GollyJer! 🎉 |
Edit By Maintainer: Please see the upstream Hermes + Windows Issue If you are running into this bug, please include your Expo SDK version (which tells us what React Native version you are using) and include your
Podfile
from runningexpo prebuild
so that we can provide additional information to the Flipper team. ❤️(Original report below)
I'm curious if anyone has gotten the Hermes plugin to work.
React DevTools works great but I get this when trying to pull up Hermes (which our app is using).
And this is all that's logged.
Is the Hermes plugin even expected to work?
Thanks!
The text was updated successfully, but these errors were encountered: