Search Issue Tracker

Fixed in 2020.2

Fixed in 2018.4, 2019.4, 2020.1

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

Asset Bundles

-

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.

  1. Response avatar

    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

  2. Response avatar

    Resolution Note (fix version 2020.1):

    Fixed in 2020.1.3f1.4343

  3. Response avatar

    Resolution Note (fix version 2019.4):

    Fixed in 2019.4.10f1

  4. Response avatar

    Resolution Note (fix version 2018.4):

    Fixed in 2018.4.28f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.