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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2020.1):
Fixed in 2020.2.0a9
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b11