Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.18f1
Issue ID
UUM-28067
Regression
No
Error while downloading Asset Bundle when in WebGL Player [Add error handling when loading unsupported AssetBundle formats]
How to reproduce:
1. Open the attached project “IN-31229”
2. Open Build Settings, select the WebGL Platform, and click Build And Run
3. In the browser, press F12 to open the Console
4. Click Download in the build
Expected result: There are no errors in the browser Console
Actual result: After a few seconds there is an error in the browser Console
Reproducible with: 2021.3.18f1, 2022.2.0a7
Not reproducible with: 2020.3.45f1, 2022.2.5f1, 2023.1.0b4, 2023.2.0a2
Fixed in: 2022.2.0a8
Reproducible on: Windows 11 Pro
Full error:
hh.framework.js:3 Error while downloading Asset Bundle: Failed to decompress data for the AssetBundle 'https://game-data.gameindy.com/cmm/alpha/WebGL/bgm_assets_all_90269f6a23198aa61636191af5eff721.bundle'.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Firstly; thanks for taking the time to report this issue - we really appreciate it. It's sparked a rather interesting discussion on the build team - so thank you for that.
Unfortunately, we've marked it as a "won't fix". We believe this issue is caused by a bundle generated from a newer version of Unity being used with an older Unity runtime. We appreciate we could improve the UX around this, but it's unfortunately not something we're able to do for any of the current Unity LTSs given that they've also been bumped to support the latest AssetBundle format.
We've created a ticket to be more mindful of this in any future AssetBundle updates to ensure that it doesn't happen again.
Thanks again for your time.
Resolution Note (2021.3.X):
Firstly; thanks for taking the time to report this issue - we really appreciate it. It's sparked a rather interesting discussion on the build team - so thank you for that.
Unfortunately, we've marked it as a "won't fix". We believe this issue is caused by a bundle generated from a newer version of Unity being used with an older Unity runtime. We appreciate we could improve the UX around this, but it's unfortunately not something we're able to do for any of the current Unity LTSs given that they've also been bumped to support the latest AssetBundle format.
We've created a ticket to be more mindful of this in any future AssetBundle updates to ensure that it doesn't happen again.
Thanks again for your time.