NSDate date method returns wrong result

Question

I know there is a lot of questions of this type, but I did't find solution for my case; I need to get current and correct NSDate object, not NSString! This code returns wrong time (+3 hours), because I'm from Ukraine.

NSDate *currentDate = [NSDate date];

How to get current NSDate object from NSDateFormatter? I know only how to get NSString, but I don't need it.

EDIT: I'm using this code to compare 2 NSDates using NSCalendar object, here is code:

NSCalendar *calendar = [NSCalendar currentCalendar];
NSUInteger unitFlags = NSDayCalendarUnit | NSHourCalendarUnit | NSMinuteCalendarUnit | NSSecondCalendarUnit;
NSDateComponents *components = [calendar components:unitFlags fromDate:nowDate toDate:endDate options:0];

and components.hour shows me +3 hours difference

for test purposes you could setup your change the timezone of your mac to london to see, that the difference will be gone (or maybe 1 due to daylight saving time) in your simulator — vikingosegundo, Jul 12 '12 at 15:10

vikingosegundo · Accepted Answer · 2012-07-12T18:15:21.943

NSDates are always stored in UTC, actually the dates itselfs dont know anything about timezones or weeks, month, years. They are just a point in time.

To see the correct time for your position on the earth surface, you need to take the NSCalendar, that represents your time model in account. You could use it directly and mess around with your dates, or create a NSDateFormatter that will leave the dates untouched but adjust their appearence to your needs.

NSDateFormatter *formatter = [[NSDateFormatter alloc] init];
[formatter setDateStyle:NSDateFormatterFullStyle];
[formatter setTimeStyle:NSDateFormatterFullStyle];

NSLog(@"%@", [formatter stringFromDate: date1]);

results in

Thursday, July 12, 2012, 4:36:07 PM Central European Summer Time

in response to the comment:

try this code as test

NSDate *now = [NSDate date];
NSDate *startOfToday = nil;
NSDate *startOfThisWeek = nil;
NSDate *startOfThisMonth = nil;
NSDate *startOfThisYear = nil;
[[NSCalendar currentCalendar] rangeOfUnit:NSDayCalendarUnit startDate:&startOfToday interval:NULL forDate:now];
[[NSCalendar currentCalendar] rangeOfUnit:NSWeekCalendarUnit startDate:&startOfThisWeek interval:NULL forDate:now];
[[NSCalendar currentCalendar] rangeOfUnit:NSMonthCalendarUnit startDate:&startOfThisMonth interval:NULL forDate:now];
[[NSCalendar currentCalendar] rangeOfUnit:NSYearCalendarUnit startDate:&startOfThisYear interval:NULL forDate:now];

NSDateFormatter *formatter = [[NSDateFormatter alloc] init];
[formatter setDateStyle:NSDateFormatterFullStyle];
[formatter setTimeStyle:NSDateFormatterFullStyle];

NSLog(@"%@", now);
NSLog(@"%@", [formatter stringFromDate:now]);

NSLog(@"%@", startOfToday);
NSLog(@"%@", [formatter stringFromDate:startOfToday]);

NSLog(@"%@", startOfThisWeek);
NSLog(@"%@", [formatter stringFromDate:startOfThisWeek]);

NSLog(@"%@", startOfThisMonth);
NSLog(@"%@", [formatter stringFromDate:startOfThisMonth]);

NSLog(@"%@", startOfThisYear);
NSLog(@"%@", [formatter stringFromDate:startOfThisYear]);

you will realize, that the start of the day, week, month and year will be adjusted to your local time, as the first of each NSLog-pair will give you the date in UTC and the second in your local time zone.

on the chat you posted this code

NSDateFormatter *dateFormat = [[NSDateFormatter alloc] init]; 
[dateFormat setDateFormat:@"yyyy-MM-dd HH:mm"]; 
[dateFormat setTimeZone:[NSTimeZone timeZoneForSecondsFromGMT:0]]; 
NSDate *date = [dateFormat dateFromString:dateString]; 
[dateFormat release];

so the problem is, that the datestring is actually not from GMT, but EET (Eastern European Time)

try

[dateFormat setTimeZone:[NSTimeZone timeZoneWithAbbreviation:@"EET"]];

