-
Notifications
You must be signed in to change notification settings - Fork 956
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
[Android] Device plugin 'Hermes Debugger (RN)' is not supported by the selected device #3983
Comments
Been seeing this for weeks. Not sure if it's related to the Flipper version or what. I've tried upgrading/downgrading seemingly everything without resolution on a previously working project using API 32 and React Native 0.68. |
Tried API 31 and 33 now also, in new emulator devices. I've tried all the steps on the Flipper troubleshooting page, I've tried rebooting the machine, upgrading Android Studio, upgrading Always always this problem I never had before a few weeks ago:
@mweststrate @passy I'm really sorry to ping you, but do you have any ideas? I'm out of theories to even try and we're dead in the water without the ability to debug. Is there anything we should look for in our Device Logs to indicate what the issue may be? Regarding the troubleshooting step: "Make sure the mobile SDK you are using is relatively recent (<1 month old)." -- this refers to the package version for Edit: Spent at least another two hours onthis, but no progress at all :( |
I really hate to bump an issue so early after my first comment, but I've spent more than an entire day on this and made no progress. There does not appear to be anything actionable from my end to make this work, nor any clues for how we could - but we desperately need it to work. |
The issue for me was custom port, and special env parameter for custom port didn't work. There definitely should be port number somewhere in settings and it should work. |
And also there should be a proper message why plugin is not available, but not Flipper is a pure pain 💩 |
@gentlee thanks for your reply! Can you share what custom port you were using? We're not using any custom port to my knowledge, unless plugins can change the port.
I couldn't agree more. It led me on a wild goose chase to figure out what was wrong with my emulator, but apparently nothing is wrong there. Sadly, I have no idea where something might be wrong. |
Every time a new update comes out I hope and pray that it will fix Flipper, upgrade the app and the This same device used to work, and now no device works. Are there some debug logs or something else I can do to try to figure out why I'm seeing this message? I've already enabled the maximum level of debugging in Flipper and see no obvious issues. All of my ports seem to be doing what I'd expect too, though I'm not 100% sure it's all correct - but nothing else is using any of the ports. |
No firewall enabled and Really tough to do anything with React Native when you can't debug it and you spend twice as long trying to fix debugging issues as you do coding... |
Same issue on physical devices. Affects iOS app also, which previously connected but now won't; same version of app that worked before, old version of Flipper, new version of Flipper, doesn't matter. I tried deleting No VPN enabled, truly nothing I can think to try. Note: I made sure to not run the emulator while trying to connect the physical device |
Also affects other projects we have, which also used to work - again, across machines... |
It stopped working for us unless specifying |
It works for me until today, and it turns into no support. I found there is a new version of Flipper, try to install the new version but the same problem still happens. 15 minutes ago it worked :( |
@Vietvantue if you're using Expo see: jakobo/expo-community-flipper#19 (comment) Even if you're not, maybe it will lead you to the right solution. Randomly we started to need to set the But if it worked 15 minutes ago, I assume you're already sure it's not some change in your code that caused it? Did you try rebooting the machine? |
Exact same issue on my end, everything is on latest version Expo Ejected "react-native": "^0.69.6",
"expo": "^46.0.16",
"react-native-flipper": "^0.172.0",
"redux-flipper": "^2.0.2", Android
Opening the debugger menu open Chrome Dev Tool, then crashes with OOM. I tried: METRO_SERVER_PORT=19000 open -a Flipper #!/bin/sh
adb reverse tcp:8081 tcp:8081
# flipper
adb reverse tcp:5037 tcp:5037
adb reverse tcp:8088 tcp:8088
adb reverse tcp:8089 tcp:8089
adb reverse tcp:9088 tcp:9088
adb reverse tcp:9089 tcp:9089
adb reverse --list console.log(!!global.HermesInternal);
// true With little luck |
I got this issue on my second project and the solution was similar to my previous one:
|
@zhangstar666 did you find any solution? I have the exact same scenario here. |
This blog post is a godsend and fixed the problem for me: https://hsiang.dev/debugging-flipper-desktop-app-clfkttntg000609kyd3kd1mz4 Long story short Flipper reaches to the Metro URL and then checks that the document returned contains one of the two strings:
And then the solution is to find your
PS: This is an awful way to check whether Metro is running. |
Hi folks. Any updates about that? I Have the same problem here, and tried the workarounds listed here. Nothing works. Same problems on emulators or real devices. |
Faced that issue on my 3rd project. The fix was to use 0.235.0 version (for 0.239.0 it doesn't work). |
Here any version <= 0.237.0 works. |
Flipper 0.235 works fine for me. Here's all old releases https://github.com/facebook/flipper/releases |
I tried what the above answer has stated, enabling react native device and seems like hermes no loger is available for in-browser distribution 👎 |
🐛 Bug Report
I can't get Hermes debugger working - it is unavailable. Got "Device plugin 'Hermes Debugger (RN)' is not supported by the selected device". Created multiple emulators - nothing.
Other plugins like Databases and Layout work.
How can device not support the plugin?
To Reproduce
custom metro port: 8082
enableHermes: true
FLIPPER_VERSION=0.156.0
Initialization:
app/build.gradle
Environment
devDeps:
Using custom port for metro 8082.
The text was updated successfully, but these errors were encountered: