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
- “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:
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