Search Issue Tracker
Fixed in 2020.1
Fixed in 2018.4, 2019.2, 2019.3
Votes
0
Found in
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a4
Issue ID
1164341
Regression
Yes
Non-prefab Assets with .prefab extension are incorrectly handled by the Prefab Importer
How to reproduce:
1. Open the submitted project (MeshPrefabImport_193)
2. Select the 'customer_model' prefab in the Project window
Expected result: the asset should not be treated like a prefab since it does not contain a prefab object
Actual result: the asset is treated like a prefab and results in errors being printed in the Console window
Reproducible with: 2018.3.0a6, 2018.4.3f1, 2019
Not reproducible with: 2017.4.29f1, 2018.3.0a5
Notes:
Starting with 2019.1.0f2, 2019.2.0a12 and 2019.3.0a1, after selecting such an asset, InvalidCastException errors are continuously printed in the Console window
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [XR] Vulkan graphics device lacks support for additional graphics queue when using Oculus XR provider
- [TransformTool] Shift rotate always reset the rotation value when used
- Crash in wrapper managed-to-native) System.Diagnostics.StackFrame:get_frame_info (int,bo when importing an mp4 5760 x 2880 video
- Bug reporter on MacOS doesn't correctly support dark mode
- [Vulkan][Android] Video Player in 2018.4 using Vulkan does not play Videos
Add comment