godotengine / godotengine/godot
Debug session over wifi have not started with android device
- Dominant language
- C++
- Stars
- 117k
- Forks
- 26.8k
- PR merge metrics
- PR metrics pending
Description
### Tested versions
- Reproduces in godot: 4.2 stable .net.
- Phone: Pixel 4a, android 13
- Tablet: Redmi Pad SE, android 13
### System information
Windows 10, Godot 4.2 stable .net
### Issue description
Debug session over wifi have not started with android device. Application builds, deploys and runs on android device but programm execution is not paused on break points. GD.Print() messages don't appear in debug output window.
### Steps to reproduce
1) create godot project
2) set node 2d scene
3) add script for node from step 2
4) in process method in script from strp 3 add print function with some text
5) Install export template
6) Install android build template
7) Set checkbox: deploy with Remote debug
8) Configure android SDK and debug keys in Editor->Editor settings->Export->Android
9) Set checkbox Import ETC2 ASTC in project settings
10) Add export presets for android
11) connect phone/tablet with adb to computer
12) Press remote debug button-> your device name
Expected result:
- application should be uploaded to device and started
- debug session should start in godot editor
Actual result
- application is uploaded to device and started
- debug session DOES NOT start in godot editor
### Minimal reproduction project (MRP)
[GodotEmpty.zip](https://github.com/godotengine/godot/files/14156805/GodotEmpty.zip)
Contributor guide
Research direction
Start by importing the attached GodotEmpty.zip project and reproducing the Android remote-debug steps with the listed Windows 10 and Android 13 setup. Verify whether deployment succeeds while breakpoints and GD.Print() output remain unavailable. Done means the application starts on the device and a debug session appears in the Godot editor with breakpoint and output support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- devtools, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100