Search Issue Tracker
Fixed
Fixed in 1.28.1, 2.7.4
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment