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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note (fix version 2022.2):
FIxed in: 2022.2.0a14