When debugging the device example for Qt 6.7.0 Beta 2 testing:

JDK 17

NDK 26

API-verison 34

Deploying to and debugging to an arm8 one plus 10T device with no C++ breakpoints set and 1 qml breakpoint set:

When the debugger connects after the app launches, the qml engine has started, but then the debugger connects and I have to start stepping through until some magic point is reached.

The qml breakpoint does trigger can be stepped.

With A C++ breakpoint set, it behaves the same, as if the breakpoint is not there.

see the attached video.

 This is with QML profiling and debugging enabled.

Disabling QML profiling and debugging, and removing the qml breakpoint: 

The c++ breakpoint triggers on qt creator 13 dev snapshot, but not qt creator 12

(I'm not sure if that was as fluke)