We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Given I've guess the new spot Then I see the countdown timer But sometimes it will say (e.g.) 23:02 for 2 seconds And then hop to (e.g.) 23:00.
So, the actual time keeping is correct, but the display is not reliably updated.
The text was updated successfully, but these errors were encountered:
Reproduced!
Sorry, something went wrong.
@michaelkirk
I am not sure what the priority of this is.
NSTimer is not meant to be super accurate.
You could try replacing the NSTimer with dispatch_source_create and dispatch_source_set_event_handler - Official Docs.
I would also replace NSDate with CFAbsoluteTimeGetCurrent().
Does this also happen on physical devices? I can't build for devices without credentials.
Looking at this a little more, the delay might be caused by the clear background of the UILabel - view cannot be drawn fast enough.
I tried the CFAbsoluteTimeGetCurrent() and dispatch_source_set_event_handler.
It did not really make a difference. Although the CFAbsolutTimeGetCurrent seems to work a little better with NSTimer.
No branches or pull requests
Given I've guess the new spot
Then I see the countdown timer
But sometimes it will say (e.g.) 23:02 for 2 seconds
And then hop to (e.g.) 23:00.
So, the actual time keeping is correct, but the display is not reliably updated.
The text was updated successfully, but these errors were encountered: