Search Issue Tracker
Fixed
Fixed in 2022.3.60f1
Votes
0
Found in
2022.3.53f1
Issue ID
UUM-88934
Regression
Yes
Only "ArgumentNullException: Value cannot be null" is displayed instead of all the actual errors when opening a project with numerous compilation errors
How to reproduce:
1. Open the “ArchTest” project
2. Open the “SampleScene”
3. Observe the Console
Expected result: The list of errors is displayed in the Console.
Actual result: The only error displayed in the Console is "ArgumentNullException: Value cannot be null."
Reproducible in: 2022.3.12f1, 2022.3.53f1
Not reproducible in: 2021.3.45f1, 2022.3.11f1, 6000.0.28f1, 6000.1.0a6
Fixed in: 2023.1.0a1
Reproduced on: Windows 10, Windows 11 (user’s)
Not reproduced on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- OnPostprocessAllAssets() is not called for a modified Prefab when another Asset is set Dirty in the same callback
- [Android] UIToolkit ClickEvent is fired when the device is rotated
- Compilation errors occur when "uintBitsToFloat(int)" gets used in OpenGLES
- User Reporting does not send reports when Managed Stripping Level is set to Low or higher
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is thrown when launching a project with a corrupted library
Add comment