11 Replies Latest reply: Apr 3, 2009 9:27 PM by stopthegears1
Stefaan Top Level 1 Level 1
I've encountered since the end of june a weird behavior in ICal. Every time I start up the ICal application, it shows again previously accepted invitations as notifications. Also at start up of the application my calendar keeps returning to the week of June 23, 08, which is, I suspect, the week this problem first showed up.

I get invitations from people using various applications such as ICal, Outlook and Notes, and the returning notifications do not discriminate amongst the application origin of invitations.

Suspecting it could be a MobileMe problem, I've reset the synchronized data from my MacBook Pro to MobileMe, but it didn't fix the problem.

As the list of returning notifications keeps growing, I would really like to resolve this


Macbook Pro, Mac OS X (10.5.4)
  • JanVolendam Level 1 Level 1
    Same here! It looks as if the oldest notification triggers the date at which the calendar is opened.
  • Matthias Kurwig Level 1 Level 1
    I have the same problem. Did you by any chance find a solution?
  • Súbastien Rezzonico Level 1 Level 1
    same here... have now more than 10 invits coming back when iCal is launched !
  • rudi76 Level 1 Level 1
    I also have this issue. any chance you found a solution.
  • Jeff Shaw1 Level 1 Level 1
    Same issue here. Very frustrating.

    You'd think Apple would know how to make a functional calendar application.
  • hibiscusjlb Level 1 Level 1
    My wife has a G4 Mac mini with Mac OS X 10.5.4. Since June 18th,
    whenever she adds an event and closes iCal, the event is lost upon
    iCal reopening.
    If I invite her to an event and she receives my email invitation, she
    clicks on the event and this opens her iCal, adds the event at the
    proper date. She accepts my invitation and closes iCal. When she opens
    it again, the event is there but it is not accepted (in grey) and the
    notification menu shows the event to be accepted.
    If she creates a new event, invites me and closes iCal, iCal forgets
    about this new event. It appears no where. If I accept the event, she
    receives the notification but there is no event on her calendar.

    Solutions tried: trash ical.plist files, restore previous calendar
    (many trials), restart the computer, repair the autorisations. Nothing
    So I tried to create a new account on her computer under System
    preferences/accounts. This account works OK with iCal. it accepts new
    events and records them, it also accepts invitations and records

    So, I think that the problem may be with some preference file or the
    calendars themselves, (she uses only two calendars).

    Thanks, Jean-Luc
  • Craig Temple Level 1 Level 1
    I've had this identical issue since mid-October 2008. After searching numerous times for the solution, I got fed up and did some serious digging.

    Fortunately, I've figured out the solution:


    Stuck with a notification that keeps coming back like the proverbial bad penny?

    Step 1: Quit iCal

    Step 2: Locate and delete the offending notification in ~/Library/Caches/com.apple.iCal/Incoming/

    Step 3: Open iCal and sigh in relief as the notification is gone for good.

    Hope that helps,
  • Robo24 Level 1 Level 1
    I have been frustrated by this same issue and thanks to Craig, it is now resolved! Thanks again.
  • bradeldridge Level 1 Level 1
    *THANK YOU!*
  • dsc.ng Level 1 Level 1
    Thanks for the posted solution to this problem which I've had for some months.

    I have since also worked out how I can replicate this problem consistently on my Mac. Each time I receive an invitation via e-mail (specifically from Lotus Notes, although I'm not certain the source of the invitation matters), but my iCal is not already launched, the mime attachments and .ics files persist in the relevant cache folder, causing the notifications to re-appear when I quit and re-launch iCal.

    Perhaps others might like to test this out on their own setups and see if you too can consistently replicate the problem. That might help Apple work on a permanent, systemic fix to this issue.

  • stopthegears1 Level 1 Level 1
    THANKS!!!! I love the way you presented it.