Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.4
2019.4
2020.2
2020.2.4f1
2020.3
2021.1
2021.2
Issue ID
1325751
Regression
No
Moving MonoBehaviour to Assembly breaks Event Listener when a method has an argument in the same Assembly
How to reproduce:
1. Open the user's attached project
2. Open 'SampleScene'
3. In the Hierarchy select Canvas > Button
4. Observe the OnClick handler in the Inspector (the Function field is set to EventListenerSample.ListenToOnClick)
5. In the Project window open Assets > Scripts
6. Right-click in the Scripts folder and select Create > Assembly Definition
7. After recompilation, in the Hierarchy select Canvas > Button
8. Observe the OnClick handler
Expected result: The Function field is set to 'EventListenerSample.ListenToOnClick'
Actual result: The Function field is set to 'Missing EventListenerSample.ListenToOnClick'
Reproducible with: 2018.4.33f1, 2019.4.24f1, 2020.2.7f1, 2020.3.3f1, 2021.1.2f1, 2021.2.0a12
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This is a known issue that will require a significative work on tracking Fully Qualified Name usage across all scenes/prefabs assets. We have plans to work on it, but unfortunately it will not be worked on yet.
I am closing this as Postponed as we are aware of it and making plans to fix this category of issues in a future release.