Search Issue Tracker
Active
Under Consideration for 6000.4.X
Votes
0
Found in
6000.0.69f1
6000.3.11f1
6000.4.0b11
Issue ID
UUM-137755
Regression
No
Deserialized byte array inside of a struct is invalid when accessed through a PropertyDrawer
How to reproduce:
1. Open the attached project “IN-137880”
2. Open the “ReproScene”
3. In the Hierarchy, select the “ObjectWithGuid (Select me to repro)” GameObject
4. Observe the Console
Actual result: Deserialized byte array is invalid and “Bytes length (-1005524112) is invalid.” is logged to the Console
Expected result: Deserialized byte array is valid and “Identifier (…) is valid.” is logged to the Console
Reproducible with: 2023.1.0a3, 6000.0.71f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0a6
Not reproducible with: 6000.5.0b1, 6000.6.0a1
Fixed in: 6000.5.0a7
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
Add comment