Q: new entries revert to "new event"

Hi,

I'm having the same issues. Tried "BusyCal" for a few days now and it's perfect.

I also had problems with answering iCloud invitations with Calendar for Mac. No problem with BusyCal.

It has all the same functions (and more) as Calendar and you can try it 30 days for free.

http://www.busymac.com/

Even if Apple fixes the bug, I won't change back. Best solution so far for me.

I have been watching this discussion with great interest. I have the problem with Mavericks and I have reported it and tried everything suggested.

My question is can those that converted to BusyCal, confirm that the problem has really gone?

I ask because it might be an iCloud syncing bug and not an iCal bug...

Thanks for helping!

I've been using BusyCal for two weeks. No problems so far and everything I enter into it migrates directly into iCal.

Hope this helps.

I have 4 iCloud calendars, 1 local calendar, 2 shared iCloud calendars and 1 subscription. Everything is working fine in BusyCal.

BusyCal uses the iCloud login, so I think the problem is the iCloud implementation in Mavericks' "Calendar".

Jake and Anma are correct - this bulldozes over this problem as a solution (BusyCal).

*There are a number of different 3rd party apps that can use iCloud to sync (and not just calendars). So if a problem with them ever DID arise it would be that 3rd Party developer who would be heavily invested in shaking the Apple cage to get it fixed. In other words, you'd have someone on your side. And I tend to think using something like BusyCal would not develop this kind of problem for a few reasons. It is outside software writing itself onto iCloud and does not originate within Apple (which is where the problem we are currently experiencing came from), Apple has a vested interest in letting other apps work nicely with it, stuff like that. You could even set BusyCal up to sync with Exchange or Google Cal so there are 2 backdoors if you ever needed them.

But, three weeks later, no issues whatsoever with BusyCal. (*And the additional capability is actually really nice - really just starting to explore the extra features. See, I really just wanted a calendar that worked!)

Thank you All !!! I am convinced I am switching to BusyCal.

I love Apple engineering and software, but arrogance can sweep into any organization at any time. At least it looks like El Capitan will be a maintenance bug-fixing release. The recent onslaught of new features and architecture changes has raised a crop of bugs in most of their OS's.

Thanks again.

Latest update -- the "New Event" problem has happily (and unexplainedly) stopped for me.  I did/changed absolutely nothing on my end, so Apple must have made a change somewhere.  I am still running OS X 10.9.5 on my Mac Powerbook.

But alas a NEW PROBLEM has now emerged -- when I create or edit *ANY* event (either in the desktop Calendar app or on my iPhone), a few seconds after exiting the event, the START TIME changes to 9am.  Always.  No matter what.  This is for new events, and edits to long-existing ones.  The only solution so far is to wait ... then change the time again.  The second change sticks.

So, you may want to double-check your start times for recently-edited events...

No difference for me. Same problem as originally described. To be frank I would be surprised and even concerned if these bugs spontaneously fixed themselves WITHOUT an appropriate software update.

The time the "new event" defaults back to is the time generated when I first double-click on an empty space in the calendar to create the event... if I modify it - which of course we WILL be doing as the start/end time and descriptive text will need tweaking - then those tweaks are all lost.

As of 1pm EDT today, the calendar problems seem to have disappeared (iMac with 10.10.3). I have tried several test calendar entries and had no problems with loss of description or changing times.

No need for the workaround that I was using (create new entry then quick calendar refresh command, then change from default calendar). 

Lets hope the fix is real and that Apple has fixed the backend problem.

I too found the problem was gone. I am running 10.9.5. But 30 minutes later it returned. I don't know what this means, but be careful about assuming the problem is resolved.

I too am suffering with the new entries reverting to a new event issue and am running 10.9.5 on a mac book pro.

Having read a lot of the previous thread and another one there seem to be various suggestions for what causes it but for me it is when I change the calendar it is assigned to. I don't have any delegations on my calendar and as far as I know it isn't linked to my phone which is android anyway. I do not want to upgrade to yosemite after reading negative reviews and am disappointed if apple won't even consider fixing this bug.

I was just wondering Jake Eagle how you found the problem had gone? (even though it then came back) Did you do anything to fix it or did it just randomly stop for a bit?

Hi Jessica, the problem seemed to go away randomly. I don't know why, but it did return. I continue to use BusyCal as my only safeguard.

Following. The reverts to New Event problem remains. Probably carrying a paper calendar is only safe way.

Still having this problem.  It has not gone away for me.

Still having this problem