Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.19.18
Issue ID
ADDR-2564
Regression
No
Bundles have non-deterministic binary differences when building with Addressables
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 "packedassets_scenes_all.bundle" to a separate directory and name it 1.bundle
8. Return to the Editor, go to the Assets folder in the Project window, and delete NewBehaviourScript.cs
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 "packedassets_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.19.4, 1.19.18 (2019.4.36f1, 2020.3.30f1, 2021.2.14f1, 2022.1.0b10, 2022.2.0a7)
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
- Crash on DynamicHeapAllocator::CreateTLSFBlock when opening a specific project
- Scene flickers when using Mesh Output with SpriteLit Shader in 2D project
- “Cache Management” text is misaligned in Preferences > Package Manager
- [macOS] network permission shows the name of previously closed app when different app requests network access
- Delta value returned by mouse movementsMonitor is different when changing Screen Resolution
Resolution Note:
There are no fixes planned for this Bug