Currently Being ModeratedDec 28, 2012 5:04 AM (in response to mistermak)
There is a glitch with the calendar app. Do you have an all day appointment on April 1, 2013? if so, alter it, make it a few hours instead of all day adn March will return.
The calendar app has had issues with April 1 being the start of daylight savings time and the fact that 'all day' can mean anything from 23-25 hours, and this glitch causes March to disappear. Remove 'all day' from the equation, the calendar app is happy again and gives you back the month of March.
Currently Being ModeratedDec 28, 2012 11:20 AM (in response to Skydiver119)
I have removed all day from Easter Monday (which is silly) and from another event. The calendar app still crashed on month view for March 2013. My iPhone has no problem. This is only on the iPad2 iOS6. What times can I use? Apple appear to have been aware of this bug for some time and it is about time it was sorted.
Currently Being ModeratedDec 28, 2012 11:29 AM (in response to Edwin.Dobinson)
Changed start time of both events on the Monday 1 Apr to 02:01 and app no longer crashes. But this is ridiculous. Summer time starts on the Sunday not Monday. The all day event of Easter Sunday is fine.
Currently Being ModeratedJan 8, 2013 2:00 PM (in response to mistermak)
Blimey I thought I was going crazy, on top of everything else another bug, and it's left to us to fix it.....again.
Why on earth do I get suckered in to this expensive game. iPad 4 latest iOS fail. iPhone 5 calendar latest ios working fine.
Thanks goodness for the community!
Currently Being ModeratedJan 9, 2013 4:39 AM (in response to bedslad)
I'm in the same position - 2 friends have birthdays on 1st April. Does that mean I have to remove ALL FB birthday reminders or start unfriending people? There doesn't seem to be an option to remove individual birthdays. Pah!
Currently Being ModeratedJan 10, 2013 1:02 AM (in response to mistermak)
The crash is fixed if I unsubscribe from the holidays calendar. If I do this it allows all day events on April 1st to remain, but crashes once I introduce holiday calendar again. Week view is OK.
Currently Being ModeratedJan 11, 2013 2:47 AM (in response to mistermak)
I understand the bug, and have updated 01 April 2013 events accordingly, but my iPad calendar app is stuck on the March 2013 month view (having 'scrolled' back from April resulting in a crash where it 'stayed').
Consequently, it won't launch, as seems like it can't get far enough started to synch and remove the all-day events that are fixed on iCloud, but not locally yet.
How can I reset the calendar data complete from outside the app, or force it to rebuild from the server?
Currently Being ModeratedJan 13, 2013 8:26 AM (in response to mistermak)
I have tried the solution, but it doesn't work.
This is probably due to the fact that the entries are birthdays (so subscriptions) and invites from co-workers.
Apple, do you have a solution? At this rate I will have no calendar for a whole month!
Currently Being ModeratedJan 23, 2013 4:00 AM (in response to mistermak)
I'm in the same position as some of you, 3 friends have birthdays on 1st April. I do not intend to remove FB birthday reminders or start unfriending people? There doesn't seem to be an option to remove individual birthdays.
Is there any other solution? Thanks.
Currently Being ModeratedJan 23, 2013 5:29 AM (in response to FMorais)
Since you can't edit birthdays, a temp work around could be to simply remove them from your calendar until after april 1. Not perfect, but a way to get march back.
For events you can edit, just make them span a few hours, or even 23 hours, just not all day. That's apparently where the bug is, the program trying to figure out exactly when april 1st starts in the mess that is daylight savings time beginning (which means march 31 is 23 hours in some places, 24 in others)
computers are stupid, they get confused
There are rumors of a fix, but it's just that, rumors. The only sure fire way to 'fix' it right now is to tweak things yourself.
Currently Being ModeratedJan 23, 2013 7:59 AM (in response to Skydiver119)
Surely March 31st causes the problem not April 1st. April 1st starts at midnight on 31st March at which time the the time changes will have taken place. Apple have known about this for some time and still no fix. It is fast becoming an April fool joke.