Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2020.1.0a7
2020.2
2020.2.0b12
2021.1
Issue ID
1295088
Regression
Yes
Preprocessor blocks cause script to no longer be recognized as a MonoBehaviour
Reproduction steps:
1. Open user's attached project
2. In Project window, select and open the script in Assets folder
3. Observe the Inspector window
4. In script editor, comment out lines 2-3
5. Observe the Inspector window
Expected result: No warning on either observation
Actual result: "No MonoBehaviour scripts in the file" warning when lines are not commented out
Reproducible with: 2020.1.0a7, 2020.1.15f1, 2020.2.0b13, 2021.1.0a7
Not reproducible with: 2019.4.15f1, 2020.1.0a6
Could not test with: 2018.4.29f1 (console errors break project)
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
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
- Unity Perforce Integration: VCS Connection Active State Fails via CLI with Valid Inputs
- Joint Gizmos for anchor and connectedAnchor do not respect their defined bodies when Swap Bodies is enabled
- Project Settings window opens up with a blank details pane when the "Configure" button is clicked in the Package Manager after installing the Cloud Diagnostics package
- [UI Builder] Viewport's gizmos for Margin and Padding disappear when dragging to modify the value and the cursor leaves the Spacing section
Resolution Note (fix version 2021.1):
Fixed in 2021.2.0a1
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b1
Resolution Note (fix version 2020.2):
Fixed in 2020.2.2f1