Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.2.0a6
2019.2.9f1
2019.3
2020.1
Issue ID
1192834
Regression
Yes
TextAsset.bytes returns different bytes with different file extensions
Reproduction steps:
1. Open project in "TextTest.zip"
2. In "TextAssetTest.cs" the test will compare bytes of 2 identical files (text wise) but with different extensions (".txt", ".bytes")
3. Open Test Runner window (Window -> General -> Test Runner)
4. Click "Run All"
Expected result: test will not fail
Actual result: test fails
Reproducible with: 2019.2.12f1, 2019.3.0b10, 2020.1a12
Not reproducible with: 2017.4.33f1, 2018.4.12f1, 2019.2.0a5
Notes:
1. TextAsset.bytes documentation implies that for getting bytes of a file, it needs to have the extension ".bytes". Even though documentation is the same for all versions, the behavior is different
2. Only some characters in files cause the issue, such as 'š', 'ž', for example. Otherwise, test results with .txt and .bytes extensions will be the same
3. Test is defined in "TextTestAsset.cs"
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 2020.1):
https://docs.unity3d.com/ScriptReference/TextAsset-bytes.html
In order to get actual bytes from file, .bytes extension must be used.
If different extension is used, returned bytes are received from TextAsset.text string value by decoding it to UTF8 format
Fixed in 2020.1.0a17