-
Notifications
You must be signed in to change notification settings - Fork 119
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
Installer does not try to detect again if the adb is not authorized yet #983
Comments
Hmm - I have seen somebody commented this popup before, but I have never seen it. Neither at the device (Nexus 5), nor at the PC (Debian) screen. I started ubports-installer from the command line, and this is the ouput: ~ (11:33:00) $ ubports-installer I have tried to kill the adb server:: Afterwards I started the adb server (adb -start-server) and tried ubports-installer again, but with the same result. |
… and handle some unlock errors (part of #1479)
… and handle some unlock errors (part of #1479)
If the device is in developer mode, but connected to the PC for the first time, there will be a popup on the device to authorize the adb connection. In the mean time, adb will print an error that passes silently as of now. This error should be handled in the module, and a modal should be shown in the installer prompting the user to accept the action on the device.
The text was updated successfully, but these errors were encountered: