Search Issue Tracker
Won't Fix
Votes
2
Found in
2020.3.42f1
2021.3.14f1
2022.1.24f1
2022.2.0f1
2023.1.0a21
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-20745
Regression
No
"Initialize XR on Startup" has no effect when disabled
Reproduction steps:
1. Create a new VR Template project and open it
2. Go to: “Edit > Project Settings > XR Plug-in Management > Android”
3. Disable the “Initialize XR on Startup” checkbox
4. Enable the Oculus Plug-in Provider
5. Build and Run on a handheld Android device and on Oculus 2
6. Observe the result
7. Enable the “Initialize XR on Startup” checkbox
8. Repeat steps 5 & 6, and compare the results
Expected result: When “Initialize XR on Startup” is disabled, the application launches successfully on the handheld device but not on Oculus.
Actual result: When “Initialize XR on Startup” is disabled, the handheld device shuts down the application, and on Oculus 2, the application loads forever, but doesn’t actually close or show the Unity logo.
Reproducible with: 2020.3.42f1, 2021.3.14f1, 2022.1.24f1, 2022.2.0f1, 2023.1.0a21
Reproducible on:
VLNQA00263 - Google Pixel 3 (Pixel 3), CPU: Snapdragon 845, GPU: Adreno 630, OS: 12.0.0
Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Will not fix.