Search Issue Tracker
Won't Fix
Votes
2
Found in
2020.3.38f1
2021.3.8f1
2022.1.14f1
2022.2.0b5
2023.1.0a8
Issue ID
UUM-12671
Regression
No
Incorrect dependencies are displayed when "Check Scene to Addressable Duplicate Dependencies" Analyze Rule is analyzed
Reproduction steps:
1. Open the attached project “AtlasTest.zip“
2. In the Addressables Analyze window select the "Check Scene to Addressable Duplicate Dependencies" Analyze Rule
3. Click the “Analyze Selected Rule” button
4. Notice that there are 3 duplicate dependencies shown as a result
5. Select the “Bundle Layout Preview” Analyze Rule and press the “Analyze Selected Rules” button
6. Notice that the Sprite Atlas itself contains 4 sprites
7. Open the “Scene_A“ scene
8. Select the Image GameObject and notice the Sprite that is being referenced in the Image component: it does not belong to the addressable Sprite Atlas from step 6
9. Repeat steps 7 and 8 with “Scene_B“ and “Scene_C“ scenes
Expected result: Analyze Rule does not return the duplicate results to the bundle that contains the Addressable Sprite Atlas.
Actual result: The Analyze Rule is returning duplicate results despite the fact that the scenes are not making any references to the Addressable Sprite Atlas.
Reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0b5, 2023.1.0a8
Reproduced on: Windows 10 Pro
Note: Building the player only includes UI Sprite Atlas and building Addressables only includes Particle Sprite Atlas so there are no duplicates being generated in the actual build process. Hence the build behavior for Sprite Atlases are as expected.
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
We're actually replacing this entire tool with the Addressables Build Report tool