Search Issue Tracker
Fixed in 4.5.5
Votes
23
Found in
4.5.0f6
Issue ID
616918
Regression
Yes
[iOS] "Application.Integrate Assets in Background" is taking up more time
Build and run project for iOS and check the time of Loading.UpdatePreloading->Application.Integrate Assets in the Unity profiler. Notice that the time is longer, compared to older versions of Unity
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
- Changing the Visual Element size moves it when two visual elements are close to each other
- Open Reference for Default Style Sheet asset redirects to missing page
- Undoing changes to Default Style Sheet does not show change until editor refresh
- TextMeshPro Caret has an active raycast when TMP_InputField is non-interactable
- Shadows do not smoothly fade in when transitioning between real-time shadows and baked distance shadows
OanhDvan
Nov 10, 2018 13:18
This problem still exists on version 2018.2.14f1 @@
HalversonS
Jul 31, 2017 12:19
This is happening again in 2017.1. 60% of the time when the first scene load occurs. Pauses for 20 seconds. Hangs up at EarlyUpdate.UpdatePreloading.... Just updated from 5.6.0f3 where this was never happening.
trueDemetri
May 17, 2017 11:50
Problem is still here in Unity 5.5.2
SBArtoons
Jan 28, 2017 05:57
I am still experiencing this problem with 5.4.3f1.When is this going to be fixed in Android and iOS.
muheydari
Nov 09, 2016 19:44
My game is suffering this issue in unity 5.3.4f1.
tayl0r
Apr 08, 2016 19:46
Also getting this in Android on Unity 5.2.2p4. 330 ms!
scottlaforge
Mar 14, 2016 19:02
I'm experiencing this in 5.2.3 as well. I seen in other posts that the issue is fixed "by design." Can someone inform me of how I can correct these in my design?
Wrymnn
Feb 29, 2016 17:10
Problem still occurs in 5.3.2. That is really making huge spikes. Why did you mark it as fixed?!
MooseMouse
Feb 11, 2016 16:28
I am still experiencing this problem with 5.3.2p3
LacunaCorp
Jan 12, 2016 19:30
This is not fixed. Still persists in 5.2+ and is causing 2200ms spike for us.