Search Issue Tracker
Won't Fix
Votes
1
Found in
5.5.5f1
Issue ID
969840
Regression
No
MonoBehaviour script with a Namespace and an Interface which has a method with a parameter cannot be loaded
Steps to reproduce:
1. Open attached “ScriptLoaded.zip” project
2. Open “Main” scene
3. Select “Doesn’t work” object in Hierarchy
4. Look at the attached script component in Inspector
Expected results:
Script is loaded
Actual results:
Script cannot be loaded
Reproduced in: 2018.1.0a5, 2017.3.0b10, 2017.2.0p2, 2017.1.2p3, 5.6.4p3, 5.5.5p1, 5.4.6f3, 5.3.8p2
Note: Script can be loaded after removing either method parameters or the namespace
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.