Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0b12
2019.3.0f3
2020.1.0a14
Issue ID
1209240
Regression
Yes
Crash when importing Elongata package from the Asset Store
Steps to reproduce:
1. Create a new project
2. Assets -> Import Package -> Custom Package
3. Import the .unitypackage attached by the user (Elongata.unitypackage)
Reproducible with: 2019.3.0b12, 2019.3.0f5, 2020.1.0a14, 2020.1.0a18
Not reproducible with: 2017.4.36f1, 2018.4.15f1, 2019.2.17f1, 2019.3.0b11, 2020.1.0a13
Notes:
- The crash doesn't reproduce a stacktrace
- Crashes when "Preparing package" window is showing "Collecting content"
Workaround:
Import the package in one of the versions where the crash is not reproducible, create a new package with the same contents and import this package into the version needed
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
- Red spots appear when Blending Lighting Scenarios using Adaptive Probe Volumes
- [Windows] About Unity Window needs to be opened twice to adapt to resolution
- NullReferenceException and temporary graph corruption after entering playmode if output node connection was changed
- Sprite Renderer with Animation does not reflect Sprite changes in the Scene when switching Mask Interaction
- Error "NullReferenceException: Object reference not set to an instance of an object" is present when loading 3D text mesh in Player from an asset bundle that is built with an older Editor version
Resolution Note (fix version 2020.1):
Fixed in 2020.2.0a9
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b11