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
- The Motion field of the Blend Tree doesn't get set when double clicking on the Motion in the Select Motion window
- Application.systemLanguage returns "Unknown" when system language is set to Norwegian Bokmål/Nynorsk
- Project fails to load scene in WebGL due to lack of memory
- [Mobile] DownloadHander.text throws an exeption when reading a not supported exception
- Particle System's Point Light flickers while Looping is on and Emission Rate over Time is set to 0 with Bursts Count set to 1
Add comment