Email or username:

Password:

Forgot your password?
Top-level
Jørn

@mysk @bert_hubert Why does iOS expose these variables in so much detail? And why should an app see the OS uptime at all?

5 comments
andrewtj

@bert_hubert @jornane @mysk I use OS uptime to make caches behave correctly regardless of system clock changes.

iOS inherited a lot of from the Mac which grew up in more innocent times. The Address Book API is a good example. On the Mac it didn't matter that any app could do what it liked. On iOS within 3 or 4 years apps were abusing it which lead to changes on both platforms.

As it happens the uptime APIs are seeing more scrutiny at the moment:

developer.apple.com/news/?id=z
developer.apple.com/documentat

@bert_hubert @jornane @mysk I use OS uptime to make caches behave correctly regardless of system clock changes.

iOS inherited a lot of from the Mac which grew up in more innocent times. The Address Book API is a good example. On the Mac it didn't matter that any app could do what it liked. On iOS within 3 or 4 years apps were abusing it which lead to changes on both platforms.

Jørn

@andrewtj @bert_hubert @mysk Users don’t change the system clock that often in my experience. Why do you need to be robust against that? Especially since they can reboot their devices, which then also messes with your cache.

andrewtj

@jornane @bert_hubert @mysk Please be a little generous. The user isn't the only thing that changes the system clock and not all caches are persisted.

Tom Lokhorst

@jornane @mysk @bert_hubert The App Store is adding the requirement to specify reasons for using specific APIs that are often used for fingerprinting. Uptime is one of the APIs that won't be allowed without a reason as of Spring 2024. developer.apple.com/documentat

Go Up