Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.3.23f1
2022.2.16f1
2023.1.0b13
2023.2.0a11
Issue ID
UUM-33431
Regression
No
Addressables take longer to load when using Safari
How to reproduce:
1. Change the Default Browser of your OS into anything other than “Safari”
2. Open the user-attached “resourcesVsAddressables.zip” project
3. Open the Build Settings window (File → Build Settings)
4. Add the “SampleScene” Scene to the Scenes In Build section
5. Build and Run for the WebGL platform
6. Observe the Addressables logs in the console of the WebGL build
7. Copy the URL of the Build into “Safari”
8. Observe the Addressables logs in the console of the “Safari” Web Browser
Expected result: No change/difference in time spent loading
Actual result: Addressables take longer to load in the “Safari” Web Browser
Reproducible with: 2021.3.23f1, 2022.2.16f1, 2023.1.0b13, 2023.2.0a11
Couldn’t test with: 2020.3.27f1 (Build fails constantly)
Reproduced on: macOS Ventura 13.1 (Intel) using Firefox and Chrome
Note: If the build is not succeeding, change the Compression Format to anything else other than Brotli - Related to a Bug: IN-35805
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 when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
No abnormalities in Unity's behavior was found. Recommend raising an issue to Safari regarding their performance vs Chrome.