Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2019.3.14f1
2020.2
Issue ID
1253270
Regression
No
AssetBundle.Contains does not find assets when bundles are built using CompatibilityBuildPipeline.BuildAssetBundles
Reproduction steps:
1. Open the attached project ("case_1253270-ContainsBug.zip")
2. Build asset bundles (Build > AssetBundles: Standalone)
3. Check if they contain "icon.png" asset (Build > Check Bundles)
4. Inspect Console logs
Expected result: 'AssetBundle.Contains' returns true
Actual result: 'AssetBundle.Contains' returns false, even though the asset is in the bundle
Reproducible with: 2018.4.23f1, 2019.4.1f1, 2020.1.0b13, 2020.1.0a15
Reproducible with package versions: 1.5.1, 1.7.3
Couldn't test with package versions 1.8.2, 1.8.4 because of case 1252686
Note: Loading the asset using the path taken from ".GetAllAssetNames()" method succeeds, but ".Contains()" method with the same path fails.
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 when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
- Artifacts appear on GameObjects when using the WebGL Player on Silicon macOS
- Only the icon of the disabled child GameObject is faded when a parent GameObject is a Prefab
Resolution Note (fix version 2020.2):
Fixed edge case with AssetBundle.Contains API when the bundle is built with Scriptable BuildPipeline.
Fixed in 2020.2.0a20
Resolution Note (fix version 2020.1):
Fixed in 2020.1.3f1.4343
Resolution Note (fix version 2019.4):
Fixed in 2019.4.10f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.28f1