Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.2.X
Votes
3
Found in
2017.1.0b6
Issue ID
913864
Regression
No
[Build] AssetDatabase.GetImplicitAssetBundleName asserts & returns wrong result when asset is being deleted
Reproduction steps:
1. Open project attached (GetImplicitAssetBundleNameBug.zip).
2. Delete one asset from each folder (SpritesInSomeBundle, SpritesInSomeOtherBundle, SpritesNotInABunble).
Expected result: Debug message will appear and it will have correct Asset Bundle name.
Actual result: Error appears: "Assertion failed: Use IsAssetAvailable before calling AssetFromGUID", Asset Bundle name in Debug message is the same for all assets.
Notes: This problem is also triggered when duplicating existing asset.
Each folder contains assets with different Asset Bundle name. In 5.6 and 2017.2 Asset Bundle name is returned as empty.
In 5.6 and 2017.2 there is an additional error: Assertion failed: AssetBundle index doesn't exist in the asset database.
Reproduced on: 5.6.0f3, 5.6.1p1, 2017.1.0b6, 2017.2.0a1.
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
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a8
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.2f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.19f1