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.

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

Device Unauthorized when using IMG_TYPE=google_apis_playstore #2

Open
lucasaas98 opened this issue Nov 1, 2023 · 2 comments
Open

Comments

@lucasaas98
Copy link

lucasaas98 commented Nov 1, 2023

Issue

I am following the readme as I am interested in creating an android emulator with playstore.
The idea is that I would be able to run scrcpy to check the output. However, I keep getting the following error:

adb connect <IP>:5555
failed to authenticate to <IP>:5555

and with scrcpy:

scrcpy
scrcpy 2.1 <https://github.com/Genymobile/scrcpy>
ERROR: Device is unauthorized:
ERROR:     --> (tcpip)    <IP>:5555      unauthorized
ERROR: A popup should open on the device to request authorization.
ERROR: Check the FAQ: <https://github.com/Genymobile/scrcpy/blob/master/FAQ.md>
ERROR: Server connection failed

Steps followed:

docker build \                                                                                                                                 
  --build-arg API_LEVEL=28 \
  --build-arg IMG_TYPE=google_apis_playstore \
  --build-arg ARCHITECTURE=x86 \
  --tag android-emulator .

docker run -it --rm --device /dev/kvm -p 5555:5555 android-emulator

Problems found

scrcpy says:

ERROR: A popup should open on the device to request authorization.

And following their docs it says we can connect via usb to solve this with the flag --otg or we need to accept it in the device.
In this case there is no device because it's an emulator.

The questions

  1. Is this expected?
  2. if yes, is there any way to accept the popup or connect to the emulator any other way to get around this?
  3. could we somehow create a virtual usb device and use scrcpy with --otg and connect that way? (it won't work if USB debugging isn't enabled by default)
@faprobst
Copy link

@lucasaas98 Did you ever figure this out? I am having the same issue, cannot get ADB to connect with authentication. I have copied the ADB keys and I have tried manually marking SKIP_AUTH = true

@lucasaas98
Copy link
Author

@lucasaas98 Did you ever figure this out? I am having the same issue, cannot get ADB to connect with authentication. I have copied the ADB keys and I have tried manually marking SKIP_AUTH = true

@faprobst nope, didn't even bother to try

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants