Search Issue Tracker

Fixed in 2018.1.X

Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X



Found in


Issue ID




Loading an asset that has an Animator component from an Asset Bundle with LoadAsync throws "Assertion failed" error

Asset Bundles


The project provided uses "Asset Bundle Browser" tool but it has anything to do with the bug

To reproduce:
1) Open the attached project "943438repro"
2) From the menu open Windows -> Asset Bundle Browser
3) Press "Build" to build the Asset Bundle
4) Open "AssetBundleTest.unity" scene
5) Enter play mode
6) On the GUI in the top right corner press "Load Bundle (Async)"
Result: "Assertion failed: Assertion failed on expression: 'Thread::CurrentThreadIsMainThread()" Error is thrown

Note: this can be reproduced without the "Asset Bundle Browser" tool
When using the "Asset Bundle Browser" tool and the script for loading the asset in the project some minor tweaking might be required depending on the platform it is being tested on

Reproducible on both Mac and Windows

Reproduced on: 2017.3.0a5, 2017.2.0b8
Regression introduced with: 2017.2.0b6
Not reproducible on: 2017.2.0b5 and earlier


Comments (22)

  1. unity_qC031LQVnx79qA

    Aug 06, 2020 00:16

  2. unity_qC031LQVnx79qA

    Aug 06, 2020 00:15

  3. unity_qC031LQVnx79qA

    Aug 06, 2020 00:15

  4. stevemrjones

    Jan 17, 2018 20:14

    Having the same issue on 2017.2.0f3

  5. pointer0001

    Dec 14, 2017 00:01

    Having the same on 2017.2.0f3 64bits

  6. diekeure

    Dec 07, 2017 10:16

    Would it be possible to merge the fix into 2017.1 ? I'm still seeing this issue in 2017.1.2p3. Thanks

  7. TheProgrammer

    Nov 07, 2017 13:08

    Its fixed in version 2017.3.0b8.
    "Animation: Fixed Asserts when loading AssetBundle with AnimationClip asynchronously (943438)"

  8. diekeure

    Nov 07, 2017 08:20

    Any idea in what future release this issue will be fixed?

  9. VARtechLLC

    Nov 04, 2017 03:30

    Why is this marked as resolved? This is still an issue in 2017.2...

  10. bluescrn

    Oct 31, 2017 10:42

    Seeing a lot of this error when using bundles in the editor with 2017.0.1p4 or 2017.1.1.f1 (haven't tried anything newer yet)

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.