Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3
2020.1
Issue ID
1187967
Regression
No
[SerializeReference] looses object reference to Material in build
Reproduction steps:
1. Open the attached project "SerializeReference" and scene "MaterialList"
2. In the Hierarchy, select "MaterialList" and make sure "Test1", "Test2" materials are attached to the "Materialcells" list
3. Enter Play Mode and see both Materials being logged in the Console
4. Build and Run the project.
5. Open Player Log by clicking the three dots in the right corner of the Console window and selecting "Open Player Log"
Expected result: Both Materials are being logged in the Player Log
Actual result: Materials are null
Reproducible with: 2019.3.0a2, 2019.3.0b6, 2020.1.0a8
Could not test with: 2017.4.33f1, 2018.4.11f1, 2019.2.8f1, 2019.3.0a1 (SerializeReference inaccessible due to its protection level)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.1):
Fixed in 2019.3.0f1, 2020.1.0a15