Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2021.1.X
Votes
2
Found in
2019.3
2019.3.7f1
2020.2
Issue ID
1232538
Regression
No
[SerializeReference] CustomPropertyDrawer doesn't get correct value when multiple elements use the same attribute in collection
How to reproduce:
1. Open user's attached project
2. Open "SampleScene" Scene
3. Select "GameObject" in Hierarchy
4. In the Inspector expand "Foos"
5. In the Inspector expand "SpecificElementA", "SpecificElementB", "WorkaroundElementC"
Expected result: Under the "SpecificElementB" the 3rd field should say "FooBarred: Unfortunately Yes"
Actual result: Under the "SpecificElementB" the 3rd field says the same as "SpecificElementA" 3rd field which is "FooBarred: Yes"
Reproducible with: 2019.3.0f1, 2019.3.9f1, 2020.1.0b5, 2020.2.0a7
Could not test with: 2017.4.39f1, 2018.4.21f1, 2019.3.0a1 because [SerializeReference] was introduced in 2019.3.0a2, 2019.3.0b12 because the elements get the attribute name (member) instead of attribute
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2020.2):
Fixed in 2021.2.0a4
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b7
Resolution Note (fix version 2020.2):
Fixed in 2020.2.6f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.22f1