Search Issue Tracker


Fixed in 2022.3.13f1, 2023.1.19f1, 2023.2.0b16, 2023.3.0a12



Found in





Issue ID




PropertyDrawer is not refreshing when populating [SerializeReference] fields in the Inspector Window



How to reproduce:
1. Open the user-attached “” Project
2. Select the “New Test Scriptable Object.asset” found in the Assets folder in the Project window
3. In the Inspector Window add a new element to the Integer and Float arrays under the “Expected To Break” Drop-down
4. Observe the Inspector Window

Expected result: The PropertyDrawer is populated and the new variables are visible in the Inspector Window
Actual result: The PropertyDrawer is populated, but the new variables are not visible in the Inspector Window

Reproducible with: 2022.2.0a13, 2022.3.11f1, 2023.1.16f1, 2023.2.0b13, 2023.3.0a9
Not reproducible with: 2021.3.31f1, 2022.2.0a12

Reproduced on: macOS Sonoma 14.0 (Intel)
Not reproduced on: No other environment tested

- Reproducible on a new project
- Workaround: De-select and re-select the Asset and the PropertyDrawer will show the new variables correctly
- The reporter noted that Tiago investigated the issue a bit and found this information:
" So, the issue is with propagating the refresh messages - modifications get received as expected, from any property drawer that references that field, but the refresh only gets responded to by the first registered responder, which causes the refresh to happen in the property drawer with the first path that refers to that object and not in any other paths. And if the first path is hidden, the first path makes the refresh message go nowhere."

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.