MobileNativeFoundation / MobileNativeFoundation/Kronos
Invalid timeIntervalSince1970 date
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 699
- Forks
- 100
- PR merge metrics
- No merged PRs in 30d
Description
We are using Kronos like this
let time = String(Int(Clock.now?.timeIntervalSince1970 ?? Date().timeIntervalSince1970))
And sometimes we are getting an error because Clock.now?.timeIntervalSince1970 can give incorrect time (sometimes even in days).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Clock.now entry point and its timeIntervalSince1970 value, then investigate how Kronos obtains and adjusts the current time. Reproduce the discrepancy, identify the source of the incorrect timestamps, and verify that the reported date remains accurate across the affected conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100