Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
3.2.2
Issue ID
OXPB-89
Regression
Yes
[OculusXR][Quest] Application crashes on start up upon updating to OculusXR 3.2.1
Steps to reproduce:
1. Open the attached user's project "Into-Dementia-VR2.zip"
2. Switch to the Android Platform
3. In "Project Settings > Wwise Editor" under "Asset Management", uncheck ‘Copy Soundbanks …' and ‘Generate Soundbanks …’. Also, uncheck ‘Connect to Wwise’.
4. Build to Quest 2
5. Open Android Logcat and observe the crash
Expected results: The application does not crash
Actual results: Application crashes on start-up upon updating to OculusXR 3.2.1
Reproducible on: OculusXR 3.2.1 - 3.2.2 (2021.3.16f1, 2022.2.2f1, 2023.1.0a24)
Not reproducible on: OculusXR 3.0.2 (2021.3.12f1, 2022.2.0b12, 2023.1.0a16)
Could not test on 2020.3.43f1 due to project errors when downgrading
Notes:
-If step 3 is not performed, the build will fail
-Issue does not reproduce with OpenXR plugin
-This issue can be resolved by updating the OVRPlugin.dll integrated in Oculus Integration to the latest version
-Android logcat is attached named "Quest2logcat.txt"
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
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
- Visual glitches when using Handles API
- The RGBA color values are inconsistent when comparing two identical colors set in the Inspector
Resolution Note:
This appears to be an incompatibility between an older OVRPlugin version in the Oculus Integration asset and a newer Oculus XR Plugin with a newer OVRPlugin.
The forced upgrade of the Oculus XR Plugin package when updating Unity versions is just the nature of how verified packages work when updating Unity versions. What seems to be happening is that the Oculus Integration Asset has an older version of the OVRPlugin which isn't compatible with the one the updated package was built against.
The general solution here is that the Oculus Integration asset needs to be updated when updating to newer versions of Unity. This isn't always the case, and we try to maintain backwards compatibility as much as possible, but sometimes there are breaking changes with 3rd party assets like this.
Another option when installing the Oculus Integration Asset is to not select the option to update to the OVRPlugin in the integration asset. But this could result in compatibility issues the other way around.
If updating the Oculus Integration Asset doesn't resolve this issue, please reopen the issue.