Search Issue Tracker
Fixed in 2023.1.0b14
Fixed in 2023.1.X, 2023.2.X, 2023.2.0a12
Votes
0
Found in
2023.1.0a8
2023.1.0a13
2023.2.0a1
Issue ID
UUM-15877
Regression
Yes
AssetDatabase.StartAssetEditing throws warnings when called from script
Reproduction steps:
1. Open the user’s attached project
2. In the Editor window menu, select BugRepro > DoestWork
Expected result: No Console warnings
Actual result: Warning “Empty track found while loading timeline. It will be removed.” in the console
Reproducible with: 2023.1.0a8, 2023.1.0a13
Not reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.19f1, 2022.2.0b10, 2023.1.0a6
Reproducible on: Windows 10
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
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
- [HDRP] Volumetric cloud shadows disappear when there is no directional light shadows
- “Selector” column names in the Search window are lowercase when added
- Install List Project Counter Panel can be right clicked through and Install Context Menu can be opened disabling Project Counter Panel's buttons
- [MacOS] Scene is marked/flickering as dirty (with asterisk) when dragging a Material on a GameObject in Scene view
Resolution Note (fix version 2023.2):
All assets that are created in between start- and stop-asset editing are not fully imported before the call to StopAssetEditing.
This is by design.
If certain asset database API's are called before the call to StopAssetEditing and with assets that are not yet fully imported, you will experience unexpected behavior.
An update to the documentation for StartAssetEditing and StopAssetEditing has been submitted as a response to this bug.
Resolution Note (fix version 2023.1):
All assets that are created in between start- and stop-asset editing are not fully imported before the call to StopAssetEditing.
This is by design.
If certain asset database API's are called before the call to StopAssetEditing and with assets that are not yet fully imported, you will experience unexpected behavior.
An update to the documentation for StartAssetEditing and StopAssetEditing has been submitted as a response to this bug.