Search Issue Tracker
Won't Fix
Votes
12
Found in
2020.3.17f1
2021.1.17f1
2021.2.0b9
2022.1.0a5
2023.1.0a1
2023.2.0a1
2023.3.0a3
Issue ID
UUM-6894
Regression
No
Identical Asset bundles differ bitwise when building Addressable content
How to reproduce:
1. Open the user's attached project
2. Open Scenes/SampleScene
3. Go to Window -> Asset Management -> Addressables -> Groups
4. In the toolbar of the Addressables Groups window, select Build -> Clean Build -> All
5. Select Build -> New Build -> Default Build Script
6. In the project folder, find the directory Library/com.unity.addressables/aa/OSX/StandaloneOSX (or Library/com.unity.addressables/aa/Windows/StandaloneWindows64)
7. Copy the file "samplescene_scenes_all<...>.bundle" to a separate directory and name it 1.bundle
8. In the Editor, go to the Game view and change the Aspect ratio in the toolbar
9. In the toolbar of the Addressables Groups window, select Build -> Clean Build -> All
10. Select Build -> New Build -> Default Build Script
11. Go to the previously navigated Project Library directory
12. Copy the file "samplescene_scenes_all<...>.bundle" to a separate directory and name it 2.bundle
13. Perform a binary comparison on these two bundle files (can be done with the "diff" command through the macOS Terminal)
Expected result: the two bundles are identical
Actual result: the two bundles differ although Asset content did not change
Reproducible with: 1.16.19, 1.18.15 (2019.4.29f1, 2020.3.17f1, 2021.1.17f1, 2021.2.0b9, 2022.1.0a5)
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
- Editor default Stylesheet/Matching Selector buttons in Debugger don't do anything
- Graphics.DrawMeshNow stops rendering Render Texture after a few frames when viewed in the Player
- New selector in Matching Selectors displays as on line -1 in debugger
- The first frames are skipped when playing a video
- Text auto-scrolling can not work when naming assets/objects until backspace key is pressed
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are committed to resolving other higher-priority issues and delivering the new UI system. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However, we know each case is different, so please continue to log any issues you find and provide any general feedback on our roadmap page to help us prioritize.
Forum announcement
https://forum.unity.com/threads/ui-toolkit-update-q3-2022.1329159/
Roadmap https://unity.com/roadmap/unity-platform/ui