Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.46f1
2021.3.22f1
2022.2.13f1
2023.1.0b10
2023.2.0a8
Issue ID
UUM-31355
Regression
No
Multiple "Identifier expected", "{ expected" and "} expected" errors are thrown when naming a Script by a number
How to reproduce:
1. Open the attached “My Projectaasdasd.zip“
2. Create a new C# Script (Right click > Create > C# Script)
3. Name the Script “1”
Expected result: No errors are thrown in the Console window
Actual result: Multiple "Identifier expected", "{ expected" and "} expected" errors are thrown in the Console window
Reproducible with: 2020.3.46f1, 2021.3.23f1, 2022.2.13f1, 2023.1.0b10, 2023.2.0a8
Reproduced in: macOS Monterey 12.6
Note: Issue is not reproducible when creating a script without naming it by a number and then renaming the script to a number
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
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
- Warnings due to obsolete Object.FindObjectsByType<T> usage and [SerializeReference] are logged when opening the Netcode for Entities setup scene
- Non-standard pointers cannot change Inspector values with arrow controls when crossing Inspector area
- No longer able to change the Toggle or Slider GameObjects' Target Graphic value and a NullReferenceException is thrown when the Target Graphic value is set to None at any point
Resolution Note:
It is not possible to have a script that starts with a number. The compilation error is a bit cryptic.
Resolution Note (2023.2.X):
It is not possible to have a script that starts with a number. The compilation error is a bit cryptic.