Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
0
Found in
2019.1.0a7
2019.3
Issue ID
1127443
Regression
Yes
GVR package removal logic doesn't respect dependencies other than Daydream; causes errors in Google Cardboard scenarios
I found that the GVR package, used by both Google Cardboard and Daydream, is always removed from the manifest.json if Daydream is disabled/removed from the XR SDK list. This causes problems when Cardboard is still in the list as it still depends on GVR. Also, I'm not confident that the GVR package is consistently added if you add Cardboard in, which is what I would expect.
Repro:
1. Start with Cardboard and Daydream sdks in list. Verify GVR packages is in manifest.json file
2. Remove Daydream
Expected: GVR package is still in manifest.json for Cardboard to use
Actual: GVR is removed, causing issues running Cardboard
Secondary repro:
1. Start with Cardboard and None sdks in the list
2. manually remove the gvr package from the manifest.json file, save
3. Go back to Editor and remove Cardboard from sdk list, leaving only None.
4. Add Cardboard back into sdk list
Expected: GVR package is added into manifest.json file
Actual: GVR package is not consistently added to manifest
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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Resolution Note (fix version 2019.2):
Fix verified in 2019.3.0a3 (91c086393aab)
Resolution Note (fix version 2019.1):
Fix verified in 2019.1.5f1 (6f1140cf2297)