From 0ee6795a05735f6f52ea220ac24534150649854c Mon Sep 17 00:00:00 2001 From: Hugo Locurcio Date: Wed, 15 Jun 2022 16:49:01 +0200 Subject: [PATCH] Add Android troubleshooting instructions in One-click deploy --- tutorials/export/one-click_deploy.rst | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/tutorials/export/one-click_deploy.rst b/tutorials/export/one-click_deploy.rst index 7cbe2a791..07e64df51 100644 --- a/tutorials/export/one-click_deploy.rst +++ b/tutorials/export/one-click_deploy.rst @@ -58,3 +58,25 @@ Using one-click deploy - Click the button to export to the desired platform in one click. .. image:: img/oneclick.png + +Troubleshooting +--------------- + +Android +^^^^^^^ + +If you can't see the device in the list of devices when running the +``adb devices`` command in a terminal, it will not be visible by Godot either. +To resolve this: + +- Check if USB debugging is enabled *and authorized on the device*. + Try unlocking your device and accepting the authorization prompt if you see any. + If you can't see this prompt, running ``adb devices`` on your PC should make + the authorization prompt appear on the device. +- Try `revoking the debugging authorization `__ + in the device's developer settings, then follow the steps again. +- Try using USB debugging instead of wireless debugging or vice versa. + Sometimes, one of those can work better than the other. +- On Linux, you may be missing the required + `udev rules `__ + for your device to be recognized.