Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.1.0a7
2020.1.0b14
2020.2
Issue ID
1261028
Regression
Yes
'pragma warning restore' causes scriptable object to not be valid and unable to compile when new line after is not present
How to reproduce:
1. Open attached project "Pragma Warning Scriptable Object.zip"
2. In Project window, right-click "NotWorkingSO" script -> Reimport
3. In Project window, select "NotWorkingSO" scriptable object
4. Observe Inspector window
Expected result: no error is thrown, "thing" variable is visible
Actual result: "The associated script can not be laoded. Please fix any compile errors and assign a valid script" is thrown
Reproducible with: 2020.1.0a7, 2020.1.0b15, 2020.2.0a17
Not reproducible with: 2018.4.23f1, 2019.4.3f1, 2020.1.0a6
Workaround: Insert a new line after pragma restore line
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a21