Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
6
Found in
2018.4.9f1
2019.2
2019.2.17f1
2019.3
2020.1
Issue ID
1211380
Regression
Yes
Dynamic functions unavailable when private generic UnityEvent<T> fields have [SerializeField] attribute
Steps to reproduce:
1. Open the attached project (case_1211380.zip)
2. Select the "Test" Game Object
3. Click the plus icon under "Derived Event Bug ()" (expand "Container" if not expanded already)
4. Select "Test" as the Object
5. Click on "No Function" and navigate to BugExample context menu
Expected result: EventHandler can be selected as a dynamic function
Actual result: Only the static EventHandler function can be selected
Reproduced in: 2018.4.9f1, 2019.2.18f1, 2019.3.0f5, 2020.1.0a20
Not reproducible in: 2017.4.36f1, 2018.4.8f1
Notes:
- In 2018.4.9f1 & 2018.4.10f1 dynamic functions are unavailable for all generic UnityEvent<T> fields
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a23
Resolution Note (fix version 2019.3):
Fixed in 2019.3.5f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.19f1