We are trying to debug a model specific bug on a game running C++ code through NDK with Visual Studio 2022 and Android Game Development extension.
We have a model specific rendering bug that we can’t reproduce anywhere outside Galaxy S24 FE Vulkan rendering. However, on the specific model we can’t seem to attach break points on the code as usual, which makes it very difficult to reason the data sent to rendering API.
The phone has developer mode and USB debugging enabled as usual and we can launch debug build through USB from Visual Studio. However, whenever we run the debug version through USB debugging, any set breakpoints turn inactive and declare “The breakpoint will not currently be hit. Unable to find a valid address to bind breakpoint.”
There are no instantly obvious messages concerning debugger in program output or logcat (I can probably post some logs if necessary) and the same debugging setup works on practically all other phones - older or newer - available for testing for us. The phone has the auto-blocker feature disabled. We’ve also updated the Samsung USB drivers.
We’ve tried building the debug version with NDK versions 27.2.12479018 and 23.2.8568313 and are using the most recent AGDE version 24.1.99.
The phone is running Android 14, One UI 6.1 and March 1 2025 security patch.
Just wanted to share that I am also experiencing an issue attaching a debugger to my Galaxy S24. I can breakpoint the Java code used in my application, but none of my breakpoints work when trying to do it in my C++ code. Either they are skipped entirely, or Android Studio changes the red dot to a white crossed circle indicating after attempting to catch it. Hovering over said circle displays a message that says there was no code associated with the line I selected.
The debugger works just fine when I try to do it on the simulator, so I suspect the problem is with the Samsung device.
I have an S23 Ultra that has worked fine until today when I updated the device. I’m not sure which update caused this problem but the phone is now on Android 15, One UI version 7.0. Now I’m in the same boat, I can’t set breakpoints. I can debug with other devices fine but this one no longer works. I’m using Visual Studio and AGDE version 24.1.99 (the latest), debugging NDK(r26d)/C++ code.
Is there any update on this? veli-matti.karhula, did submit a developer support request?
Our immediate graphical issue got fixed by the system update with OneUI 7.0 and we had to shift focus to putting out other fires.
I’ve created a ticked and received a detailed response though. Apparently some of the debugger issues have been fixed by the recent system updates for the phone, but no luck for the particular one I have. I’ve now sent them some system logs, we’ll see if something comes out of it.
The slow progress is completely on my side at this point. So many fires to put out currently that this one ended up getting sidelined for a while unfortunately.
Just to add some additional information, my team has also seen the issue. We see it with Samsung S23, S24, and S25 devices on Android 15. If the device is on Android 14 or below, we do not see the issue.
Interestingly enough, S21 devices on Android 15 do not have the issue. We have not tested an S22 yet.
We are using Visual Studio 2022 17.12 LTSC with AGDE version 24.1.99 and NDK 26.3.