[Android]:Hermes app crash when a second debugger tries to connect

[Heniker]

Description

When a second debugger connects to the application that already has a connected debugger - the application crashes.

The error only happens on Android debugger:

hyIkpYIb3X.mp4

Here is what happens on iOS:

7TO1YvW5rI.mp4

---

Metro does not show warning on Android and the app crashes.

Is it possible to make Android behavior consistent with iOS? - the app should not crash and Metro should show a warning when another debugger connects.

Version

0.66.3

Output of npx react-native info

System:
    OS: Windows 10 10.0.19043
    CPU: (12) x64 AMD Ryzen 5 2600X Six-Core Processor
    Memory: 13.15 GB / 31.93 GB
  Binaries:
    Node: 14.18.1 - D:\scoop\apps\nvm\current\nodejs\nodejs\node.EXE
    Yarn: 1.22.15 - D:\scoop\apps\yarn\current\Yarn\bin\yarn.CMD
    npm: 6.14.15 - D:\scoop\apps\nvm\current\nodejs\nodejs\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 29, 30
      Build Tools: 30.0.0, 30.0.2, 30.0.3
      System Images: android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
    Windows SDK:
      AllowAllTrustedApps: Enabled
      AllowDevelopmentWithoutDevLicense: Enabled
  IDEs:
    Android Studio: Not Found
    Visual Studio: Not Found
  Languages:
    Java: 1.8.0_312 - D:\scoop\apps\openjdk8-redhat\current\bin\javac.EXE
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.66.3 => 0.66.3
    react-native-windows: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce

0. Create React Native app npx react-native init AwesomeProject and enable Hermes
1. Start React Native Android Hermes app
2. Connect to app with a debugger (e.g. flipper)
3. Connect to app with another debugger (e.g. chrome)
4. The second debugger won't work correctly
5. The third connection will crash the app (if flipper was used it will try to reconnect automatically)

Snack, code example, screenshot, or link to a repository

No response

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.