Search Issue Tracker
Fixed in 1.16.0
Votes
0
Found in [Package]
1.3.3, 1.5.0
Issue ID
1197058
Regression
No
[Addressables] AssetReferenceUILabelRestriction("LabelName") Attribute is disregarded when used in a nested sub class
How to reproduce:
1. Open the attached project ("case_1197058-AssetReferenceUIBug.zip")
2. Open the repro scene ("SampleScene")
3. Select the "Testing" GameObject n the Hierarchy
4. Select the "AssetReferenceWithLabel_4_Nested" variable and check which assets can be selected
Expected results: Only the assets which have "Restricted" label can be selected
Actual results: All assets can be selected, even the ones without the specified label
Reproducible with: 2018.4.15f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
Couldn't test with 2017.4 (No package manager)
Reproducible with package versions: 1.3.3, 1.5.0
Couldn't test with earlier package versions because of the missing "AssetReferenceUILabelRestriction" attribute
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 1.16.0):
Issue is fixed. The attribute now works in all nested classes, whatever the level.