Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
Issue ID
1079571
Regression
No
[GearVR][Android][XR] Oculus plugin is not loaded when using ARM64 as target architechture
How to reproduce:
1. Open attached "OculusInitialization" project
2. Build & Run project (all the configuration is already done in the project) on Android device
Expected result - Application is initialized as XR app (using Oculus)
Actual result - Black screen is shown on launch. After getting application out of focus and refocusing on it again, you can see that application is not initialized as XR app. In logcat you can observe the error: "Oculus Plugin could not be loaded."
Reproducible with - 2019.1.0a1 (a95a274daf4f), 2018.3.0b1(7f2ac4f15f13), 2018.2.7f1(4ebd28dd9664)
Note - Does not happen with Cardboard or Daydream, VR is intialized when using these SDK's
DUT:
VLNQA00164, Samsung Galaxy S8, Mali-G71, Exynos 9 Octa 8895, Android 8.0.0
VLNQA00143, Samsung Galaxy S9+, Adreno (TM) 630, Snapdragon 845 SDM845, Android 8.0.0
VLNQA00021, Samsung Galaxy S7, Mali-T880, Exynos 8 Octa 8890, Android 7.0
VLNQA00012, Samsung Galaxy S6, Mali-T760, Exynos 7 Octa 7420, Android 7.0
VLNQA00013, Samsung Galaxy S6 Edge+, Mali-T760, Exynos 7 Octa 7420, Android 7.0
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
XR Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.