Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X, 2022.1.X
Votes
1
Found in
2020.1.0a7
2020.3
2021.2
2021.2.13f1
2022.1
2022.2
Issue ID
1407718
Regression
Yes
MonoBehaviour Scripts cause compilation errors when the namespace contains a line break
How to reproduce:
1. Open the user-submitted project
2. Open the scene "Reproduction" (Assets/Scenes/Reproduction.unity)
3. In the Hierarchy window, select the GameObject "BrokenMonoBehaviour"
4. In the Inspector window, observe the "Broken Mono Behaviour" Component
Expected result: "Does This Mono Behaviour Work" bool is seen
Actual result: "The associated script can not be loaded" warning is seen
Reproducible with: 2020.1.0a7, 2020.3.30f1, 2021.2.15f1, 2022.1.0b11, 2022.2.0a7
Not reproducible with: 2019.4.36f1, 2020.1.0a6
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a11
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0f1
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.4f1