Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.2.X
Votes
0
Found in
2022.3.62f1
6000.0.50f1
6000.1.5f1
6000.2.0b3
Issue ID
UUM-107651
Regression
No
The code editor does not decompile the String.cs code when the API Compatibility Level is set to ".Net Standard 2.1"
Reproduction steps:
1. Open the attached “IN-98860” project
2. Open the “Script.cs” script
3. Right-click on “string” and select “Go To Definition” (If using JetBrains Rider, select “Go To Declaration and Usages”)
4. Observe the opened file
Expected result: The code editor will correctly decompile and open the original String.cs code
Actual result: The code editor won’t decompile the String.cs code and instead will open the reference System.cs code
Reproducible with: 2022.1.0a3, 2022.3.62f1, 6000.0.50f1, 6000.1.5f1, 6000.2.0b3
Reproducible environments: Windows 11 (by reporter), macOS 15.5
Not reproducible environments: No other environments tested
Note: Editor scripts (Scripts in the “Editor” folder) do get decompiled as expected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment