Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.33f1
2021.3
2022.1
2022.2
Issue ID
1421764
Regression
No
Unity editor will not recognize MonoBehaviour when it has certain text combination in the source file
Reproduction steps:
1. Open the attached project "Temp2020.3.33.zip"
2. In the Project window select the "StrangeBehaviour" C# script
3. Look for the message in the Inspector window
Expected result: An inactive code block inside the preprocessor should not affect MonoBehaviour validity
Actual result: An inactive code block inside the preprocessor affects the MonoBehaviour validity
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.4f1, 2022.1.3f1, 2022.2.0a13
Not reproducible with: 2022.2.0a14, 2022.2.0a16
Reproduced on: Windows 10 Pro
Notes:
- The Editor does not recognize the $"{}" combination, however it recognizes combinations //$"{}", $"{x}", "{}"
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
- The build size is larger when Models have Animation Type set to Generic
Resolution Note (fix version 2022.2):
FIxed in: 2022.2.0a14