CloudPull 2.5.2 is now available through this web site and through the in-app software update mechanism. This update has also been submitted to the Mac App Store and will be available there as soon as possible.

This update contains the following changes:

  • Fixed a bug that, in certain cases, resulted in events being excluded from calendar backup files.
  • Added the ability to back up responses from legacy forms on Google Drive. Responses from newer forms are only backed up if those responses are stored in a Google Drive spreadsheet.
  • Made the username field in the login web view editable.
  • Fixed a cosmetic bug with a progress indicator when running under Mavericks.
  • Improved the performance of updating the list of mail labels that should be backed up for an account.

Notes about the Calendar Event Fix

In CloudPull 2.5, I inadvertently introduced an egregious bug where calendar events found during the first backup of a calendar would be excluded when writing newer versions of that calendar if it had more than 250 events. I want to apologize for this bug. Please know that I take the integrity of backup data very seriously.

During the first backup cycle after applying this update, CloudPull will create a new backup of all of your calendars to ensure that your current Google Calendar backup files have all of their events.

Notes about the fix involving Legacy Form Responses

If you create a Form on Google Drive today, it will allow you to send the responses to a Google Spreadsheet. If you choose to do that, CloudPull will back up the responses in the process of backing up that spreadsheet. If you choose not to do that, CloudPull will be unable to back up the responses to that form.

Some older legacy forms do not allow you to send responses to a Google Spreadsheet. This update allows CloudPull to back up responses to these older forms. Please email me at if you have any questions about this.