Search Issue Tracker
Fixed
Fixed in 1.10.0
Votes
0
Found in [Package]
1.10.0
Issue ID
OXRB-300
Regression
No
[Quest] Player crashes at launch when built with OpenXR and Meta store-compatible AndroidManifest.xml
Reproduction steps:
1. Open the attached project "ReproProj"
2. Switch platform to Android (File > Build Settings > Android > Switch Platform)
3. Open the “/Assets/Samples/Meta XR Core SDK/60.0.0/Sample Scenes/MRC.unity” Scene
4. Build and Run on Quest 2
Expected result: The Player launches successfully and continues to run
Actual result: Player crashes at launch
Reproducible with: 1.9.1 (2023.3.0b5), 1.10.0 (2021.3.35f1, 2022.3.19f1, 2023.2.7f1, 2023.3.0b5)
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- The workaround is to delete AndroidManifest.xml in the “\Assets\Plugins\Android” folder
- Does not reproduce with Oculus XR
- Reproduces with Vulkan and OpenGLES3
-
lianne13
Feb 21, 2024 17:10
Looked into the issue and seems this is not a bug on our end. The crashing lies in the AndriodManifest file at line 6 where is says
<activity android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen"If changed to
<activity android:theme="@style/Theme.AppCompat.DayNight.NoActionBar"
the app will build and run correctly. Seems the issue was the user was using the wrong Theme library which cause it to fail to launch with the original manifest file.
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
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
- TextMeshPro memory leak occurs when reloading the scene using Addressables
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
Resolution Note (fix version 1.10.0):
Looked into the issue and seems this is not a bug on our end. The crashing lies in the AndriodManifest file at line 6 where is says
<activity android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen"
If changed to
<activity android:theme="@style/Theme.AppCompat.DayNight.NoActionBar"
the app will build and run correctly. Seems the issue was the user was using the wrong Theme library which cause it to fail to launch with the original manifest file.