Search Issue Tracker
Won't Fix
Votes
5
Found in
2018.3.0a6
2018.3.3f1
2019.1.0a1
2019.2.0a1
Issue ID
1122903
Regression
No
Errors when importing prefab from Unity Package file
Reproduction steps:
1. Open the project from "PGF1Grading.zip"
2. Import assets from Unity Package from a file "CivitareseFrank_Week3Project"
Expected: Unity Package imports without any issues
Actual: Four errors are logged in the Console window
Reproduces on: 2018.3.8f1, 2019.1.0b6, 2019.2.0a7
Note:
- Different errors are thrown on 2017.4.20f1 and pre-2018.3.0a6 as well, but it is likely due to Unity Package containing prefabs packed in Prefab Editor
- Error Log:
AssetImporter is referencing an asset from the previous import. This should not happen.
AssetImporter is referencing an asset from the previous import. This should not happen.
Assertion failed on expression: '!GetPersistentManager().IsStreamLoaded(metaDataPath)'
Asset import did not unload metadata path. This will leak memory. File a bug with repro steps please. (Assets/CivitareseFrank_Week3Project/Prefabs/LayerGray.prefab)
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note:
The Prefab from the repro project: 'LayerGray.prefab' is corrupt: It has a disconnected Prefab variant root and a corresponding asset object that has the same GUID as the Prefab meta file's GUID. This can only happen if the files was edited outside Unity.