Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0b6
Issue ID
1092037
Regression
Yes
Use of unassigned local variable error after upgrading project
Steps to reproduce:
1. Open attached project
2. Notice error "Use of unassigned local variable 'val'"
Reproduced with: 2018.3.0b6, 2019.1.0a5
Not reproducible: 2018.2.13f1
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note (2018.3.X):
The Roslyn C# compiler reports some warnings that the mono C# compiler did not. I have added section at end of Upgrade Doc mentioning potential of new compiler warnings from Roslyn.