Device is unauthorized

[red-avtovo]

Latest emulator doesn't provide debugging option enabled by default, which doesn't allow to run automation on Android 7.x

Operating System:
Debian 9

Docker Image:
butomo1989/docker-android-x86-7.1.1

Docker Version:
18.03.1-ce, build 9ee9f40

Docker Command to start docker-android:

docker run -d \
	--privileged \
	--restart=unless-stopped \
	--link selenium-hub:hub \
	-p 6080:6080 \
	-p 4724:4723 \
	-e DEVICE="Nexus 5" \
	-e APPIUM=True \
	-e CONNECT_TO_GRID=True \
	-e APPIUM_HOST="ip" \
	-e SELENIUM_HOST="hub" \
	-e APPIUM_PORT=4724 \
	-e SELENIUM_PORT=4444 \
	-e MOBILE_WEB_TEST=True \
	-e BROWSER=chrome \
	--name android-container711 \
	butomo1989/docker-android-x86-7.1.1

Expected Behavior

Device is authorized or at least asking for authorization, like on android 8.x images

Actual Behavior

[budtmo]

I think it is possible to do it manually under Developer Option @red-avtovo , but yes, we need to automate it somehow.

[red-avtovo]

I'm digging in it and I really hope, that this is just 1 argument to avd creation or emulator starting

[diemol]

I bumped into the same issue some weeks ago, the root cause is because when the emulator is using Google Play Services it assumes that it is a "production build", so no root access is possible.

To install apps and so on, adb uses the common mechanism of private and public keys. And this error pops up when the emulator does not have the public key of the adb server.

The way I fixed it in our project was to do "adb devices" before starting the emulator. This is implicitly starting the adb server and generating the keys before the emulator is started, and when the emulator starts it will have the adb server keys.

That is what needs to be automated in order to have it working.

[red-avtovo]

Will try that! Thank @diemol

[red-avtovo]

@diemol that would be super easy, but it didn't work. I see the keys, but emulator doesn't know about them.

[red-avtovo]

I solved an issue by starting emulator with -wipe-data flag.

[budtmo]

Hi @red-avtovo ,

Could you create a PR for it? It would be great.

[diemol]

ah ok, the adb devices thing works when the AVD has not been created yet, which is the approach I was using (and I omitted that part).

Your solution seems pretty good as well, I didn't think about it :) But I guess that can make the boot process slightly slower?

[red-avtovo]

I didn't make a PR yet, because I'm pretty sure, that we need this tweak just for first container run.
After container restart that would be quite annoying to loose all data.

[budtmo]

Fixed in release 1.2