On first launch you will be prompted to enter your Google OAuth credentials so the app can access your Google Calendar. The app will walk you through these steps.
You can also review the setup instructions here: https://github.com/jevdemon/flip2calendar/blob/main/README.md#installation
What's New in v1.1.2
Performance improvements, risk mitigation, and bug fixes. No new functionality.
-
Added HttpException + shared httpGet/httpPostForm helpers that guarantee disconnect() on every request (success or failure) and surface the real response body on errors, instead of leaking HttpURLConnection instances on every calendar fetch/token exchange
-
Replaced fragile string-matching (e.message?.contains("401")) with a typed HTTP status check for detecting expired tokens
-
Fixed redundant/incorrect isAllDay condition when parsing event start times
-
Isolated per-calendar fetch failures so one bad or inaccessible calendar no longer blanks out the entire event list
-
Treat freeBusyReader calendars as read-only, matching existing reader handling
-
Added URL-encoding code, client_secret, and refresh_token in OAuth token request bodies