You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the first screenshot is the dates being handled by iOS 11. The second screenshot is the dates being handles by iOS 10.
First, there is a row where the exact timestamps pulled from parse are printed, then a row showing what happens to the timestamps after .endOfDay is called and then I try to calculate the number of days between the two dates.
`
if let start = self.transaction.pickupDate{
if let end = self.transaction.returnDate{
print("start date: \(start), end date: \(end)")
let days = abs(end.endOfDay.daysFrom(start.endOfDay))
print("Start Date: \(start.endOfDay), End Date: \(end.endOfDay), number of days: \(days)")
}
}
`
You can see clearly that endOfDay is doing something really weird in iOS 11
endOfDay might be from an older version of Timepiece that I have. But basically, it does the following: return change(hour: 23, minute: 59, second: 59)
The text was updated successfully, but these errors were encountered:
the first screenshot is the dates being handled by iOS 11. The second screenshot is the dates being handles by iOS 10.
First, there is a row where the exact timestamps pulled from parse are printed, then a row showing what happens to the timestamps after .endOfDay is called and then I try to calculate the number of days between the two dates.
`
`
You can see clearly that endOfDay is doing something really weird in iOS 11
endOfDay might be from an older version of Timepiece that I have. But basically, it does the following: return change(hour: 23, minute: 59, second: 59)
The text was updated successfully, but these errors were encountered: