Search Issue Tracker
Active
Under Consideration for 1.14.X
Votes
1
Found in [Package]
1.11.0
Issue ID
OXRB-358
Regression
Yes
[Android]The Player displays a black screen when the OpenXR is used as the Plug-In Provider (Part 1)
Reproduction steps:
1. Open the attached "ASDQWE" project
2. Build and run the Player (File > Build And Run)
3. Observe the Player
Expected result: The Player displays the default Scene
Actual result: The Player displays a black screen
Reproducible with: 1.11.0 (2021.3.39f1, 2022.3.32f1, 6000.0.6f1)
Not reproducible with: 1.10.0, 1.11.0-exp.1 (2022.3.32f1)
Reproducible environment: MacOS 14.5 Sonoma (Intel), Windows 11 (user's)
Not reproducible environment: No other environment tested
Reproducible on:
VLNQA00175, Samsung Galaxy Note9 (SM-N960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00519, Google Pixel 4 (Pixel 4), Android 12, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00146, Htc 10 (HTC 10), Android 8.0.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00372, Samsung SM-G991U (SM-G991U), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Not reproducible on:
MacOS Buildtime (Simulator, Game View)
Could not test on:
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 6.0, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
(The device does not have the minimum required Android OS version)
Notes:
- The Unity logo Splash Screen does not appear when the issue occurs
- Reproducible with both Vulkan and OpenGLES3 Graphics APIs
- Reproducible with a blank project
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
mikeskydev
Dec 24, 2024 22:38
To be clearer than the original ticket, this happens on Android devices that *don’t* support OpenXR. It is expected to not attempt to initialise OpenXR, but continue execution as normal where other XR providers may or may not be successful at loading. Worked prior to 1.12, so it’s a regression and critical functionality for our app.
mikeskydev
Nov 13, 2024 12:44
Please fix, this is blocking us from deploying our universal apk.