Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.2.0a1
2017.2.0f3
Issue ID
968739
Regression
Yes
Errors appear when changing size of an array with serializable objects via Inspector
How to reproduce:
1. Open attached Unity project "New Unity Project"
2. Load scene "s"
3. Enter Play mode
4. Select GameObject
5. In the inspector Change Size of the Array
Expected result: New element appears in the array without any errors.
Actual result: New element appears in the array along with two errors for each element: "GetBool is not allowed to be called during serialization, call it from Awake or Start instead".
Reproducible with: 2018.1.0a3, 2017.3.0b9, 2017.2.0p2.
Not reproducible with: 2017.1.2p2, 5.6.4p2, 5.5.5p1.
Note: resizing array via script cause not errors.
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