Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.0
Issue ID
ECSB-182
Regression
No
An exception is thrown when calling GetSingleton<>() in specific method constellation
Reproduction steps:
1. Open the “My project” Project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Open the “Assets/Scripts/AnySystem.cs” Script and observe lines 29-30
4. Observe the Console Window
Expected result: No error is displayed in the Console Window
Actual result: An error is displayed in the Console WIndow
Reproducible with: 0.51.1-preview.32 (2021.3.17f1)
Could not test with:
- 0.51.1-preview.21 (2020.3.44f1 (error CS0619: 'FixedString128' is obsolete: 'Renamed to FixedString128Bytes (UnityUpgradable) -> FixedString128Bytes'))
- 0.17.0-preview.42 (2021.3.17f1 (error CS8377: The type 'U' must be a non-nullable value type, along with all fields at any level of nesting, in order to use it as parameter 'T' in the generic type or method 'NativeList<T>'))
- 1.0.0-pre.15 (2023.1.0a26 various Library/PackageCache/com.unity.collections@2.1.0-pre.6 errors)
Reproduced on: Intel MacOS 13.1
Notes:
- if you comment the line 29 and call and return it through a separate method (uncomment line 30), the issue does not occur.
- The issue does not occur in the OnUpdate() function
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
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
- [Usability] Selected node gets unselected when undoing changes in the Graph Inspector Node Settings tab
- Search Default option for Column Format does not reset the column's format
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.0.X):
There are no fixes planned for this Bug