Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0a1
2019.3.5f1
Issue ID
1228192
Regression
Yes
Unity YAML Upgrading project to 2019.3 Asset Database V2 makes the project crash on startup
Reproduction steps:
1. Create a new project with 2019.2.0a14 (Asset Database V1)
2. Import Package "pref.unitypackage" (note 1)
3. Ignore errors in the console
4. Try to upgrade the project to 2019.3 (prompt to update to Asset Database V2)
Unexpected behaviour: Unity crashes!
5. Open the project in 2019.2.0a14 again
6. Delete prefab "ModelPlacement2D"
7. Upgrade the project to 2019.3 (Asset Database V2)
The project successfully launches (note 2)
Reproducible with: 2019.3.0a1, 2019.3.14f1
Not reproducible with: 2019.2.21f1, 2020.1.0b8, 2020.2.0a10
Notes:
1. The package is "ModelPlacement2D" prefab exported from the user's project
2. In users original project this corrupts all Scene and Prefab files (check image001)
3. The 2019.2 version can be anything (tested 2019.2.0a14, 2019.2.17f1, 2019.2.21f1)
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
- [Windows] The Unity import progress is not shown in the Windows taskbar
- Custom shader creation APIs are missing the AssetImportContext and thus can't handle includes correctly
- 2019.4: PackedMemorySnapshot: nativeObjects.gcHandleIndex contains -1 always
- [Hub] Project "Remove from list" option is behind notifications when selecting the most bottom project in the list
- [Android][Vulkan] Black Screen renders on devices with Adreno 640 and Mali GPU's
Resolution Note:
The root cause of the issue was commented out YAML. Unity YAML for performance concerns only support a subset of the YAML language and comments are not part of this subset. For more information on Unity YAML https://docs.unity3d.com/Manual/UnityYAML.html