BusySync Release Notes

BusySync 2.3.1 (July 24, 2012)

• Supports Mountain Lion Gatekeeper.
• Fixes bug that would cause conflicts to occur when syncing with Google.

BusySync 2.3 (July 27, 2010)

• Fixed Google "cannot delete a cancelled event" syncing error
• Fixed detached event syncing error
• Fixed serial number validation error
• Allow deleted events to be restored on a subscribed calendar
• Other minor bug fixes

BusySync 2.2.9 (March 22, 2010)

• Fixed error when unpublishing a calendar to Google
• Fixed time zone discrepancy when publishing calendars to Google
• Support Google alarms < 5 minutes
• Ignore malformed dates created by other apps that sync with Sync Services
• Other minor bug fixes

BusySync 2.2.8 (Feb. 6, 2010)

• Fixed several crashers
• Added warning dialog when updating if AppTrap is installed
• Other minor changes and bug fixes

BusySync 2.2.7 (Jan. 25, 2010)

• Fixed several Google sync errors

BusySync 2.2.6 (Jan. 6, 2010)

• Improved handling of deleted Google calendar feeds
• Fixed Google "Could not delete entry" sync error
• Improved logging

BusySync 2.2.5 (Dec. 28, 2009)

• Fixed Google sync internal error
• Fixed Google sync error that could cause orphaned calendars
• Fixed Google sync error that displays calendar titles as UIDs
• Improved logging

BusySync 2.2.4 (Dec. 10, 2009)

• Fixed several Snow Leopard syncing bugs.
• Fixed crash caused by Log directory permissions error.
• Fixed crash caused by strings with leading & trailing non-breaking spaces.
• No longer appending [calendar name] to meetings on Snow Leopard.
• Improved email validation for meeting organizers and attendees.
• Fixed Google sync bug that caused calendar titles to display as UIDs.
• Fixed Google 403 errors.
• Fixed Google Location URL bug.
• Fixed Google bug when syncing meetings with no organizer.
• Fixed Google bug when syncing empty email elements.
• Fixed Google "could not update entry" error.

BusySync 2.2.3 (Sep 18, 2009)

• Improved sync error handling on Snow Leopard
• Uses less memory on Snow Leopard
• Fixes several syncing bugs recently introduced on Google Calendar
• Improved detection and deletion of duplicate events and reminders

BusySync 2.2.2 (Aug 26, 2009)

• Supports Mac OS X 10.6 Snow Leopard
• Various bug fixes

BusySync 2.2.1 (Aug 20, 2009)

• Supports database conversion from BusyCal to BusySync (requires BusyCal 1.0b12 or later)
• Repairs malformed and duplicate alarms
• Various syncing bugs fixed
• New eSellerate library

BusySync 2.2 (May 19, 2009)

• Fixed several google syncing bugs.
• Faster iCal syncing.
• Compatibility with forthcoming BusyCal.

BusySync 2.1.9 (December 3, 2008)

• Fixed bug that could cause Alarms to multiply
• Fixed crasher on Tiger
• Fixed bug that could cause calendars to become orphaned on Google
• Fixed bug syncing recurrence exceptions with Google
• Fixed bug syncing with Google Holiday Calendars

BusySync 2.1.8 (October 19, 2008)

• Added support for new Google API for deleting detached recurring events
• Better handling of badly formatted dates in iCal
• Improved error handling and logging

BusySync 2.1.7 (September 14, 2008)

• Fixed Google syncing bugs
• Improved crash recovery on Tiger
• Improved error reporting

BusySync 2.1.6 (August 22, 2008)

• Fixed a crash in Google syncing
• Improved error logging

BusySync 2.1.5 (August 11, 2008)

• Fixed a bug in Add Remote Server that affected German, Japanese, and French versions
• Fixed several Google syncing bugs
• Fixed several crashes
• Improved detection of sync services corruption
• Reduced memory usage

BusySync 2.1.4 (July 7, 2008)

• Fixed a bug that caused the menu bar app to think BusySync was stopped
• Changed Google reminders to map to iCal Message with Sound alarms instead of just plan Message alarms
• Fixed a number of rare crashes in Bonjour and Google syncing
• The "skip this version" button in the Sparkle update dialog should now work correctly

BusySync 2.1.3 (June 30, 2008)

• Google syncing bug fixes
• LAN syncing bug fixes
• Error alert improvements
• Conflict resolver improvements
• Alarm syncing improvements
• Performance improvements
• Improved crash recovery logic
• Menu bar app now shows LAN sync status
• Menu bar app allows you to toggle the "!" warning icon for services that are offline
• Fixed a crash in the register dialog on Japanese systems

BusySync 2.1.2 (June 5, 2008)

• Improved the error reporting system
• Fixed a problem with publishing events older than 1950 to Google
• Fixed a crash when subscribing to a calendar over the LAN

BusySync 2.1.1 (May 30, 2008)

