Search Issue Tracker
By Design
Won't Fix in 2.3.X
By Design in 2.3.X
Votes
1
Found in [Package]
1.22.3
2.3.7
Issue ID
ADDR-3824
Regression
No
Sprite Atlas bundles size is double when built for iOS
Reproduction steps:
1. Open the attached “BugRepro” project
2. In the Build Settings, make sure iOS platform is selected
3. In the Addressables Groups window (Window > Assets Management > Addressables > Groups), build the bundles (Build > New Build > Default Build Script)
4. In the Addressables Reports window (Window > Assets Management > Addressables > Addressables Reports), select the latest report
5. Observe the Totals size of all bundles
6. In the Build Settings, switch to Android platform
7. Repeat steps 3-5
Expected result: The bundle sizes on iOS and Android are the same, or nearly the same
Actual result: The iOS bundles size is double than the Android bundles
Reproducible with: 1.21.19 (2022.3.31f1), 1.22.3 (2022.3.55f1), 2.3.1 (6000.0.32f1, 6000.1.0a8)
Couldn't test with: 1.22.3 (2021.3.57f1) (Addressables content build failure)
Reproducible on: macOS Sequoia 15.1.1, Windows 11 (By user)
Not reproducible on: No other environments tested
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Hi there. This issue seems to have to do with the nature of ASTC compression, not with addressables. ASTC compression is very high quality, but leads to higher sizes on disk compared to ETC compression, which is lower quality, but has a smaller on disk size. You can see the effect of ASTC compression by changing the compression for your IOS app to PVRTC - if you do so, you'll see that in that case the on disk sizes for android vs. IOS are much more similar. (87 MB for android vs. 90 MB for IOS). This is likely the reason for the uncompressed size of all the assets being the same, but the bundle file size (i.e. the compressed size) being much larger for IOS. Closing this ticket as it does not appear to relate to addressables functionality directly.
Resolution Note (2.3.X):
Hi there. This issue seems to have to do with the nature of ASTC compression, not with addressables. ASTC compression is very high quality, but leads to higher sizes on disk compared to ETC compression, which is lower quality, but has a smaller on disk size. You can see the effect of ASTC compression by changing the compression for your IOS app to PVRTC - if you do so, you'll see that in that case the on disk sizes for android vs. IOS are much more similar. (87 MB for android vs. 90 MB for IOS). This is likely the reason for the uncompressed size of all the assets being the same, but the bundle file size (i.e. the compressed size) being much larger for IOS. Closing this ticket as it does not appear to relate to addressables functionality directly.
Resolution Note (2.3.X):
Hi there. This issue seems to have to do with the nature of ASTC compression, not with addressables. ASTC compression is very high quality, but leads to higher sizes on disk compared to ETC compression, which is lower quality, but has a smaller on disk size. You can see the effect of ASTC compression by changing the compression for your IOS app to PVRTC - if you do so, you'll see that in that case the on disk sizes for android vs. IOS are much more similar. (87 MB for android vs. 90 MB for IOS). This is likely the reason for the uncompressed size of all the assets being the same, but the bundle file size (i.e. the compressed size) being much larger for IOS. Closing this ticket as it does not appear to relate to addressables functionality directly.