Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
0
Found in
2020.3
2020.3.1f1
2021.1
2021.2
Issue ID
1326412
Regression
Yes
[iOS] realTimeSinceStartup and unscaledTime no longer match after locking and unlocking the screen
Steps to reproduce:
1. Open the attached project ("1326412.zip")
2. Build and open in Xcode
3. Deploy to a device
4. Disconnect from Xcode
5. Launch the app if it quit upon disconnecting
6. Lock the screen
7. Unlock the screen
Expected results: realTimeSinceStartup and unscaledTime are still in sync and provide the same values
Actual results: realTimeSinceStartup and unscaledTime are no longer in sync and provide the different values
Reproducible with: 2020.3.4f1, 2021.1.3f1, 2021.2.0a12
Not reproducible with: 2019.4.24f1
Reproducible on:
- iPad 9.7" 6th gen (14.4)
- iPad Air 2 (11.0.3)
- iPhone XR (13.4.1)
- iPhone 8 Plus (12.0)
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 ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a13