Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2019.1.X
Votes
0
Found in
2019.1.0b3
2019.2.0a1
Issue ID
1127555
Regression
No
Unity crashes in "Scripting::ScriptingWrapperFor" when trying to import the MagicLeap unitypackage into the project
Steps to reproduce:
1. Download the attached files(oc link)
- Also, download and install Magic Leap SDK if not done prior
2. Create a new project with an Editor that has Lumin installed
3. Copy + Paste the Magic Leap XR Package into your projects 'Packages' folder, let Unity recompile
4. Import XR Legacy Input Helpers from the Package Manager
5. Switch Platform to Lumin
6. Import the MagicLeap.unitypackage
Expected results: Magic Leap package imported successfully without any Editor crashes, warnings and errors.
Actual results:Editor crashes upon importing the Magic Leap package
Reproduced on 2019.1.0b3, 2019.2.0a6
Notes:
- Does not always crash on the first time doing it, can take 3-6 times
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Wrong documentation page is displayed for the "Scene Template Pipeline" help icon
- Missing Device Simulator API
- Shadow gets cut off when in Play Mode and using shader "Shader Graph/Rotation Shader" for material
- Unable to get textureOverrideSettings from BuildPipeline.GetBuildTargetName when trying to pass in the platform string
- Getting the current process name returns Null when building with IL2CPP
Add comment