Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2019.3
2019.4
2019.4.14f1
Issue ID
1292235
Regression
No
An error is thrown when selecting Image.color Animation dependencies after upgrading to Unity version with Asset database v2
How to reproduce:
1. Open the attached "SelectDependencies" project in Unity 2019.4.15f1
2. When the "Asset Database Version Upgrade" window appears select the "No" option
3. In the Project window right-click on the "WaitForServerResponseAnim" Asset and select the "Select Dependencies" option
Expected results: No errors are thrown
Actual results: The "ArgumentException: Asset path cannot be null or empty." error is thrown
Reproducible with: 2019.3.0b10, 2019.4.15f1
Could not test with: 2018.4.29f1 because the Asset Database v2 is not yet introduced, 2019.3.0b9, 2020.1.14f1, 2020.2.0b11, 2021.1.0a6 because the Asset Database v2 is used automatically without any choice to use the v1
Notes:
- The Animation has to have the "Image.color" property animated to reproduce the issue
- The issue is only reproducible on versions that have the "Asset Database Version Upgrade" window appear when opening a project that was last saved in Asset Database v1 and choosing not to upgrade to the Asset Database v2
- Choosing to use the Asset Database v2 will not make the issue appear
- Right-click on any Asset and choosing the "Reimporting all" option fixes the issue but reimporting only the animation does not
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
Add comment