All Oculus Quest developers MUST PASS the concept review prior to gaining publishing access to the Quest Store and additional resources. Submit a concept document for review as early in your Quest application development cycle as possible:

For additional information and context, please see "Submitting Your App to the Oculus Quest Store".
Welcome to the Oculus Developer Forums!

Your participation on the forum is subject to the Oculus Code of Conduct.

In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.

Process finish when hit breakpoint remote debugging Oculus Quest 2

joseangelmtjoseangelmt Posts: 2
edited October 17 in Oculus Quest Development
I'm starting to play with Android Studio and Mobile SDK and Oculus Quest 2.

Everything is working correctly but when I start remote debugging any of the SDK samples in the device, when the debugger hits a breakpoint, after two or three seconds the process finishes and the debugging session closes.

The logcat pane shows something like this: Process 26768 exited due to signal 9 (Killed)
And the Debug pane shows something like this: Process finished with exit code 22

Is there a way to avoid the process to finish/exit when debugging the application?

Thanks in advance.


  • a-rsmitha-rsmith Posts: 1
    edited October 19
    FWIW, I'm seeing this too, along with programatic asserts using __builtin_trap().

    It's made debugging..... interesting.
Sign In or Register to comment.