Search Issue Tracker

Fixed in 2020.1

Fixed in 2018.4, 2019.3

Votes

7

Found in

2018.4.13f1

2019.2.13f1

2019.3.0b7

2020.1.0a5

Issue ID

1203242

Regression

Yes

Building asset bundles when build path doesn't exist causes a failed assertion on "pluginAppendices.size() <= 1"

Asset Bundles

-

How to reproduce:
1. Open the attached project
2. Make sure Project/AssetBundles directory doesn't exist
3. Window > AssetBundle Browser >> Build
4. Select any Build Target that is supported
5. Press Build

Actual result: Failed assertion is thrown.
Expected result: No failed assertion is thrown.

Reproducible with: 2020.1.0a17, 2019.3.0f3, 2019.2.16f1, 2018.4.14f1.
Regression introduced in: 2020.1.0a5, 2019.3.0b7, 2019.2.13f1, 2018.4.13f1.
Not reproducible with: 2020.1.0a4, 2019.3.0b6, 2019.2.12f1, 2018.4.12f1.

Notes:
- The error appears if the asset bundle build path doesn't exist.

  1. Response avatar

    Resolution Note (fix version 2020.1):

    Fixed in 2020.1.0a19

Comments (6)

  1. Fcae81ba0049b6f6cb0a78a246ab87d4?d=mm

    mohsinmukhtar344

    Sep 05, 2020 06:01

    Whoever you are that logged the reproducibility list above, I need to offer sincere thanks. This is very amazingly.

  2. 0daafa153db0e5c25f3610185eba3519?d=mm

    HiddenJason

    Jan 25, 2020 20:41

    This is blocking us here as well. Our editor script that builds the asset bundles even explicitly creates the destination folder before calling BuildPipeline.BuildAssetBundles. We definitely need a fix for 2019.2 (which is not currently listed in the planned fixes), since 2019.3 is still only a "pre-release".

  3. 3951f94a3c7f654f27f125ea96c62d06?d=mm

    Lisan

    Jan 17, 2020 10:59

    Also description says, that "The error appears if the asset bundle build path doesn't exist.", it's not true, cause we have error even if the folder exists.

  4. 3951f94a3c7f654f27f125ea96c62d06?d=mm

    Lisan

    Jan 17, 2020 10:57

    Still not fixed in 2019.2.18!
    We forced to downgrade to 2019.2.12, whitch is disgrace.

  5. 6e9548a177e169bc3c2090c0c6c3476d?d=mm

    rickknowles

    Jan 09, 2020 16:40

    Also - this *isn't* fixed in 2019.3, so whichever misleading twit marked it fixed, next time check properly.

  6. 6e9548a177e169bc3c2090c0c6c3476d?d=mm

    rickknowles

    Jan 09, 2020 16:39

    Whoever you are that logged the reproducibility list above, I need to offer sincere thanks. The list above led me to a downgrade that I would never have even thought to try (2019.2.17 -> 2019.2.12) which worked.

    Unity need to take a long hard look at themselves if they want to be considered serious players with this kind of rubbish going on routinely. Between this and the "Blendshape Normals setting being ignored until 2019" error it's turning into a god damned minefield knowing which version to use.

    Again thank you.

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.