Android Emulator "Allow USB Debugging" dialog close right after showing

Question

I'm trying to debug with Android R in Pixel emulated devices w/ PlayServices but the "Allow USB Debugging" dialog instantly close right after showing, so I can't click in "Allow" to AS connect to the AVD. I went to Developer options in Android to switch off and on again the USB debugging, but again the dialog close imediatelly right after showing. I tried kill/star ADB and unistalling all AS/user configs/etc and reinstalling again but didn't solve. Anyone has a clue?

Are you using a real device or emulator? – cdevansh Sep 16 '20 at 15:49 — cdevansh, Sep 16 '20 at 15:49
AS emulator, up to date. – Maurício Lima Sep 16 '20 at 17:17 — Maurício Lima, Sep 16 '20 at 17:17

score 9 · Answer 1 · edited Jun 22 '21 at 13:55

9

Seems like this issue is related to your emulator's API version, after some testing I found that Pixel 4 API 30 have your problem, while others don't.

Versions

Another odd thing about the box is that it will ask you again for permission when you start a new session, even though I clicked the "always allow this device" button.

edited Jun 22 '21 at 13:55

Machavity

30,841
27
92
100

answered Jun 22 '21 at 10:03

Ng Lok Chun

199
2
10

7

Pixel 3a API 30 also has the same problem. – Jaineel Mamtora Sep 20 '21 at 10:09
1

Pixel 3 API 30 also has the same problem. – Viktor Brešan Feb 23 '22 at 14:30
I stick to pixel 2. – Ng Lok Chun May 08 '22 at 04:26

score 7 · Answer 2 · answered Mar 10 '21 at 00:51

7

Wipe data and it will pop up and stay. Check the "always allow debugging on this device" box and you should be good to go.

answered Mar 10 '21 at 00:51

MandelMech

467
4
6

score 5 · Answer 3 · edited Apr 25 '22 at 08:59

5

Try remove files adbkey and adbkey.pub in:

~/.android/adbkey/ on Linux
%UserProfile%\.android on Windows
%ANDROID_SDK_HOME%\.android on Windows, if set

adb kill-server
adb devices

Restart the emulator after wiping its data. Then the permission for "USB Debugging" should be given and it should show up as debuggable device.

The problem should only appear with google_apis_playstore devices, see here. Reason I think is, that the key files are only copied by adb, if no other keys already exist on the emulator. So may deleting the files on the emulator may also work.

edited Apr 25 '22 at 08:59

Viktor Brešan

5,293
5
33
36

answered Jan 09 '22 at 22:15

User Rebo

3,056
25
30

It didn't help in my case. Dialog is still disappearing before I have a chance to click on it. – Viktor Brešan Apr 24 '22 at 05:42
@ViktorBrešan did you change the `ANDROID_SDK_HOME` or `ANDROID_PREFS_ROOT` variable? Make sure any old keys are deleted in any possible `.android` directory. If so, there shouldn't come up a dialog at all, the keys are then copied automatically to your device and you should be able to debug without confirming :) – User Rebo Apr 24 '22 at 13:54
1

It wasn't problem with folders, I have slightly 'corrected' your answer. – Viktor Brešan Apr 25 '22 at 09:00

score 4 · Answer 4 · answered Dec 24 '20 at 12:43

4

get your public key from ~/.android/adbkey.pub
append it to /data/misc/adb/adb_keys of emulator (create it if not exist)
restart emulator

then you should connect directly.

ref: How to solve ADB device unauthorized in Android ADB host device?

answered Dec 24 '20 at 12:43

user2767141

134
5

1

Unfortunately nothing worked, not even uninstalling Android Studio, the only way to work is to select a non-PlayServices from the AVD list. – Maurício Lima Apr 20 '21 at 12:57
i experience the same as @MaurícioLima . also, how would you put the key on the device if you cannot connect to it..? – mx1up Apr 27 '21 at 15:58

score 2 · Answer 5 · answered Sep 02 '22 at 09:21

2

This problem occurs with Pixel emulators on API level 30, so choosing 31 instead will solve the issue.

answered Sep 02 '22 at 09:21

Johannes Nyman

21
2

score 1 · Accepted Answer · answered Dec 02 '20 at 23:42

1

I had the same issue. I tried to click "Allow" in time, but it was too fast on my PC. However, I noticed that after a cold boot this popup pops and doesn't hide for some time (may be due to load lag), so I managed to click it this way.

If someone still has this problem and the goal is to upload some file or apk, better upload it to google drive and download it by link in the emulator.

answered Dec 02 '20 at 23:42

UnholyRaven

368
3
9

2

Actually this is the only way I managed to run the apk, copying and installing it, the AVD doesn't connect to the Android Studio and after 300 seconds give a message that waited and wasn't able to connect. – Maurício Lima Apr 27 '21 at 14:41

score 1 · Answer 7 · edited Feb 17 '22 at 06:05

1

I solved this problem by following steps:

Wipe emulator data
Start emulator again

Above steps resulted in no dialog at all, weird, then I looked at the Android Studio, the emulator was already connected.

edited Feb 17 '22 at 06:05

Dharman

30,962
25
85
135

answered Feb 17 '22 at 05:59

Muhammad Faizan

1,891
2
18
37

Same situation for me, after wipe it was already authorized/connected – QuantumBlack Apr 09 '23 at 20:31

PRANAV SINGH · Answer 8 · 2022-09-10T05:54:36.217

0

After some experiments I found that x86 apis were showing this error so simply switching to x86_64 apis solved the problem :

edited Sep 10 '22 at 05:54

answered Sep 09 '22 at 20:40

PRANAV SINGH

1,000
11
17

score 0 · Answer 9 · answered Mar 08 '23 at 17:33

In my case, it was because I had enabled an accessibility app. At least, after trying various things (turning on/off developer mode, USB debugging, etc.;, rebooting and so on), I disabled that accessibility service, and voila, the "Allow USB debugging" was back to normal!

Android Emulator "Allow USB Debugging" dialog close right after showing

9 Answers9