Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0a4
2018.2.0a8
Issue ID
1024903
Regression
Yes
[XR] Editor crashes on removing vuforia resource files
Editor crashes on removing vuforia resource files after disabling "Vuforia Augmented Reality Supported" in XR settings
Steps to Repro:
1. Create a new project.
2. Edit > Project Settings > player settings > Player.
3. Enable "Vuforia Augmented Reality" checkbox from XR settings.
4. Disable "Vuforia Augmented Reality" checkbox.
5. Select "Remove Files" on "Disabling Vuforia" pop-up.
Observe the crash
Reproducible on:
2018.2.0a8, 2018.2.0a6, 2018.2.0a4.
Working fine on:
2018.1.0f1, 2018.1.0b13, 2017.3.0f3, 2017.2.0f3.
Environment:
Occurring on Windows 10, Windows 7, Mac 10.13, Mac 10.12.
Note:
1. On 2018.2.0a3 , 2018.2.a2 & 2018.2.0a1 following Exception is thrown continuously
"ArgumentException: There must be 2, 3 or 4 components in the version string" and editor doesn't crash.
2. On 2018.1.0b13, 2018.1.0f1, 2017.3.0f3 & 2017.2.0f3 following Exception is thrown
"MissingReferenceException: The object of type 'VuforiaConfiguration' has been destroyed but you are still trying to access it", and editor doesn't crash.
3. Sometimes an editor doesn't crash on disabling Vuforia once, crashes after disabling twice or thrice.
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Resolution Note (2018.3.X):
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.