Search Issue Tracker
Fixed in 2022.1.X
Fix In Review for 2020.3.X, 2021.2.X
Votes
2
Found in
2020.1.0a19
2020.3
2020.3.11f1
2021.1
2021.2
2022.1
Issue ID
1341180
Regression
Yes
TextAsset.bytes includes UTF-8 header when loading a file from AssetBundle
How to reproduce:
1. Open the attached '1341180.zip' project
2. Open the SampleScene
3. Enter the Play mode
4. Press the 'Load' button
5. Observe the Console
Expected result: 'textAsset.bytes.Length 4' gets printed in the Console
Actual result: 'textAsset.bytes.Length 7' gets printed in the Console
Reproducible with: 2020.1.0a19, 2020.1.17f1, 2020.3.14f1, 2021.1.14f1, 2021.2.0b3, 2022.1.0a1
Not reproducible with: 2018.4.36f1, 2019.4.29f1, 2020.1.0a18
Note:
- AssetBundles can be rebuilt via Assets > Build AssetBundles
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
- FP32 is used for a temporary when compiling a shader for GLES or Vulkan
- The highlight that was created with Highlighter.Highlight does not disappear when the window is closed with the element
- [URP] CommandBuffer warnings thrown while debugging Depth Overlays with Post-processing enabled in Rendering Debugger
- hlslcc: float image atomics don’t work
- [Apple silicon][M1] Game view FPS is very low when the view is moved to an external display
Resolution Note (fix version 2022.1):
The inconsistency was caused by `bytes` getter fix that made it return all text asset data. Inconsistencies with UTF headers showing up in newly bundled assets can easily be solved by using encodings that won't produce headers.