Is mach_absolute_time no longer monotonic in iOS13

Our code relies on subsequent calls to 

mach_absolute_time
calls being monotonic, and was working fine until iOS13. After iOS13 it started crashing on the assertion that two reads are monotonic. The crash is more likely to occur after wakeup.


Did anything change in iOS13?

Up vote post of ds;lkfgjsd;lghjld;s Down vote post of ds;lkfgjsd;lghjld;s
432 views
Posted by
ds;lkfgjsd;lghjld;s
Reply
Add a Comment

Replies

Mach absolute time should be monotonic. Maintaining monotonicity in all circumstances is a surprisingly tricky technical challenge, and it seems that something has broken here. I recommend that you file a bug report for this.

Please post your bug number, just for the record.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware 

let myEmail = "eskimo" + "1" + "@apple.com"
Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Add a Comment

Hi, I did open a ticket: FB7383880

Posted by
ds;lkfgjsd;lghjld;s
Up vote reply of ds;lkfgjsd;lghjld;s Down vote reply of ds;lkfgjsd;lghjld;s
Add a Comment