Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X, 2022.1.X
Votes
0
Found in
2020.3
2021.2
2021.2.4f1
2022.1
2022.2
Issue ID
1405245
Regression
Yes
[Addressables] Bundles get compressed in Android builds
Reproduction steps:
1. Open project "LoadingTest"
2. Build the project (Build Settings > Build)
3. Change the extension from .apk to .zip
4. Open the zip file in 7zip
5. Go to assets > aa > Android
Expected result: Both files have the Method "Store"
Actual result: Both files have the Method "Deflate"
Reproducible with: 1.19.4 (2020.3.30f1), 1.19.19 (2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a8)
Not reproducible with: 1.18.19 (2020.3.30f1)
Could not test with: 2019.4.36f1 (Gradle build failed)
Note:
-To test this on macOS, you can use the Terminal command "zipinfo <path_to_apk>" to check the Method
Comments (1)
-
davidla_unity
May 06, 2022 15:14
Hey, just wanted to post. This ticket is marked as "Won't Fix" since it won't be fixed by the Addressables team. This is an issue with the Android gradle in the Editor and the fix needs to go into the Editor, not the Addressables package.
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
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a15
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.3f1
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.4f1