Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.5f1
Issue ID
1127670
Regression
No
XRSettings.enabled and XRSettings.supportedDevices return incorrect results when printing with InitializeOnLoad attribute
To reproduce:
1. Open QA attached project "XRSettingsCase.zip" on Unity with supported Android and UWP platform
2. Observe the console (or enter Play mode to print again)
Expected: XRSettings.enabled is printed as true, XRSettings.supportedDevices prints Standalone, Android and UWP XR settings
Actual: XRSettings.enabled is printed as false, XRSettings.supportedDevices prints Standalone and Android XR settings
Reproduced in: 2017.4.21f1, 2018.3.7f1, 2019.1.0b4, 2019.2.0a6
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note (2019.2.X):
We are no longer updating 2019.2. If this is still an issue for you in 2019.3 or greater, please re-submit your bug.