SmartTree
SmartTree

Reputation: 1471

UIDatePicker returns wrong date (-1 day to the real date)

I have a UIDatePicker mm/dd/yy. It works fine, but there is one problem: I set minimum and maximum date to it, and when user tries to choose the forbidden day, month or year, the [datePicker date] property begins working wrong. It returns you the current day - 1 or current month - 1 or current year - 1. I added some pictures, so you can see the situation.

Correct date This is correct
wrong date This is wrong (After choosing the forbidden date)

Does somebody know, how can I fix this ? Thanks !

UPD: Code

[self.myDatePicker setMinimumDate:[NSDate date]];
[self.myDatePicker setMaximumDate:[[NSDate date] addTimeInterval:2 * 365.25 * 24 * 60 * 60]]; // to get upto 5 years
NSDate * now = [[NSDate alloc] init];
[self.myDatePicker setDate: now animated: YES];

self.myDatePicker.timeZone = [NSTimeZone localTimeZone];
self.myDatePicker.calendar = [NSCalendar currentCalendar];

Upvotes: 13

Views: 10865

Answers (10)

Arslan Kaleem
Arslan Kaleem

Reputation: 1608

For me this problem is resolved by adding this line

datePicker.date.addingTimeInterval(TimeInterval(TimeZone.current.secondsFromGMT()))

This line adds up the seconds in dateTime of UIDatePicker and dateTime will be equal to current dateTime

Upvotes: 0

Arundev
Arundev

Reputation: 1934

Just add one line of code for setting your timezone.

self.datePicker.timeZone = [NSTimeZone timeZoneForSecondsFromGMT:0];

0 is for GMT 00 . Add according to your time zone.

Upvotes: 14

Wimukthi Rajapaksha
Wimukthi Rajapaksha

Reputation: 1019

Try this,

let formatter = DateFormatter()
formatter.dateFormat = "yyyy-MM-dd"
formatter.string(from: yourPicker.date)

Upvotes: 1

Apoorv
Apoorv

Reputation: 1

It does not return wrong date. What actually happens is, when you select a so called forbidden date, the date picker gets reset to maximum or minimum allowed date with first moment of the day i.e 12:00AM.

So if you are at a place where time zone is for example, 2 hours ahead of GMT, the date returned by date picker will be yesterday's 10:00PM GMT. So here, you might think it is returning yesterday's date but if you convert it to your time zone, you will get today's date only but time component will be 12:00AM.

Upvotes: -2

João Nunes
João Nunes

Reputation: 3761

My solution was to set the returned date to 12:00 AM as NSDates work in UTC

NSDate * adjustedDate = [[NSCalendar currentCalendar] dateBySettingHour:12 minute:0 second:0 ofDate:sender.date options:0];

Also for date calculations you shoud use NSCalender methods and not addTimeInterval

Upvotes: 6

Jim Clermonts
Jim Clermonts

Reputation: 2660

Boolean futureevent;
- (void)viewDidLoad
{
 futureevent = false;
}

int intervall = (int) [currentdate timeIntervalSinceDate: datePicker.date] / 60;

if (intervall < 1200 && intervall > 0)
{
    futureevent = true;
    NSDate *newDate1 = [datePicker.date dateByAddingTimeInterval:60*60*24*1];
    birthdate = [newDate1.description substringToIndex:spaceRange.location];
}
else
{
    if (futureevent)
    {
        NSDate *newDate1 = [datePicker.date dateByAddingTimeInterval:60*60*24*1];
        birthdate = [newDate1.description substringToIndex:spaceRange.location];
    }
    else
    {
        birthdate = [datePicker.date.description substringToIndex:spaceRange.location];
    }
}

Upvotes: -1

Vladimir Shutyuk
Vladimir Shutyuk

Reputation: 2976

I ran into the same trouble and this is what i derived:

Don't use [date description] to check NSDate if you want correct representation for your system. Use NSDateFormatter, because it shows date based on your system preferences (in simulator it will be simulators preferences).

For example:

NSDateFormatter *df = [[NSDateFormatter alloc] init];
[df setDateStyle:NSDateFormatterShortStyle];
[df setTimeStyle:NSDateFormatterNoStyle];
NSLog(@"date for locale is %@", [df stringFromDate:date]);

Upvotes: 1

vikingosegundo
vikingosegundo

Reputation: 52227

It is deffinately something with the timezones and/or Daylight Saving Times. But it must be very subtle, as the code looks fine (beside the interval). Now to my question about if you are in russia:

This year the Kremlin did several back and forth swings on keeping daylight saving times forever. Actually I am not sure, what they decided at last. But maybe it isnt reflected correctly in Cocoa. The the video WWDC 2011 Video "Session 117 - Performing Calendar Calculations" , the presenter even mentions that things like that can happen.

Please try to work with dates with manually set times to noon, as this would keep you out of such mess.


The world just saw a similar misbehavior in iOS 6: the DND-Always-Active bug. I bet this was for a wrong date format (YYYY instead of yyyy)


Also try to set the timezone property on the picker at the very first thing and assign a manually instantiated Gregorian calendar to it.

Upvotes: 5

AlexWien
AlexWien

Reputation: 28727

Check if you use the wrong formatting symbols with big letters: "YYYY". Replace them with "yyyy".

Upvotes: 5

Anoop Vaidya
Anoop Vaidya

Reputation: 46543

Might be due to TimeZone...

Set your time zone.

Upvotes: 0

Related Questions