Search Issue Tracker
Active
Fixed in 2.7.4
Under Consideration for 1.28.X
Votes
0
Found in [Package]
2.7.2
Issue ID
ADDR-4068
Regression
Yes
Custom group templates don’t keep enum values from the custom schema when there’s more than one schema
How to reproduce:
1. Open the “Addressable Test.zip“ project
2. Open the Window → Asset Management → Addresables → Groups window
3. Create a new “Unexpected Behaviour“ group in the Addressables Groups window
4. Select the “Unexpected Behaviour1“ Group and observe the Inspector
Expected result: The “Custom Description” field under “Custom Schema“ is set to “Option B“
Actual result: The “Custom Description” field under “Custom Schema“ is set to “Option A“
Reproducible in: 1.22.2, 1.27.0 (2022.3.66f1), 2.1.0, 2.7.2 (6000.0.57f1, 6000.2.4f1, 6000.3.0b1)
Not reproducible in: 1.21.21 (2022.3.66f1), 2.0.8 (6000.0.57f1)
Reproduced on: Windows 11 Pro (24H2)
Note: If a Domain Reload is triggered or the project is restarted, the “Unexpected Behaviour1” asset will change the enum to the expected “Option B”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Addressables Report window UI is broken when opening via Build > New Build > Default Build Script
 - Addressables Profiles window UI break when creating a new Variable with a long name
 - No character limit when renaming Profile in Addressables Profile window, allowing excessively long names
 - Blurry, low quality Active Profile icon used in Addressables Profiles window
 - Tree Asset Preview window is not updated after assigning a new Material
 
Add comment