Search Issue Tracker
Active
Votes
0
Found in
1.16.1
Issue ID
UUM-131300
Regression
No
Android Player for Meta Quest launches as a 2D application when using OpenXR and having "Custom Main Manifest" option enabled
Reproduction steps:
1. Open the attached project “ReproProject“
2. Switch to the Android platform in Build Profiles (File → Build Profiles → Select Android, press “Switch Profile”)
3. Build the Player
4. Launch the Player on the device
5. Observe the result
Actual result: The Player launches as a 2D application on the device
Expected result: The Player launches in VR mode on the device
Reproducible in: 1.11.0 (6000.3.3f1. 6000.5.0a4), 1.16.1 (6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Reproducible on devices:
- Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740
- Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650
Notes:
- Does not reproduce with Oculus XR
- Reproduces only with “Custom Main Manifest“ option enabled (located at Edit → Project Settings → Player → Publishing Settings, option “Custom Main Manifest“)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment