Android studio Emulator ( device unauthorized)

Question

I know that on a normal device I have to authorize the debugging process, but Authorizing it on an emulator is my first time.

I just installed my first emulator on my home pc to do some work stuff, and this poped up.

Any idea what is the cause or is it normal for android o api 26 google play SDK?

PS: I am using windows version at home.

possibly a duplicate, take a look at: https://stackoverflow.com/q/26079838/1008011 you may have to also authorize on your emulator — chornge, Oct 03 '17 at 20:20
i did those except unplugging my device since it is an emulator. i also started developer option on emulator but didn't get the prompt — Mohammad Tabbara, Oct 03 '17 at 20:24
Is your ADB integration enabled? You can try disabling it and then re-enabling it with `Tools > Android > Enable ADB Integration` — chornge, Oct 03 '17 at 20:27
is it possible to create a new emulator and try again? if possible, try with a nexus 5 or nexus 5x (comes with google play and android-oreo) — chornge, Oct 03 '17 at 20:32
Now i got another problem the emulator just black screens then crashes — Mohammad Tabbara, Oct 03 '17 at 20:42
Made a new emulator then fixed the black screen by changing the settings to use hardware graphics. And Bam every thing works thanks. — Mohammad Tabbara, Oct 05 '17 at 20:29

score 12 · Accepted Answer · answered Oct 06 '17 at 07:50

12

Issue Resolved.

Step 1- Made a new emulator(Any). Step 2- then fixed another problem the black screen by changing the settings to use hardware graphics.(Dunno if this problem was related to the bug)

And Bam every thing worked.

answered Oct 06 '17 at 07:50

Mohammad Tabbara

1,438
1
16
31

3

Except that for me there is no option to use hardware graphics. The control exists, but you get exactly one choice: automatic. It's grey and doesn't react to clicks. – James Moore Nov 12 '17 at 18:45
4

Try to choose another emulator that isn't with a google play but a google api image. U can edit it then. Btw i updated to android 3.0 and it happened again for me so I switched to use genymotion. – Mohammad Tabbara Nov 13 '17 at 19:17
3

I had same issue due to emulator with google play and resolved. – atifali Nov 15 '17 at 10:43
Worked like a charm for me too - Windows 10. – nonbeing May 04 '18 at 08:40
strange but work – Xin Meng Apr 07 '22 at 07:55

AllanRibas · Answer 2 · 2019-09-29T04:01:03.270

3

when this happens you can request permission through the emulator demonstrative video

But on the android Q api 29 emulator, when USB debugging is requested, the alert is gone before it can be confirmed, and the emulator bugs, preventing the emulator from connecting. I am not able to solve, just resetting and losing everything to solve.

edited Sep 29 '19 at 04:01

answered Aug 29 '19 at 02:03

AllanRibas

678
5
14

This exactly happens to me, still an issue in February 2021 – yalcinozer Feb 19 '21 at 11:26

score 2 · Answer 3 · edited Oct 14 '19 at 11:30

2

TOOLS-->AVDMANAGER

Click on tooltip on the right side, you can see wipe data before doing that turn off your emulator.

This Worked for me.

edited Oct 14 '19 at 11:30

Jitesh Prajapati

2,533
4
29
51

answered Oct 14 '19 at 11:08

lava

6,020
2
31
28

score 2 · Answer 4 · answered Jul 25 '20 at 22:29

2

I was facing the same issue and tried all most all the suggested steps but following worked for me :

Steps:

Delete all the emulators with google play.
Create new emulator without google Play .
Now if you run the emulator, no authorization issue will be there

Or

An another approach to fix this issue is : Steps:

let your emulator launch
Go to settings and enable the "USB debugger" option as you normally do in real time devices(5 click on Developer Options->build number)

answered Jul 25 '20 at 22:29

amarnath roy

21
1

Deleting ALL emulators and creating a new one without Google Play fixed it for me. After that I was able to create a new emulator with Google Play and that one worked as well. My problem started after moving my emulators to another storage partition, I probably didn't update all relevant .ini files. – npace Sep 15 '20 at 06:57

score 1 · Answer 5 · answered Sep 11 '18 at 14:35

I found a mismatch between the .android/adbkey* files associated with the user running the process running adbd, and the same file associated with the user running the emulator.

I don't know about windows, but this is possible in Linux if you run adb as root to work around file permissions.

Fix: As the user running the emulator, type this into a command shell:

adb kill-server; adb devices

score 1 · Answer 6 · answered Aug 30 '21 at 18:23

1

Delete your Emulador, then Create an emulador without google play services, it can be Android Q (Android 11). It worked for me.

answered Aug 30 '21 at 18:23

Rafael Alejandro Navarro Herna

11
1

score 0 · Answer 7 · answered Apr 05 '19 at 15:55

0

For this to work for me I had to start a new emulator from android studio with Oreo instead of Pie as a system image.

answered Apr 05 '19 at 15:55

Steven Heffner

21
3

score 0 · Answer 8 · answered May 16 '19 at 10:01

0

Just delete the ~/.android folder.

answered May 16 '19 at 10:01

Mercy Reuben

17
1

score 0 · Answer 9 · answered Jan 17 '20 at 13:20

I also face the same issue and its generated because I copied my SDK from one PC to another PC with Same configuration(Software and Hardware). Now I create an emulator on Pie and also tried Oreo but unauthorised comes for both.

Solution: I delete my build tools, platform tools, emulator only not complete SDK and download all of them again. Now I create my emulator for all type of Version and now no unauthorised error for all type of emulators.

score 0 · Answer 10 · answered Mar 08 '20 at 21:33

Keep the Emulator on
Delete android folder using

rm -rf ~/.android
Then restart adb

adb kill-server
You should get a prompt on the emulator to allow USB Debugging
View the device status

adb devices

This should fix the issue, I used this to fix when I was having issues launching the emulator from expo when making a react native app.

score 0 · Answer 11 · answered May 16 '20 at 12:19

0

Had the same issue, none of the answers here worked, eventually found the following worked for me:

Create a new emulator without Google Play and start it, visual studio detects it on first start and the device will be authorised.

answered May 16 '20 at 12:19

Luke Alderton

3,198
1
23
34

score 0 · Answer 12 · answered Aug 04 '21 at 06:29

I fixed this issue on my Arch Linux while I'm developing Flutter apps, by deleting all of the emulator devices and create a new emulator without the Google Play Store.

Also, in the Graphics setting don't forget to choose Hardware Graphics instead of Automatic and the device will be available and detected.

score 0 · Answer 13 · answered Aug 30 '21 at 18:27

0

Create an emulador without google play services, it can be Android Q (Android 11). It worked for me.

answered Aug 30 '21 at 18:27

Alex

265
3
6

score 0 · Answer 14 · edited Jan 11 '23 at 10:30

0

I fixed it on Win10. When adding new device, choose Android 11 (without Google play)

edited Jan 11 '23 at 10:30

Riccardo

1,083
2
15
25

answered Jan 09 '23 at 22:25

Murcha

1
1

Android studio Emulator ( device unauthorized)

14 Answers14

Linked