Android Native Client App Immediately Crashing on Meta Quest 3

Gaming and Visualization Technologies XR – VR/AR/MR CloudXR (VR and AR Streaming)
1

Dear Forum,

I am currently trying to deploy the native Android client sample, shipped in with the CloudXR SDK 4.0, on a Meta Quest 3 device. Every now and then of course I get build errors at different attempts, which I fix, but no matter what I do I can not stop the deployed apk from immediately crashing. On the first run after installation, the device asks the user for permissions that the apk requires, which is a positive sign. However, immediately after it crashes. In subsequent runs, I get the black screen with the 3 loading dots, however in just a couple seconds I am back to the Meta Quest menu. I have built the apk numerous times on 2 different computers, and deployed every iteration to the device, but no matter what I do, the result is the same. Experimental features are also off on the device.

Any help or guidance would be greatly appreciated. Thank you in advance.

Debugging from within the Android Studio also yields:
Connected to the target VM, address: ‘localhost:59989’, transport: ‘socket’
Disconnected from the target VM, address: ‘localhost:59989’, transport: ‘socket’

While this is happening, the Quest device displays “waiting for the debugger to attach”, and as soon as the message box disappears the “Disconnected […]” message is displayed on the Android Studio debug console.

1 Like
2

I’d need to see the CloudXR Client Log from the device from failing runs, and/or logcat captured from prior to launch to after termination.

Are you following the instructions in these two sections?

https://docs.nvidia.com/cloudxr-sdk/usr_guide/cxr_ovr_client.html#running-the-oculus-vr-client
https://docs.nvidia.com/cloudxr-sdk/prog_guide/misc_features.html#how-to-launch-on-android

1 Like