Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.0a1
2019.3.0f6
2020.1
2020.2
Issue ID
1261524
Regression
Yes
String array data is lost when one of the strings starts with a colon symbol
How to reproduce:
1. Open the attached project (case-1261524.zip)
2. In the Project window select the 'test' ScriptableObject
3. In the Inspector window expand the Strings field and set Element 1 to ':one'
4. Exit and reopen Unity
5. Select 'test' ScriptableObject again
Expected result: the field 'Strings' remains unchanged
Actual result: all the Elements starting with a colon symbol got removed and an Element before them got set to an empty string (size = '2', Element 0 = '', Element 1 = 'two')
Reproducible with: 2019.3.0a1, 2019.4.3f1, 2020.1.0b15, 2020.2.0a17
Not reproducible with: 2018.4.24f1, 2019.2.0b10, 2019.2.21f1
Notes:
1. The issue doesn't occur when a colon is not the first symbol of a string
2. The issue occurs only with an array of strings (not with char, char[], string)
3. The issue also occurs when a Script with string array field is used as a Component to a GameObject
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a21
Resolution Note (fix version 2020.1):
Fixed in 2020.1.4f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.9f1