Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.1.0a11
2023.1.0a19
Issue ID
UUM-19272
Regression
Yes
"Failed to decompress file with brotli, uncompressCodeError” error appears when decompressing files using brotli on mobile devices
How to reproduce:
1. Build And Run the user’s attached project on a mobile device
2. Press the “Start decompress” button
3. Observe the console window
Expected result: Brotli compression works and “<BrotliDecompress>d__3:MoveNext()” is printed
Actual result: Brotli compression doesn’t work and “Failed to decompress file with brotli, uncompressCodeError” is printed
Reproducible with: 2021.2.0a21, 2022.1.0a11, 2023.1.0a17, 2023.1.0a19
Not reproducible with: 2020.3.42f1, 2021.2.0a20, 2022.1.0a12, 2022.1.23f1, 2022.2.0b15
Could not test with: 2023.1.0a16 (button from 2nd step is not visible)
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.0.3 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Samsung Galaxy Z Flip3 5G (SM-F711B), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Samsung Galaxy S22 (SM-S901B), Android 12, CPU: Exynos 2200, GPU: Ltd.
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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note:
Plugins breaking between Unity versions is expected and could happen due to a lot of different reasons, such as SDK upgrades on our side. In this scenario, the plugin needs to be updated accordingly.
Unfortunately, we currently cannot help with figuring out the exact cause due to other priorities.
However, we would be happy to have a closer look in case you find additional information that points to the problem being a bug with Unity.