Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.5.X
Votes
0
Found in
6000.0.64f1
6000.3.1f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-129886
Regression
No
UTF-8 character in index.html is corrupted when building a WebGL project
How to reproduce:
1. Use a text editor to open “IN-124125_UnityWebGL_UTF8_Bug > Assets > WebGLTemplates > TestTemplate > index.html”
2. Observe the character in line 7 “CHARACTER:"
3. Open the “IN-124125_UnityWebGL_UTF8_Bug” project
4. Build the project for Web platform
5. In the build folder “index.html” file, line 7 observe the “CHARACTER:"
Actual result: The character stays the same “Ö”
Expected result: The character gets corrupted and displays the question mark symbol
Reproducible with: 2023.1.0a6, 6000.0.64f1, 6000.3.1f1, 6000.4.0b1, 6000.5.0a3
Reproducible on: macOS Tahoe 26.1, Windows 11 (by user)
Not reproducible on: no other environments tested
Note: After unzipping the project the character can appear as corrupted, instead use a hex editor and observe the hex values, the correct value is “D6”, the corrupted will appear as “EF BF BD”.
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:
We were unable to reproduce this issue as there appears to be an overall encoding issue with the input files (They started off as Latin-1/Windows-1252 and were converted to UTF-8) causing the build process to have issues, to solve this it is recommended to edit the files using a known good text editor and ensure they are UTF-8 from the start as this makes the issue not reproducable.
Resolution Note (6000.5.X):
We were unable to reproduce this issue as there appears to be an overall encoding issue with the input files (They started off as Latin-1/Windows-1252 and were converted to UTF-8) causing the build process to have issues, to solve this it is recommended to edit the files using a known good text editor and ensure they are UTF-8 from the start as this makes the issue not reproducable.