Google has announced that on April 20, 2017 they will no longer allow apps to sign-in to Google using embedded browsers known as web-views. Instead, Google will require third-party apps to use a web browser for signing-in.
This affects all third-party apps that use a web-view to sign-in to Google Calendar, including old versions of BusyCal. Specifically, BusyCal 2 will not be compatible with Google Calendar on or after April 20, 2017.
BusyCal 3 supports Google's new OAuth requirements
BusyCal 3 has been updated to support the new Google OAuth requirements. If you have updated to the latest release of BusyCal 3, there is nothing more you need to do and BusyCal will continue syncing with Google Calendar as usual.
BusyCal 2 does not support Google's new OAuth requirements
BusyCal 2 uses the old web-view method to sign-in to Google and will be unable to sync with Google Calendar on or after April 20, 2017. BusyCal 2 users that wish to continue syncing with Google Calendar should upgrade to BusyCal 3.
Please contact us if you have questions.