Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.21.19
2.0.9
Issue ID
ADDR-3586
Regression
No
Addressables Build with Unique Bundle IDs fails when Bundle Naming Mode is set to Filename
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the Addressables Groups window (Window > Asset Management > Addressables > Groups)
3. Build the Addressables content (Build > New Build > Default Build Script)
4. Observe the Console and check the built bundles in the File Explorer (<PathToProjectDirectory>/Library/com.unity.addressables/aa/Windows/StandaloneWindows64)
5. In the Project window, select “Assets/AddressableAssetsData/AssetGroups/Default Local Group.asset“ Asset
6. Change “Bundle Naming Mode” to “Append Hash To Filename”
7. Repeat steps 3 and 4
Expected result: The Build completes successfully with both “Bundle Naming Mode” options
Actual result: The Build with “Append Hash to Filename” option selected builds successfully, while with the “Filename” option, it gives errors in the console and does not create the bundles
Reproducible with: 1.21.19 (2021.3.33f1, 2022.3.15f1, 2023.2.3f1, 2023.3.0a15), 2.0.6 (2023.2.3f1, 2023.3.0a19)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: When using the option “Filename”, after the building process is finished, in the Console it logs “Addressable content successfully built”, even if there were errors and the bundles were not created successfully
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.