godot: Unable to debug Android game over USB in 3.2 beta3
Godot version: 3.2 (>=beta3 & master)
OS/device including version: Windows 10 v1903 (x64) - editor Xiaomi Redmi Note 7, Android 9 - player/device
Issue description: In latest stable (3.1.2), if I press the one click export, everything works flawlessly and my profiler/monitor/etc connect and I get remote debugging from my phone:
0 param: --remote-debug
1 param: localhost:6007
2 param: --use_depth_32
3 param: --use_immersive
Installing to device (please wait...): Xiaomi Redmi Note 7
** Device API >= 21; debugging over USB **
** DEVICE API >= 21; DEBUGGING OVER USB **
Reverse result: 0
** Debug Process Started **
Godot Engine v3.1.2.stable.official - https://godotengine.org
OpenGL ES 2.0 Renderer: Adreno (TM) 512
if I copy the project and launch it with 3.2 (both beta3 and master), or even make a new blank project and set it up for Android exporting, localhost
changes to 127.0.0.1
(unsure if this is exactly why it’s breaking) and I get an error about USB debugging, even though it was working fine on 3.1.2:
0 param: --remote-debug
1 param: 127.0.0.1:6007
2 param: --xr_mode_regular
3 param: --use_depth_32
4 param: --use_immersive
Installing to device (please wait...): Xiaomi Redmi Note 7
--- Device API < 21 or no USB connection; debugging over Wi-Fi ---
--- DEVICE API < 21 OR NO USB CONNECTION; DEBUGGING OVER WI-FI ---
no more output after that, no profiler or monitor info (everything else is fine though)
on 3.2 beta3 I can set the remote debugging IP to my local IP and the wifi debugging does work as a temporary workaround, but as USB worked in 3.1 it’d be nice to have it back
Steps to reproduce:
Test one project’s one click deploy in both 3.1.2 and 3.2, for me it doesn’t matter what the project is, 3.2 never lets me debug over usb 3.2 beta2 works as normal, the remote-debug address being localhost
still
Minimal reproduction project: N/A (works with basically any project that is exportable)
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 3
- Comments: 15 (10 by maintainers)
Just ran into this, same situation still happening as OP. And this is on 3.2 RC2, it just straight up breaks USB debugging. Edit: Win10 64 bit, Android 9 Moto G6. Everything worked on 3.1.2 Also adding my device debug info as well:
Likely a regression from #32854, CC @cooperra.