• Fixed bug that would cause BusySync 2.1 to report an error after resetting sync history.

BusySync 2.1 (May 30, 2008)

• BusySync menu bar app, displays current status and Sync Now menu command
• Google date range limit for syncing, solves quota errors and improves performance
• Google syncing improvements and bug fixes
• Time zone bug fixes
• iCal auto-repair improvements
• Alerts for various common errors
• Localized into Spanish (in addition to French, German and Japanese)
• Fixed Google Calendar sync bug related to repeating meetings with attendees.
• Other miscellaneous bug fixes.

BusySync 2.0 (April 17, 2008)

• Ability to sync iCal with Google Calendar
• Option to filter out Alarms and To-Dos from subscribed calendars
• LAN/WAN synching improvements, VPN compatibility, IPv6 and Back to My Mac compatibility
• Auto-repair of damaged iCal databases
• Meeting titles have their source calendar appended in brackets to avoid Conflict Resolver errors
• Fixed bug that caused edits to be lost on Tiger if you moved an event to a different calendar
• Fixed bug where events were deleted if you moved them to a different calendar, then deleted the source calendar
• BusySync will no longer appear to be "not responding" during long syncs
• Added Reset Sync History button to Reset tab
• Fixed a crash involving NSURLConnection
• Improved error logging
• BusySync 2.0 is backwards compatible with other BusySync 1.5 users on your network
• Fixed attendee syncing bug involving recurring events
• Fixed VPN/WAN syncing bug
• Localized 2.0 strings

BusySync 2.0b9 (April 14, 2008)

• Fixed bug that could occur when interrupting a full sync
• Fixed bug involving meetings that get duplicated after resetting sync history
• Fixed bug involving Back to My Mac IPv6 connection errors
• Fixed bug involving Google Captcha dialog that is displayed when wrong email address is entered
• Improved error/status messages and logging
• Miscellaneous UI improvements

BusySync 2.0b8 (April 8, 2008)

• Attendees are no longer synced from iCal to Google. This will prevent Google from creating duplicate shadow events on the Google primary calendar to block your free/busy time. It will also stop Google from sending out email reminders to all attendees 24-hours before an event.
• Message Alarms in iCal can be mapped to either a pop-up, SMS or Email alarm in Google. See Google Settings for more info.
• When subscribing to a calendar via Bonjour, you can remove Alarms and/or To-Dos. See Subscribe Options for more info.
• When events with attendees (meetings) are published via Bonjour, the calendar name is appended to the title in brackets (e.g. "Lunch Meeting [Company Calendar]"). See Scheduling Meetings for more info.
• Fixed various Google syncing bugs.
• Fixed Floating time bugs.

BusySync 2.0b7.1 (March 25, 2008)

• Fixes a bug introduced in 2.0b7 that affects users syncing with a remote server (WAN)

BusySync 2.0b7 (March 21, 2008)

• Calendar colors can now be changed independently between iCal and Google
• Calendar names can be renamed in iCal or Google to be different than the source
• BusySync will now allow you to delete meetings when you are not the Organizer
• Recurrence exceptions are stored in the same fashion as iCal to appease the Conflict Resolver
• Fixed bug that caused edits to be lost on Tiger if you moved an event to a different calendar
• Fixed bug where events were deleted if you moved them to a different calendar, then deleted the source calendar
• Lengthened retry interval for Wide-Area Bonjour failures (Back to My Mac)
• Various Google syncing improvements
• Crash Reports are now captured properly on Leopard
• Fixed rare crash involving NSURLConnection
• Improved error logging

BusySync 2.0b6 (March 10, 2008)

• Improved recovery from Google quota errors
• Fixed bug that could cause Bonjour syncing to fail if Back to My Mac was enabled
• Fixed bug when syncing events to Google that are over 1000 years old
• BusySync will auto-repair events that contain duplicate alarms
• Added a Reset Sync History button to Reset tab
• Improved error logging

BusySync 2.0b5 (Feb. 29, 2008)

