I’m trying to step through JUCE’s initialisation code on Android in order to see where the
AndroidComponentPeer) triggers the
createNewView method. However, I’ve noticed that as soon as the debugger steps out of C++ world via JNI back into Java via the
launchApp method, the debugger loses track. Any breakpoints I add after that point (.e.g in
Component::addToDesktop) are ignored.
I’m fine with digging into the code, adding logs and following calls manually but it would be handy to be able to debug using breakpoints across the JNI bridge. Is this is a limitation of the Android Studio debugger?