Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2020.3.46f1
2021.3.21f1
2022.2.12f1
2023.1.0b9
2023.2.0a6
2023.3.0a3
6000.0.0b11
Issue ID
UUM-31685
Regression
No
RegisterValueChangeCallback is not called when changing the PropertyField value
Reproduction steps:
1. Open the attached project “CallBackBug“
2. Open the Project Settings (Edit > Project Settings)
3. Go to the “SingletonRegisterIssue” tab
4. Modify the “Export Destination” property
Expected result: The changes are logged in the Console Window
Actual result: The RegisterValueChangeCallback does not register any changes
Reproducible with: 2020.3.46f1, 2021.3.21f1, 2022.2.12f1, 2023.1.0b9, 2023.2.0a6
Reproducible on: Windows 11
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.