问题
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.
回答1:
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.
回答2:
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
回答3:
Just delete the ~/.android folder.
回答4:
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.
回答5:
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.
回答6:
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.
来源：https://stackoverflow.com/questions/46552660/android-studio-emulator-device-unauthorized