Previous 1 2 Next 18 Replies Latest reply: Feb 21, 2014 2:38 PM by David Canada
tanyafromhamilton Level 1 Level 1

Some of the birthdays on iCal (from Address Book) are wrong. They are out by one day and one year (appearing in iCal one day earlier, and taking one year off the person's age). Deleting the entry and starting again does not work. Error seems to occur for early 1990s. Can anyone help? Problem occurred before upgrading to Lion, and is still there.

iCal, Mac OS X (10.7.2)
  • jonathank63 Level 1 Level 1

    I have the same thing.  Running OSX Lion , started using iCloud (though thats not seemingly implicated) si finally thought I'd rely on address book and ical .... now beginning to regret it.


    As above certain birthdays in Address book show as one day and one year different in iCAL, surely this is basic functionality that Apple should have solve years ago....


    a previous fix suggested was to turn off prefs in Ical to show birthdays , close ical then reopen and re apply the preference.  This worked previously but not now.


    Any thoughts anyone?

  • garyfromtaupo Level 1 Level 1

    I also have this issue. Has anyone found a fix yet?

  • damianfrommadera Level 1 Level 1

    Same problem!

    I have entered birthdays in address feilds, and several of them appear "One day out" in ICal.

    Does not seem to have any logic ie I have dates in 2008 and 1978 and they dont work....

    Look forward to a fix for this....

  • jmg77584 Level 1 Level 1

    I am having the same problem, but only on my iPad 2. My iPhone 4s and iMac do not seem to have the problem.

  • 0815guy Level 1 Level 1

    I have the same issue on my iPhone 4S ( iOS 5.0.1 ).

    My Mac runs Snow Leopard, no iCloud involved.

    Some birthdays are off by one day prior to the real birthday-date !?

    This applies to dates in the past and future.

  • ingoratsdorf Level 1 Level 1



    Same problem with my iPhone 4 iOS 5.0.1.

    To reproduce, I enter a birthday like 02-09-2001. All correct in Apple Address Book on the phone.

    The birthdays are also shown incorrectly on any other 3rd part contact app on the iPhone, like RContacts & ContactsXL. They all show the birthday for 03-09-2001, however if you touch the contact to edit - voila, it shows up as 02-09-2001... weired.


    I then sync to groupware server and the iPhone sends 03-09-2001 for birthday. Of course the birthday is saved incorrectly on the server and once the iPhone has synched back, the birthday magically change to 03-09-2001 on the iPhone.

    When modifying this contact, the birthday is being sent to the groupware server as 04-09-2001.... to be continued.


    This is what is happening using CardDAV:


    Sent by eGroupware to iPhone:




    PRODID:-//EGroupware//NONSGML EGroupware Addressbook 1.8//EN





    changed some NOTES text and iPhone sends it again to eGroupware:




    PRODID:-//EGroupware//NONSGML EGroupware Addressbook 1.8//EN





    When the card was submitted, the iPhone still showed 200-09-02 for birthday and once it saved it and synced it back, guess what:


    Birthday was on 2001-09-03! (Of course, because that's what it sent)


    But why does the iPhone sends the birthday as 2001-09-03???????

    Mind you, only happend for CardDAV sync, activeSync (aka Exchange) works correctly. Maybe Apple have corrected the exchnage bug but have the same still in CardDAV?


    But then why are all 3rd party apps showing the birthday wrong too? Cannot be a sync issue only. I guess it's some internal storage problem that only gets corrected when synching via activeSync.


    And this is repetitive. So EVERY TIME i edit an address on the iPhone, the birthday shifts another day. Drives me crazy!

  • kayp Level 1 Level 1

    I'm posting my same silly idea this a leap year issue? All of my dates after February are shifted by one day

  • enscryprio Level 1 Level 1

    I'm running OSX 10.7.2 on my iMac. In my Address Book, I only enter the day and month; not the year and that seems to work. Otherwise, it just shows up in iCal one day before the date that I have entered in Address Book. The year's not that important anyway although a fix would be handy

  • germanoschilli Level 1 Level 1



    I use a macbookpro, iphone & ipad. I only have this problem for my ipad, the macbook pro & iphone sync fine. I enter all my contacts thru my iphone & here's the fix I found... But before you do kindly back up your contacts and calendars just in case.


    In my ipad I went to settings - icloud - then turned off contacts & calendars - Resetted the ipad - turned it on then went back to settings - icloud then turned on 1st the contacts (because this is where the calendar gets the info) after my contacts synced. I then went on to again settings - icloud - then turned on the calendars. After syncing calendars all info was on the right place.


    Hope this helps - if it does you can choose to like our business fan page which were trying to build.  -

  • ingoratsdorf Level 1 Level 1

    Nope, has nothing to do with iCloud. Not using it at all.

    I have come to the conclusion that this is a time zone issue.


    My very strong suspicion is that iOs saves the birthday internally as a DateTime structure, not a date. This causes all sorts of issues.

    No available software supports times for birthdays, not even Apple. Although a nice idea for future proofing, it needs a but if understanding of how date times and times zones work.

    Since in no available software a time with times on for a birthday can be specified, the time would have to be interpreted as UTC. However, Apple seems to be interpreting it as local time zone, which makes no sense whatsoever.


    The following scenario happens:


    User A In UTC+12 enters birthday, say 1973-11-01.

    IOs receives the date and interprets it as local time zone and therefore converts it into 1973-11-01 00:00:00 +12.

    When birthdays are synched via CalDav, only dates are supported and the whole things gets converted to UTC, therefore into 1973-10-31 12:00:00 and then shortened to a date only, ie 1973-10-31.


    The same would happen with any time zone with an offset more than 0, time zones with an offset <0 are fine, since offsets are added and deleted again, all within the same day. Since the US, where Apples developers are sitting, is <0, no one ever noticed this issue...


    Does that make sense?


    The fix is extremely simple: Interpret the date as UTC and no offsets will be added or deleted and the date stays the same.

    I recently fixed the same bug in a groupware called Tine20. Exactly the same symptoms. Hope they have committed that fix........


    So please Apple, spare half an hour of one of your devs and get this issue fixed.




  • craigos3 Level 1 Level 1

    My only work around so far has been to edit the dates that are wrong, removing the year in Contacts. This then changes the entry in iCal to the right date. I had thought it was only birthdays in the 70's but some are still right. Hopefully someone or Apple figures it out.

  • Tazyas Level 1 Level 1

    I have that too, only with some people. I find that if I don't put the year in, it's OK. Odd. If someone has a solution for this please post.

  • rickyv Level 2 Level 2

    I have this problem too only in iCal.  My calendars on my iCloud, iPhone and iPad show the correct birthdays.  On iCal, some birthdays are late by one day.


    It puzzles me that this problem has been with iCal for two years, based on the dates on this thread.


    I hope Apple does something about this.  For now, I am using Busycal as a replacement application for iCal.  It syncs birthdays correctly with Address Book.  Just make sure you don't turn on the birthday subscription option because that one syncs with the incorrect birthday entries on iCal.

Previous 1 2 Next