I am having consistent issues deploying to the Meta Quest 2 headset. I’m utilizing openXR and XR Interactions Toolkit with this application. While the application deploys and runs successfully on the HTC Vive Focus 3 headset and on my PC, when deployed to the Meta Quest 2 the application will crash before even getting to the unity splash screen. This happens with a blank project as well that only has OpenXR and the XRIT added and gives the same crash trace. Using ADB Logcat I get the following crash error, however I cannot find anything related to this on the forums of in the documentation. I am developing in windows using Unity 2021.3.28f1.
When i accidentally left the viveXR runtime checked and built to the quest the application does load in a 2D phone/tablet mode, so it appears its an issue with the oculus support itself.
Has anyone else encountered this?
09-06 07:50:21.664 3884 3884 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-06 07:50:21.664 3884 3884 F DEBUG : Revision: '0'
09-06 07:50:21.664 3884 3884 F DEBUG : ABI: 'arm64'
09-06 07:50:21.665 3884 3884 F DEBUG : Timestamp: 2023-09-06 07:50:21-0500
09-06 07:50:21.665 3884 3884 F DEBUG : pid: 3808, tid: 3836, name: UnityMain >>> com.XXXX.XXXXXXX <<<
09-06 07:50:21.665 3884 3884 F DEBUG : uid: 10093
09-06 07:50:21.665 3884 3884 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
09-06 07:50:21.665 3884 3884 F DEBUG :[B] [/B]Abort message: 'Unknown device to support: cambria'
09-06 07:50:21.665 3884 3884 F DEBUG : x0 0000000000000000 x1 0000000000000efc x2 0000000000000006 x3 000000758bc3f030
09-06 07:50:21.665 3884 3884 F DEBUG : x4 ff736d64686b4264 x5 ff736d64686b4264 x6 ff736d64686b4264 x7 7f7f7f7f7f7f7f7f
09-06 07:50:21.665 3884 3884 F DEBUG : x8 00000000000000f0 x9 fb715e2fba8b0a9b x10 0000000000000001 x11 0000000000000000
09-06 07:50:21.665 3884 3884 F DEBUG : x12 fffffff0fffffbdf x13 0000000000000023 x14 0000000000000004 x15 ffffffffffffffff
09-06 07:50:21.665 3884 3884 F DEBUG : x16 00000076781b03f8 x17 00000076781904c0 x18 000000754118cb88 x19 0000000000000ee0
09-06 07:50:21.665 3884 3884 F DEBUG : x20 0000000000000efc x21 00000000ffffffff x22 000000758bc3f899 x23 000000758bc42020
09-06 07:50:21.665 3884 3884 F DEBUG : x24 000000758bc3f778 x25 0000007479cecece x26 000000758bc3f899 x27 000000758bc3f888
09-06 07:50:21.665 3884 3884 F DEBUG : x28 0000007479e9a000 x29 000000758bc3f0b0
09-06 07:50:21.665 3884 3884 F DEBUG : sp 000000758bc3f010 lr 000000767814318c pc 00000076781431b8
09-06 07:50:21.666 3884 3884 F DEBUG :
09-06 07:50:21.666 3884 3884 F DEBUG : backtrace:
09-06 07:50:21.666 3884 3884 F DEBUG : #00 pc 00000000000811b8 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: d103c38b4b0eaa366a982b6fbf424e5e)
09-06 07:50:21.666 3884 3884 F DEBUG : #01 pc 0000000000008d58 /system/lib64/liblog.so (__android_log_buf_vassert(int, char const*, char const*, char const*, std::__va_list)+260) (BuildId: 9589be14c0e9903846d58da9465dad70)
09-06 07:50:22.261 1040 3721 I ActivityManager: Process com.XXXXX.XXXXXXXXXXXXXXX (pid 3808) has died: fore TOP
09-06 07:50:22.293 1040 1077 W ActivityManager: setHasOverlayUi called on unknown pid: 3808
Hey - if it helps I’m seeing a similar issue but only on a headset that is managed. I can install it with no issues on an unmanaged headset via sideload APK… any work around?
I think I figured out the culprit. You need to make sure that you’re not targeting the Oculus Pro in both setting menus, I assumed that the Oculus settings would have just transferred over to the OpenXR settings… nope! You’d think if you unchecked it in one area it would automatically uncheck it in another… it does not
When I did this fix it booted up and I didn’t see the error anymore.