but the by far most elegant solution would be to get the datestring with the offset to UTC, similar to 2012-07-12 12:23:00 +0300if some how possible.
In such an case you could parse it with
[dateFormat setDateFormat:@"yyyy-mm-dd HH:mm:ss Z"]; and don't need further time zone handling, as the formatter knows the offset via the Z-specifier.
Also note, that if you don't set any timezone, the device's current should be used. If the user is always in the same timezone as the time from the date string, this should work, too. But if the user leaves that zone, or you inted to have it working world wide, you should use one of the solutions I gave you. With the second (specifying the timezone with-in the datestring) as the preferred one.

But they give me wrong time when I get components.hour from NSDateComponents :) — Timur Mustafaev, Jul 12 '12 at 15:13
BTW: you should not compare dates by it's components, but by the NSDate compare method — vikingosegundo, Jul 12 '12 at 15:17
I don't need to compare, I need to now how much time is left from now, to endDate :) — Timur Mustafaev, Jul 12 '12 at 15:18
Is it possible, that you create the both dates differently? one with taking the timezone in account and one without? pleas add these code to your question. — vikingosegundo, Jul 12 '12 at 15:24
let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/13796/discussion-between-timur-mustafaev-and-vikingosegundo) — Timur Mustafaev, Jul 12 '12 at 15:27
no, sorry, I have to go. please add the date creation codes to your questions, as I think, that they are created in different timezones. — vikingosegundo, Jul 12 '12 at 15:29

score 2 · Answer 2 · edited May 23 '17 at 12:00

2

The date probably has the correct value; perhaps you think it's incorrect because it looks wrong when you log it? This is because when you log it, it shows the date in UTC. You can get the string in your local timezone by using an NSDateFormatter.

edited May 23 '17 at 12:00

Community

1
1

answered Jul 12 '12 at 14:48

Jesse Rusak

56,530
12
101
102

1

It is also possible that the timezone of the device (or simulator) is set incorrectly, and thus returning an "incorrect" time – Dan F Jul 12 '12 at 14:53
Please, look at Edited code, what can you say now? Problem is not it device or simulator – Timur Mustafaev Jul 12 '12 at 14:58
Well, what are nowDate and endDate? – Jesse Rusak Jul 12 '12 at 15:01
Now date:(18:04) by my time, and End time is 2012-08-15 00:00 – Timur Mustafaev Jul 12 '12 at 15:05

JeremyP · Answer 3 · 2012-07-12T15:41:52.037

The answer is correct if the second date is in UTC. The Ukraine is currently 3 hours ahead of UTC so midnight UTC is at 21:00 in the Ukraine. 21:00 - 18:00 is 3 hours. So check how you are obtaining the second date. The wrong time zone is probably being specified for it.

If the first date really was created at 18:00 Ukraine time via

nowDate = [NSDate date];

then the second date really is 21:00 Ukraine time which corresponds to midnight UTC. Since you claim it is midnight, you must have used UTC to create it from a string - either implicitly or explicitly. Show us how you created it.

** EDIT **

The code you gave me on chat is this:

NSDateFormatter *dateFormat = [[NSDateFormatter alloc] init]; 
[dateFormat setDateFormat:@"yyyy-MM-dd HH:mm"]; 
[dateFormat setTimeZone:[NSTimeZone timeZoneForSecondsFromGMT:0]]; 
NSDate *date = [dateFormat dateFromString:dateString]; 
[dateFormat release];

The third line sets the time zone to GMT which is identical to UTC for all intents and purposes. Your date formatter is probably initialised to the correct locale for the device and so probably you can just leave that line out.

@Timur `NSDates` don't have time zones. They are always in UTC so when you created it, from a string say, you either specified UTC or implicitly specified UTC. — JeremyP, Jul 12 '12 at 15:20
Second date I've got from NSString using NSDateFormatter, please, lets speak here http://chat.stackoverflow.com/rooms/13796/discussion-between-timur-mustafaev-and-vikingosegundo , I'll show you code — Timur Mustafaev, Jul 12 '12 at 15:29

NSDate date method returns wrong result

3 Answers3

Linked

Related