• Better handling of Google quota errors. Google limits the amount of data you can sync per calendar per day. If a calendar has exceeded that quota, it will be skipped and syncing will continue with the next calendar.
• BusySync will detect calendars on Google with malformed Titles/UIDs and ignore or recover from them.
• BusySync will no longer appear to hang during its initial sync.
• Line breaks in iCal Notes are retained when syncing with Google.
• Google Privacy settings are retained after editing in iCal.
• iCal detached all-day events will now sync to Google.
• Better handling of events in the Alaska Time Zone (which Google doesn't properly support).
• Unicode characters are stripped from Location field when syncing with Google.
• Fixed bug causing some events to not sync when switching from a WAN to LAN connection.
• Fixed a bug that confused BusySync into seeing duplicate servers when syncing between multiple user accounts on the same mac with Back to My Mac enabled.

BusySync 2.0b4 (Feb. 18, 2008)

• Fixed time zone bugs
• Fixed sync errors involving events with control characters
• Fixed sync errors involving recurring events with degenerate exceptions
• Fixed various recurring event bugs
• Improved error message logging

Warning: This new version will automatically reset your Google Settings. This means, all calendars you are Publishing to Google will be unpublished, and all calendars you are Subscribing to from Google will be unsubscribed. So, you will have to reconfigure your Google Settings after installing this new version.

BusySync 2.0b3 (Feb. 11, 2008)

• Fixed memory leak.
• Event Locations in iCal now sync to Google.
• Display error message in Log tab when Google is experiencing temporary server errors.

BusySync 2.0b2 (Feb. 09, 2008)

• Only meeting attendees with valid email addresses are sync'd with Google Calendar.

BusySync 2.0b1 (Feb. 08, 2008)

• First public beta release with support for Google Calendar syncing.

BusySync 1.5 (Dec. 29, 2007)

• Added WAN support for syncing over the internet.
• Fixed Leopard Firewall bug that caused it to always prompt to Allow incoming connections for BusySync (BusySync is now signed).
• Publisher name defaults to account name, rather than computer name, to work better on a shared computer.
• Set default Publishing port to 4990.
• Register button remains enabled even after registering, in case you need to change your serial number later.
• To-Do URLs are not sync'd if it is a local URL like addressbook:, mailitem:, message:, or file:.

BusySync 1.07 (Dec. 5, 2007)

• Fixed To-Do syncing bugs on Leopard
• Added an alert informing users if they need to perform a Reset to fix Leopard iCal bug
• Fixed Registration dialog bug
• Improved logging and added support for all email clients when sending logs
• Other bug fixes

BusySync 1.06 (Nov. 21, 2007)

• Fixed Alarm syncing bug

BusySync 1.05 (Nov. 20, 2007)

• Fixed Registration bugs
• Reset BusySync button will now reset the Sync Services database as well as the BusySync database (to resolve a Leopard iCal bug)
• Improved logging
• Other bug fixes

BusySync 1.04 (Nov. 10, 2007)

• Added SSL support on Leopard
• Added support for floating event times on Leopard
• Fixed Backup bug on Leopard
• Improved logging
• Other bug fixes

BusySync 1.03 (Oct. 30, 2007)

• Fixed serial number validation bug that affected users running on a shared Mac with multiple user accounts.
• Network copy protection is now per-computer rather than per-user account.
• This version is Leopard compatible (as were the previous versions). The next planned update will add some new Leopard specific features.

BusySync 1.02 (Oct. 25, 2007)

• Fixed a bug that would cause syncing to stop if a sync conflict occurred
• Check for Updates now works even when BusySync is stopped
• French localization fixes

BusySync 1.01 (Oct. 21, 2007)

• Fixed bug in eSellerate Web Store implementation

BusySync 1.0 (Oct. 21, 2007)

• The 30 trial period has been reset
• New integrated eSellerate Web Store, accessible via the Register button
• Fixed a bug that was causing the iCal backups to be named incorrectly
• Reduced the volume of output shown in the Log tab
• Fixed a three-way sync loop between BusySync, iCal, and MissingSync
• Other minor bug fixes

BusySync 1.0b4 (Oct. 13, 2007)

• New icon.
• Localized in French, German, and Japanese thanks to the generous contributions of Stéphane CARRE, Christoph Schmitz, and Yuzuru Shiraiwa.
• Added a subscribe to mailing list option on first launch.
• Fixed a bug in recurring events that occurred when moving a single occurrence of a repeating event and then selecting Undo Detach. The undo wasn't sync'd.
• Fixed a bug in recurring events that affected users in the EST time zone. New York and Sydney both use the same time zone abbreviation of EST, which BusySync was interpreting as New York time and was causing the event to appear at the wrong time if you were in the Sydney Australia time zone.
• Various user interface enhancements.

BusySync 1.0b3 (Oct. 8, 2007)

• Numerous bug fixes and optimizations.
• Leopard compatibility. Plus, Tiger and Leopard users can sync with each other via BusySync.
• You can now rename calendars you are subscribed to. BusySync automatically renames calendars to prevent duplicates. For example, if you have a calendar called "Home" and you subscribe to someone else's calendar also called "Home", BusySync will rename it "Home(2)". You can change that name to something else in iCal, if you wish. Your local name will not be synched over the network.

BusySync 1.0b2 (Oct. 2, 2007)

• BusySync automatically starts when first installed.
• An error is now displayed in the Publish and Subscribe tabs if BusySync is not running.
• Users are now prompted to enter a password when subscribing to a calendar that everyone can read but requires a write password.
• Password dialog responds better to the keyboard (Enter for OK).
• Fixed a bug where Publishers with static port configurations set in Advanced Network Options were not visible to Subscribers.
• Fixed a bug where multiple user accounts on the same machine would not see each other.
• Hooked up the Help icons to point to the appropriate section of the online user's guide.

BusySync 1.0b1 (Sept. 27, 2007)

• First public beta release