Update AndroidManifest.xml #404
Conversation
Adding the necessary meta-data and intent for hello_xr to actually run on devices like Quest and Pico
|
|
|
I'm a little undecided on this one: it seems like meta and pico should not be requiring these extra vendor specific metadata. I can understand requiring standard Android entries (like rumble permission) and the OpenXR specified intent filter, but these vendor specific ones feel like the opposite of what OpenXR should be doing. Will check with the wg in case you haven't already. |
| @@ -48,6 +48,14 @@ | |||
| android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" | |||
| android:exported="true" | |||
| tools:ignore="NonResizeableActivity"> | |||
| <!-- Required meta-data and inent category for Meta devices --> | |||
| <meta-data | |||
There was a problem hiding this comment.
Maybe it needs to moved into the application not activity? You can check the GitHub Action's building failure information.
There was a problem hiding this comment.
You can check https://developer.oculus.com/documentation/native/android/mobile-native-manifest/ and https://developer-global.pico-interactive.com/document/unity/quickstart-configure-settings/ for Quest and PICO tutorial.
|
An issue (number 2019) has been filed to correspond to this pull request in the internal Khronos GitLab (Khronos members only: KHR:openxr/openxr#2019 ), to facilitate working group processes. This GitHub pull request will continue to be the main site of discussion. |
Adding the necessary meta-data and intent for hello_xr to actually run on devices like Quest and Pico