Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.3.60f1
6000.0.51f1
6000.1.7f1
6000.2.0b4
Issue ID
UUM-109303
Regression
No
“Parser Failure at line 2: Expected closing '}'“ error is thrown when loading the project
Reproduction steps:
1. Create a project with any template
2. Observe the Console window
Expected result: No errors are thrown
Actual result: “Parser Failure at line 2: Expected closing '}'“ error is thrown
Reproducible with: 2022.3.60f1, 6000.0.51f1, 6000.1.7f1, 6000.2.0b4
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: Link to discussions [https://discussions.unity.com/t/parser-failure-at-line-2-expected-closing/1654688]
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
Third Party Issue is not really the best reason. But the issue has already been resolved on our end through a DNS update. For more information this thread will be updated. https://discussions.unity.com/t/announcement-unity-editor-update-check-service-discontinued/1654579/7