Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Can't open developer menu on Android (device or emulator) when error #11884

Open
beeteedubs opened this issue Feb 9, 2021 · 10 comments
Open

Can't open developer menu on Android (device or emulator) when error #11884

beeteedubs opened this issue Feb 9, 2021 · 10 comments
Labels
Android Expo Go The client distributed on app stores

Comments

@beeteedubs
Copy link

beeteedubs commented Feb 9, 2021 •
edited

Summary

Can't open developer menu on AVD or Android device when there's an error in the code. This makes it impossible to Enable Debug JS. This is ultimately to debug on VSCode or Chrome.

Attempts at resolving

  • Ctrl+M
  • adb shell input keyevent 82 (if USB connected or AVD)
  • shaking (only if AVD, lol jk)

Observations

  • the concentric circles w/ cross hashing always appear when I can't open developer menu

Following this tutorial: https://youtu.be/0-S5a0eXPoc?t=1829

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android

SDK Version (managed workflow only)

how do you even find that out?

Environment

Expo CLI 4.1.6 environment info:
System:
OS: Windows 10 10.0.18363
Binaries:
Node: 14.0.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
SDKs:
Android SDK:
API Levels: 29, 30
Build Tools: 28.0.3, 29.0.2, 30.0.3
System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
IDEs:
Android Studio: Version 4.1.0.0 AI-201.8743.12.41.6953283
npmPackages:
expo: ~40.0.0 => 40.0.1
react: 16.13.1 => 16.13.1
react-dom: 16.13.1 => 16.13.1
react-native: https://github.com/expo/react-native/archive/sdk-40.0.1.tar.gz => 0.63.2
react-native-web: ~0.13.12 => 0.13.18
Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

https://snack.expo.io/c7p_RBpXE

  • try debugging on AVD or Android Device without having Debug Remote JS already set with an error like the above
@beeteedubs beeteedubs added the needs validation Issue needs to be validated label Feb 9, 2021
@sydney-thompson
Copy link

I am experiencing the same problem! I found it following the same tutorial.

I tested this with both an emulator and a physical device with the same results. However, on an iOS emulator, this is not an issue.

@tannert
Copy link

tannert commented Feb 14, 2021

bump!

@lerubeta
Copy link

+1

4 similar comments
@Marion-Artigaut
Copy link

+1

@oliviajacquesbaker
Copy link

+1

@darthtater42
Copy link

+1

@HPRP01
Copy link

HPRP01 commented Feb 22, 2021

+1

@byCedric
Copy link
Member

Hi people! This is a hard one to fix, it's nested deeply in the Android app. It's not the best way, but there is a workaround.

Because the settings within the Android app is "shared" across your apps, you can open it if you just start a working project (e.g. a new one with expo init). You can enable or disable remote debugging, close it and start your project with the error. This also applies for the other way around, if you are stuck in remote debugging you can disable it like that.

Hope this helps!

@ldobreira
Copy link

+1

@brentvatne brentvatne changed the title expo can't open developer menu on Android (device or emulator) when error Can't open developer menu on Android (device or emulator) when error Mar 3, 2021
@brentvatne brentvatne added Expo Go Expo Go The client distributed on app stores Android and removed Expo Go needs validation Issue needs to be validated labels Mar 3, 2021
@brentvatne
Copy link
Member

please consider submitting a pull request to help with this if you are capable of doing so :)

if not, please refer to @byCedric's comment above:

Hi people! This is a hard one to fix, it's nested deeply in the Android app. It's not the best way, but there is a workaround.

Because the settings within the Android app is "shared" across your apps, you can open it if you just start a working project (e.g. a new one with expo init). You can enable or disable remote debugging, close it and start your project with the error. This also applies for the other way around, if you are stuck in remote debugging you can disable it like that.

Hope this helps!

we have made a note to investigate this. we have the information we need and so to ensure the above response remains prominent in this thread i am going to lock this

@expo expo locked and limited conversation to collaborators Mar 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Android Expo Go The client distributed on app stores
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests