Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
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
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
- Unity Version Control server textfield’s text overlaps with the dropdown triangle button in the Explore repositories window when an organization with a long name is selected
Add comment