Search Issue Tracker
Fixed
Fixed in 2022.2.12f1, 2023.1.0b9, 2023.2.0a6
Votes
0
Found in
2022.2.7f1
2023.1.0b5
2023.2.0a3
Issue ID
UUM-27561
Regression
Yes
UnityEvent listener execution state is Off by default
Reproduction steps:
1. Open the “OffByDefault” project
2. Open the “SampleScene“ scene
3. Select the “Test” GameObject
4. In Inspector click the “+” button to add a listener the “TestEvent” UnityEvent
5. Observe the execution state (top left) of the added listener
Expected result: the state is “RuntimeOnly“
Actual result: the state is “Off“
Reproduced in: 2022.2.0a9, 2022.2.7f1, 2023.1.0b5, 2023.2.0a3
Not reproduced in: 2020.3.45f1, 2021.3.19f1, 2022.2.0a8
Reproduced using: macOS 13.0.1 (Intel), Windows 10 (by the reporter)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2023.2.0a6):
Adding a new PersistentCall to a UnityEvent is added with the default value UnityEventCallState.RuntimeOnly instead of UnityEventCallState.Off