Search Issue Tracker
Fixed
Votes
1
Found in [Package]
1.3.3
1.6.0
1.8.3
Issue ID
ADDR-1018
Regression
Yes
[Addressables] All Asset Bundles from local Build Path group are rebuilt when an asset is added or removed
How to reproduce:
1. Open project from "AddressableRebuildBug.zip"
2. Open "Addressables Groups" window and build player content
3. Open "Library\\com.unity.addressables\\StreamingAssetsCopy\\aa\\Windows\\StandaloneWindows" with file explorer
4. In "Addressables Groups" window move "Sphere.prefab" to "Default Local Group"
5. "Update a Previous Build"
6. Check changes to files and modification timestamps at folder opened in step 3
Expected result: Only "defaultlocalgroup_assets_sphere.prefab.bundle" is created
Actual result: "defaultlocalgroup_assets_cube.prefab.bundle" and "localgroup2_assets_capsule.prefab.bundle" get modified, "defaultlocalgroup_assets_sphere.prefab.bundle" is created
Reproducible with: 2018.4.17f1, 2019.3.1f1, 2020.1.0a23
Could not test with: 2017.4 - packages not supported
Reproducible with packages: 1.3.3, 1.6.0
Not reproducible with package: 1.2.4
Note: Does not reproduce if the asset is moved to Remote group after being moved between local groups first
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
CanisLupus
May 25, 2020 11:58
Now this was update to "By Design"...
It can't be!
This problem also happens for remote content (i.e. even if we use "Can change post release"). My issue (1234854) was marked as a duplicate but has a reproduction for remote assets, please check it.
This is a very important bug! We literally can't publish our game while this bug exists, otherwise the smallest update with a new file will cause ALL USERS to redownload ALL ADDRESSABLES they had previously.
CanisLupus
May 04, 2020 13:43
Also:
1. This doesn't seem to be true for us (?), or we misunderstood: "Does not reproduce if the asset is moved to Remote group after being moved between local groups first"
2. This also happens for a new build, not only update content. Normally, creating a new build will generate the same files if no changes were made.
CanisLupus
May 04, 2020 13:33
Just wanted to add that this is also reproducible with the most recent version, 1.8.3.
Any ETA on the fix?