Search Issue Tracker
Fixed in 2021.3.35f1
Fixed in 2021.3.X, 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0a17
Votes
0
Found in
2021.3.15f1
2022.3.15f1
2023.3.0a17
Issue ID
UUM-21896
Regression
Yes
Parse error "The file is corrupt, or compression was misconfigured" when WebGL build is opened
Reproduction steps:
- Open the provided project
- Build And Run the project on WebGL platform
Expected result: The build opens without any errors
Actual result: The build opens with an error:
“Unable to parse Build/10d91a12865a7ba6ccc4168c86733d38.js.unityweb! The file is corrupt, or compression was misconfigured? (check Content-Encoding HTTP Response Header on web server)”
Reproducible with: 2021.3.4f1, 2021.3.15f1
Not reproducible with: 2020.3.42f1
Could not test with: 2022.1.23f1, 2022.2.0f1, 2023.1.0a21 (Sysroot Base package errors when converting to other Unity Editor versions)
Reproducible on: macOS 13.0 (M1 Max), macOS 13.0.1 (Intel)
Notes:
- Forum for the issue https://forum.unity.com/threads/getting-invalid-js-from-user_jspre_placeholder.1246204
- The Unity WebGL build replaced "g=$&th^~$&sh" in sha512.min.jspre with "g=Module["USER_JSPRE_PLACEHOLDER"] = "USER_JSPRE_PLACEHOLDER";th^~Module["USER_JSPRE_PLACEHOLDER"] = "USER_JSPRE_PLACEHOLDER";sh"
- Unknown regression version
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2023.3):
Verified the issue is fixed in Ubuntu 22.04 in 2023.3.0a17