Search Issue Tracker
Fixed
Fixed in 6000.3.15f1, 6000.4.6f1, 6000.5.0b7, 6000.6.0a5
Votes
0
Found in
6000.0.62f1
6000.2.12f1
6000.3.0b9
6000.4.0a4
6000.5.0a1
6000.6.0a1
Issue ID
UUM-126159
Regression
Yes
"[CreateProperty]" on nullable generic types causes compilation error when using a non-nullable type
Reproduction steps:
1. Open the attached “IN-120943” project
2. Observe the Console window
Expected result: Property bags are generated successfully without any compilation errors
Actual result: Compilation fails due to incorrect type being generated for the nullable generic property. Error: {{Cannot implicitly convert type 'bool?' to 'bool'. An explicit conversion exists (are you missing a cast?)}}
Reproducible with: 6000.0.60f1 (f02d6f9f9009), 6000.0.62f1, 6000.2.12f1, 6000.3.0b9, 6000.4.0a4
Not reproducible with: 2022.3.66f1, 6000.0.59f2 (ef281c76c3c1)
Reproducible on: Windows 11, Ubuntu 24.04
Not reproducible on: No other environments tested
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 Scripting::ScriptingWrapperFor when exiting Play Mode during an active web request
- Material Inspector shortly disappears resulting in "Add Component" button jumping when the Material is recompiled
- Hand Interaction Profile breaks hand teleport to arbitrary locations
- Grabbing Dynamic Attach interactable in Interaction Simulator makes controller spin
- XRI Starter Assets Interactable shader generates Console warnings
Resolution Note (fix version 6000.6.0a5):
Fixed in 6000.6.0a5
Resolution Note (fix version 6000.5.0b7):
Fixed in 6000.5.0b7
Resolution Note (fix version 6000.4.6f1):
Fixed in 6000.4.6f1
Resolution Note (fix version 6000.3.15f1):
Fixed in 6000.3.15f1