Skip navigation

.tmp files in ~/Library/Calendars/Calendar Sync Changes?

2644 Views 18 Replies Latest reply: Sep 2, 2013 2:08 PM by carlager RSS
1 2 Previous Next
G. L. Gray Calculating status...
Currently Being Moderated
Feb 29, 2012 1:51 PM



I noticed recently that huge numbers of .tmp files in:


~/Library/Calendars/Calendar Sync Changes?


were getting backed up. They have names like D2AAF5C6-0C3A-449E-8A59-0D8FBA29AA28.tmp. Last night when I looked in that folder, there were almost 370,000 of these files. While I have deleted them (it took a long time!) and have not noticed any adverse affects in iCal, I am noticing that something is generating 7 or 8 of these files every hour. Since last night, there are 118 of these files in there. Here is that the contents of one of these files looks like:


<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "">

<plist version="1.0">




























I don't recall seeing this before (I am running OS X 10.7.3). Does anyone know what might be causing these files to be generated and what I can do to stop them from being generated? Finally, I should add that iCal feels much faster since deleting these numerous tmp files.


Thank you.

2.66 GHz MacBook Pro (Core i7), 8GB RAM, Mac OS X (10.7), 16GB iPhone 4, Mac mini HTPC, 2TB Time Capsule, 64GB iPad
  • edsjo Calculating status...

    I have the same problem. As I use iCloud I did the following to see if it helped: a) stopped iCloud syncing (deleting the local calendars), b) threw away the ~/Library/Calendars folder and c) started up iCloud syncing again. I now have all the calendars back, but the Calendar Sync Changes folder has already started filling up again. By looking at the dates of these temporary files, they date back to Feb. 2, which I think is the same date as I updated to Mac OS X 10.7.3. My guess is that it came with that update. Hopefully Apple will submit a fix shortly.

  • Jonnygreen65 Calculating status...

    I've also had the same problem.

    I only noticed it because my Super Duper backup kept hanging.

    I ran all sorts of disk scans in case the HD was faulty, but noticed a Disk Warrier log stating I had more than 100,000 files in the Calendar Sync Changes folder.

    When I looked I had more than 1.5 MILLION!

    It took me a few hours to delete using Terminal and I too now have an Automator Workflow set up to delete them

    I noticed when I opened iCal that it generated about 30 .tmp files every minute that it was open, nothing when I shut it down.

    Hopefully this will get fixed but maybe Apple don't even know about it?

  • edsjo Level 1 Level 1 (0 points)

    I only had 517 000 files so you win! Anyway, I have submitted a bug report to Apple, not that I know if it helps. Are your problems correlated to the 10.7.3 upgrade? 10.7.3 was released Feb 1 and I am pretty sure I updated the day after, which is the same day these .tmp files started appearing.

  • Jonnygreen65 Level 1 Level 1 (0 points)

    I'm afraid I can't be certain when my problem started.

    It's quite possible it's since the update but I've only just found the problem


  • Jonnygreen65 Level 1 Level 1 (0 points)

    Anybody syncing to Google calendars through iCal? (I am)

    Just wondering if the problem is coming from there?

  • John Agapitos Calculating status...

    I also have this problem with about 15 users out of 30 on our network.  I'm on 10.6.8 with home directories on an xserve.  I have to clear about 50,000 files a week as it also creates a slow network.


    There seems to be a problem with iCal not deleting the tmp files after a refresh of each calendar.  I have created a new user account and the problem still exists.


    I hope someone out there can tell us why this is happening.

  • jgmarcel Calculating status...

    Today I remembered to check the total space occupied by my .tmp files in “~/Library/Calendars/Calendar Sync Changes” and, to my surprise and delight, they are all gone! The command “find ~/Library/Calendars/Calendar\ Sync\ Changes -name '*.tmp'” returned absolutely nothing and the said directory is completely empty. Maybe it was fixed by the recent 10.7.4 update? Has anyone else observed the same phenomenon? Thank you all!

  • jgmarcel Level 1 Level 1 (5 points)

    Great! Thanks for your input, G. L. Gray. Well done, Apple! ;-)

  • edsjo Level 1 Level 1 (0 points)



    It definitely seems to be fixed in 10.7.4. I checked on one of my machines where ~/Library/Calendars/Calendar Sync Changes had filled up quite a bit. After the update to 10.7.4, when i launched iCal, all the files were removed and no new ones seem to be accumulating.



  • John Agapitos Level 1 Level 1 (20 points)

    Still a problem with 10.6.8.  Does anyone know what Apple did to fix it.  I would love it fixed in 10.6.8 as we are not planning to upgrade until next year

  • Jeff Bailey Calculating status...

    Holy mackeral!  I stumbled upon this thread while searching for cause for my marathon Time Machine backups.  The log files indicated some 88K-92K files were being backed up, and I had no idea where they were.  Now that I've excluded ~/Library/Calendars/Calendar Sync Changes from my TM backups all is well again.  I'm syncing with Google calendars, so I suspect that's messing something up.  I like the brute force method of emptying the directory daily.



  • Clint Davis Calculating status...

    I'm seeing this issue on a MacBook Pro that's only 18 months old. I did a clean install of Mountain Lion, and it's still happening. My calendar syncs to our OS X Calendar Server. It also syncs to iCloud for my iPhone.

1 2 Previous Next


More Like This

  • Retrieving data ...

Bookmarked By (1)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.