Hermes debugger won't connect

[alex-trofimov]

🐛 Bug Report

Hi. I'm experiencing issues when trying to get Hermes debugger to work with an Expo app. Hope this is the right place to discuss.

I found a similar issue but it's closed and the solutions listed there don't seem to work for me.

This is what I see in hd's windows after I start the app (expo start --dev-client):

Selecting either option leads to:

If I start metro manually (react-native start --host 0.0.0.0) I get the following window instead:

Flipper itself works fine. Debugging hermes via chrome devtools also works fine.
Been fighting this issue for a week now. Will appreciate any help!

localhost:8081/json

Flipper logs

To Reproduce

1). Check out this example repo: https://github.com/alex-trofimov/flipper-hermes-issue
yarn install

2). Make a build with expo eas (or you could use this one) and install it on a device.

3). Start the project:
yarn run metro
yarn start

4). Open Flipper, make sure that the app is connected, navigate to Hermes debugger.

5). ???

Environment

OS: Windows 10
Flipper version: 0.131.1 (tried all the versions from 0.125 to 0.133.1)
SDK: expo 44
Device: emulator, android 8.1

[alfredarcifa]

Same error : #3549

OS: macOS Monterey
Flipper version: 0.138.0
Device: emulator iOS

hermes-chrome-inspector-conn (20): EXC_BAD_ACCESS (code=EXC_I386_GPFLT)

_LIBCPP_INLINE_VISIBILITY
__value_func& operator=(nullptr_t)
{
__func* __f = _f;
_f = nullptr;
if ((void*)__f == &_buf)
__f->destroy();
else if (__f)
__f->destroy_deallocate(); >>>> hermes-chrome-inspector-conn (16): EXC_BAD_ACCESS (code=1, address=0x464019d4a100)
return *this;
}

[obasille]

Hi!
I have what look like the same issue on Win 10 Pro 64, trying to debug an Android simulator build.
I'm using Expo 44 + Flipper 125.

[Nantris]

Same issue with Expo 45 + Flipper 144 on Windows 7 x64.