Hi there, I am having the same problem with March 2013 but I found if I removed my contacts I had no problem with viewing as a month. Tough call I guess, lose the contact or a month good luck with finding a solution. Please keep us updated. My issus are with the ipad 3
you gave me an idea : I deleted the display of "my calendar" and of "birthdays" and had no problem viewing March 2013
although I cannot see thebutility of viewing an empty calendar...
Reintroducing the display of either one calendar does reactivate the bug !?
Currently Being ModeratedApr 26, 2012 12:56 AM (in response to Andy Eastwood)
Same problem here in our company with many iPAD's
I love it to ask my co-workers "can you please switch to month view March 2013" and than watch their face
I'm really astonished that Apple seems not to be interested in giving their customers any kind of feedback regarding this serious issue.
I remembered when Google has had a issue with their calendar sync their employees were quite active in several forums in giving updates regarding the upcomin solution and try to offer some workaraounds as a quick solution. Therefore I'm more than happy that I still have my Android phone which shows me a month view for March 2013 .
Let's hope that Apple wakes up and fix this issue or will they maybe really ban March 2013 from all calendars
Ok, I went to the apple store with this issue they told me they had never seen this issue before but we found a way around it. It appears (my issue anyway) was due to birthdates in outlook contacts which were being transferring when the iPad was sync'd.
I transferred my contacts from outlook to windows address book and mapped the sync that way manually adding any birthday information to the iPad and it worked!
Currently Being ModeratedApr 26, 2012 12:59 PM (in response to Andy Eastwood)
I personally transferred my contacts and my calendar to Gmail... It didn't delete the crashing of March 2013 !
Am I correct assuming that you suppressed the birthdays of your contacts before transferring them and added them manually afterwards on the IPad ?
What about next synchronisation ?
I spoke with Apple last night - Dimitris, from Athens. He was extremely patient and we tried a number of things, including a very lengthy reset but, in the end, to no avail. He has now referred the fault to the iCloud engineers, so I'm optimistic of a good outcome. That said, I'm reassured to know that I AM NOT ALONE!!
On a French forum I followed someone's suggestion and found the MIRACULOUS CURE : change the time of your iPad to Cupertino's and... NO MORE BUG !
Very nice for the few users not living in another time zone !
I got rid of this issue by deleting the birthday of one of my contacts on 1st April... following the advice from DEVART, developer of Holiday Calendar app which is copied below :
Yes, this is an iOS issue.
The crash is caused by Apple's iOS.
The reason is the daylight saving time change the weekend before 1 April 2013. This problem affects ALL all-day events on Monday 1st of April.
We reported this bug to Apple, and hopefully they will fix the bug in the Calendar app soon.
Other apps like CalAlarm, miCal, Week Calendar do not suffer from this problem.
Please edit all-day events on 1 April 2013 in the week view. Either remove the event or change the all-day event into an appointment event, starting for example 12.00.
Please try and post your results !
Thanks for the informative post. While this certainly is a work around, it's not easily an option for me since I need to view multiple shared calendars, some of which I cannot edit. Regardless, switching to weekview does resolve the problem.
This issue goes beyond the March 2013 thing, and it also happens on my iPhone. I have several meeting invitations that were sent to me from one of the administrative secretaries, from Outlook, and that I accepted into my iCloud calendar. Some recur, some are one time only. Whenever I try to open any one of them on my iPad or iPhone, in any view, it crashes the calendar app. All of these appointments can be viewed just fine on my Mac. This is a serious bug, and definitely needs to be addressed by Apple. Something tells me it won't be fixed until iOS 6 makes its debut.