new entries revert to "new event"

I too have noticed problem in last few days on my iMac (Mavericks) - seems to be one specific calendar (out of the five I use/share) that refuses to let me directly input a new event without wanting to change the text I input a few seconds later to "New Entry" - it also screws around with the times I select too. Other devices are fine. Tim Cook is not doing it for me I am afraid... we continually see screw-up after screw-up regards iOS releases, for example, and the general contempt towards their customers and software bugs reported by them now exceeds the worst experiences I ever had with Microsoft. Funnily enough I moved over to Apple from Microsoft a couple of years or so ago to escape the very attitude I now experience daily with Apple. The more I scrutinise the Apple marketing strategy without the rose tinted specs on the more horrified I become. Of ALL the things Apple are doing wrong and need to correct most urgently - it is the lack of interest (and appropriate response) to the subject matter being discussed in these very forums.

Suddenly happend on my MBP running 10.9.5 as well. First I thought I was messing up but now I know better. On my MacPro running 10.8.5 no issues with this (yet). The problem is that you can easily forget what you've entered a few hours back.

A glimmer of light. I have just finished a helpful call with an Apple advisor from European Support (based in the Republic of Ireland). After making inward enquires he was able to confirm that Apple Engineers are aware of the issue and are working on a software patch / update to resolve it. His sense was of the matter coming to the attention of Apple Engineering only fairly recently (within a couple of weeks or so). Unsurprisingly he could give no indication of likely time for resolution - I guess we can hope for its inclusion in the next routine OSX updates.

So, fingers crossed!

I'm having this exact same issue too! It is so frustrating. I have several "new events" on my ical that I don't even know what they are in reference to now. I hope this gets fixed!

(I have 10.9.5)

I reported the issue using the link somebody above provided, but in the meantime entering new events into the default calendar works for me. Haven't tried going back and changing the calendar category but this will do just fine for now. I hope that helps some of you too!

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.