Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0a1
Issue ID
959500
Regression
No
Assertion Fail when certain Assets fail to import
Seeing the error message: 'GetObject failed to find Object for Library Representation' when audio or aideo assets fail to import.
Tracking down the issue seems to lead to IsVisibleInLibraryRepresentation in AssetDatabaseV1.cpp not being able to handle an error with no asset attached.
Reproduction steps:
1. Download attached movie + create a new project
2. Import the movie and enable transcoding
3. Error should appear in console, if not disable + enable transcoding again.
This reproduces on windows only, as the particular movie clip does not transcode on windows.
So to wrap up what seems to be happening here: Transcoding fails on importing the video, which is a valid failure. A secondary failure then emerges which is that the AssetDatabase can't cope with an error that has no asset attached (because no asset could be generated).
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (2019.1.X):
Hi there,
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.
Unity QA Team