Ask Gemini for a calendar and it writes a confident, well-formatted-looking .ics — that Google Calendar then refuses to import. The problem is that Gemini's calendar files break the iCalendar (RFC 5545) spec in a few predictable ways. Paste your Gemini .ics below and we fix them automatically, free.
(No sign-in needed)
Cause: Gemini frequently omits the UID line that every VEVENT requires. With no UID, importers cannot tell events apart — so they either reject the file or overwrite everything into one event, and re-importing duplicates instead of updating.
Fix: The fixer adds a stable, deterministic UID to each event missing one, so every event imports separately and re-imports update cleanly instead of duplicating.
Cause: Gemini produces recurrence rules that are not valid iCalendar — malformed FREQ values, the wrong BYDAY syntax, or RRULE keywords that do not exist in RFC 5545. Calendar apps drop the recurrence or reject the event.
Fix: The fixer rewrites broken RRULEs into spec-valid form (for example FREQ=WEEKLY;BYDAY=TU,TH) and leaves correct rules alone, so repeating events repeat as intended.
Cause: Gemini references a timezone (TZID=Europe/London, for example) on the event start time but omits the VTIMEZONE block that defines that zone. Without it, calendar apps fall back to UTC or guess, shifting every event.
Fix: The fixer resolves the dangling TZID — injecting the matching VTIMEZONE or anchoring the time — so events stay at the time you intended regardless of the importing device.
Cause: Apple Calendar enforces the spec strictly. Explanatory text Gemini placed before BEGIN:VCALENDAR, unescaped commas, or a DTEND earlier than DTSTART will make it silently discard the entire import.
Fix: The fixer removes prose outside the VCALENDAR block, escapes special characters, and corrects invalid start/end ordering so Apple Calendar accepts the file.