Search Issue Tracker
Fixed in 1.3.2
Votes
0
Found in [Package]
0.6.8, 1.1.7
Issue ID
1175938
Regression
No
Non-duplicate assets are detected when analyzing Duplicate Bundle Dependencies
Repro steps:
1. Open attached project
2. Go to Window/Asset Management/Addressables
3. In the Addressaables window, press "Analyze"
4. In the Analyze window, expand "Analyze Rules", "Fixable Rules" elements and press on "Check Duplicate Bundle Dependencies"
5. Click "Analyze Selected Rules"
6. Expand everything under "Check Duplicate Bundle Dependencies"
Expected result: Only duplicate assets ("TXR_3D_Common_Palette_128x128" and "MAT_Common_Palette") appear
Actual result: An asset, that is only used once ("Shower_01.FBX"), appears with the duplicate assets
Reproducible with: 2018.4.0f1, 2019.1.14f1, 2019.2.1f1, 2019.3.0a12
Could not test with: 2017.4.31f1 (no Package Manager)
Reproducible with package versions: 0.6.8, 0.7.5, 1.1.3, 1.1.7
Could not test with package versions: 0.5.3 (errors)
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
- Fix for 2022.3.X: Flickering of HDRP Directional Light shadows with DirectionalMixedCachedShadows when in an Entities Graphics rendered Subscene
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
Resolution Note (fix version 1.3.2):
The single used asset is no longer being registered with the bundle that has duplicate assets. Fixed in Addressables package version 1.3.3