NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev, #1761 most downloaded on pub.dev
iOS implementation of the device_calendar_plus plugin.
Latest stable
0.11.0
Last release 1 months ago
20 Oct 2026
Ships fairly regularly
a new release about every 6 weeks
Nearly every release is documented
notes for 22 of 22 stable releases
Nothing withdrawn
no release was ever pulled
1 years old
22 releases · first in 2025
Drag across the ruler to compare, or tap a release to open it.
Breaking: createCalendar's platformOptions: parameter is replaced by separate android: and ios: parameters, and the option classes are renamed: Create
createCalendar's platformOptions: parameter is replaced
by separate android: and ios: parameters, and the option classes are
renamed: CreateCalendarOptionsAndroid is now CalendarOptionsAndroid,
CreateCalendarOptionsIos is now CalendarOptionsIos, and
CreateCalendarPlatformOptions is gone. Their fields are now optional, so
one call can pass both; each applies only on its own platform. See
Migrating createCalendar.createEvent takes android: EventOptionsAndroid,
and updateEvent / updateRecurring take
android: EventUpdateOptionsAndroid. They apply only on Android and are
ignored on iOS, so shared code can pass them. Their fields speak Android's
own semantics, with no attempt at parity with iOS. See
Platform-only options.EventStatusAndroid (tentative,
confirmed, canceled, Android's STATUS values). It carries through a
single-occurrence edit, both updateRecurring spans and the
thisAndFollowing split's carried occurrences. An occurrence edited
without a status now keeps the series' status instead of being written as
confirmed. Android can't write a NULL status to an existing event, so
there's no clear; canceled on a series or one occurrence takes it out of
listings, as Android's provider reads it (#70).EKEvent.organizer (#236).user@me.com,
@icloud.com, @mac.com) is now recognised: listSources reports it
can create calendars, and createCalendar without a source uses it.
Thanks @eikob (#233). An iCloud+ custom-domain title still isn't
recognised, since EventKit gives no other way to tell iCloud from Google.updateRecurring with thisAndFollowing that makes an all-day series
timed lost the new series' last occurrence across a DST change, and west
of UTC left the split occurrence on the original series too. It now splits
first and makes the new series timed in a second save (#232).updateRecurring with thisAndFollowing that clears the rule from a
series' first occurrence now edits the series in place and keeps its ID.Your coding agent can read these notes before it upgrades. Set up the MCP server →
Breaking: updateEvent and deleteEvent act on one thing — a one-off event or a single occurrence — and take instanceId instead of eventId. A bare ID of
Breaking: updateEvent and deleteEvent act on one thing — a one-off
event or a single occurrence — and take instanceId instead of eventId.
A bare ID of a recurring series is refused with
DeviceCalendarException(invalidArguments) and nothing is written. Moving a
series' start through updateEvent used to shift the whole series and drop
every earlier occurrence without an error; series-wide changes now go
through updateRecurring / deleteRecurring (#175).
Migrating:
updateEvent(eventId: event.instanceId, …) →
updateEvent(instanceId: event.instanceId, …). Same for deleteEvent.
For a one-off event instanceId equals eventId, so nothing else
changes.updateEvent(eventId: seriesId, …) on a recurring event →
updateRecurring(seriesId, EventSpan.allEvents, …). startDate /
endDate map to start / duration; the other fields are the same.deleteEvent(eventId: seriesId) on a recurring event →
deleteRecurring(seriesId, EventSpan.allEvents).updateRecurring takes reminders (a Patch<List<Duration>>), to set or
clear reminders across a series, as updateEvent does for one event (#175).Recurring events
updateRecurring with thisAndFollowing on an event that doesn't repeat
is refused with invalidArguments on both platforms, and nothing is
written. iOS matched the timestamp against the event itself, so it edited
or deleted the whole event and reported success (#124).updateRecurring lands on the day
you asked for. The new start was compared in the wrong timezone: west of
UTC a same-day start was refused and a day-earlier move onto a day the rule
doesn't generate got through; east of UTC (e.g. Sydney) a one-day move did
nothing (#144).updateRecurring keeps every
occurrence on its calendar day. West of UTC the series gained an extra
occurrence the day before its start and lost its last one (#187).updateRecurring refuses a start move with no new rule when it breaks
any day the rule pins, as Android does. A yearly
BYMONTH=11;BYDAY=4TH series could be moved to a Thursday in December
(#188).createEvent and updateRecurring refuse a recurrence rule whose FREQ
isn't DAILY/WEEKLY/MONTHLY/YEARLY, or that is malformed, with
invalidArguments and write nothing, on both platforms. iOS createEvent
dropped the rule and saved a one-off event; Android stored FREQ=HOURLY
as an hourly series (#125).updateEvent or deleteEvent on one occurrence of a series on a
synced calendar (Google, Exchange) no longer hides the whole series when
the series hasn't synced yet (#163).Native modals
showEventModal, showCreateEventModal) always
complete; several paths used to leave the await hanging or crash (#123):
DeviceCalendarException(operationFailed) straight away. It used to
orphan the first call's future and, on iOS, fail to present, so both
hung.DeviceCalendarException(operationFailed), as openAppSettings
does. iOS used to crash, and Android threw an unconverted
PlatformException.showEventModal on an event that doesn't exist throws
DeviceCalendarException(notFound), as iOS does. It used to open the
calendar app on nothing and complete normally.Permissions
writeOnly rather than notDetermined, so a createEvent straight after
the prompt passes its permission check (#137).android: / ios:
options. CreateCalendarOptionsIos moves to the platform interface as
CalendarOptionsIos. Android-only options are ignored, and an
updateEvent or updateRecurring call whose only change is Android-only
writes nothing (#70).updateEvent with isAllDay: false and new dates on one occurrence of an all-day series saves in two steps too — the other changes first, which detaches
updateEvent with isAllDay: false and new dates on one occurrence of an
all-day series saves in two steps too — the other changes first, which
detaches the occurrence, then the timed flip with the dates. EventKit's
iCloud store persisted the hours as UTC wall clock when the detach and the
flip happened in one save: a 09:00–10:00 occurrence in Los Angeles read
back as 02:00–03:00, though the saved EKEvent reported 16:00 UTC and
its zone right up to the commit. The reverse of #210's flip; the local
store, and so the simulator, got the one-step save right (#212). Either
flip now checks that its first save detached the occurrence and fails
with operationFailed, the occurrence unchanged, when it did not, rather
than flipping an attached occurrence in one save.updateRecurring with allEvents and a start on another day of a rule
that pins days (Monday of a Mon/Wed rule to its Wednesday) moves the
series. EventKit read the .futureEvents save, with the loaded rule left
untouched, as moving one occurrence: it left the master where it was,
detached the first occurrence onto the new day with no rule, and the
plugin returned that occurrence's /RID= ID. The kept rule is now set on
the event again for such a move, which makes the save a series edit
(#206).updateRecurring with thisAndFollowing and a start on another day the
kept rule generates splits the series at the occurrence, with the rule's
remaining count carried over, instead of refusing the move while the rule
pins days. The same re-set of the kept rule makes EventKit split the
series rather than detach the occurrence (#194).updateEvent with isAllDay: true on one occurrence of a timed series
saves in two steps — the other changes and the dates first, which detaches
the occurrence, then the all-day flip. EventKit's iCloud store persisted
the detached occurrence's end a day late when the detach and the flip
happened in one save, whatever end was written: a 9–10am occurrence read
back as two days and a 23:30–00:30 one as three. The local store, and so
the simulator, got the one-step save right. Without startDate or
endDate, on a one-off as well as an occurrence, the all-day span is now
also written explicitly — local midnight of the start day through the last
second of the last day the timed event touched, the span Android writes
(#203) in #195's end convention — rather than left to EventKit.updateRecurring refuses a start move with no new rule unless the existing rule generates the series' new start. It compared only the weekday, day of m
updateRecurring refuses a start move with no new rule unless the existing
rule generates the series' new start. It compared only the weekday, day of
month and month the rule pins, so an ordinal BYDAY or a BYSETPOS series
(the 4th Thursday of November, say) could move to another occurrence of its
weekday (the 3rd Thursday), leaving the start on a day the rule never
generates (#189). A move onto another day the rule generates (Monday to
Wednesday of a Mon/Wed/Fri rule) is now allowed through allEvents; with
thisAndFollowing a move to another day still throws while the rule pins
days, until iOS can split such a series (#194).updateRecurring on an all-day series adds duration (or keeps the
existing span, when only start moves) in calendar days rather than
86,400-second days, so a multi-day all-day series no longer loses or gains
its last day when its span crosses a DST change (#195).updateEvent and updateRecurring write an all-day event's end as the
last second of its last day, the way EventKit stores it. An exclusive
midnight end written onto an existing all-day event read back as one more
day, so a two-day duration or end gave three (#195).Minimum supported SDK is now Flutter 3.44 / Dart 3.12. Android migrated to Flutter's built-in Kotlin, so the KGP deprecation warning no longer prints…
flutter build (#133).Recurring events
updateRecurring with a new rule anchors the series on the first day that
rule generates, on both platforms. Changing a weekly series to another
weekday left its start on the old day, so the first occurrence was stranded
there. A rule that generates no occurrence at all is refused with
invalidArguments and the series is left untouched (#140).updateEvent or deleteEvent on a single occurrence of a
recurring event in a local calendar no longer makes the other occurrences
disappear, the earlier ones for good (#153).deleteRecurring with thisAndFollowing also removes an
occurrence on or after the split that had been edited on its own, matching
iOS (#157).updateRecurring with thisAndFollowing carries an occurrence on
or after the split that had been edited on its own into the new series,
with its edits, as iOS does. It used to stay on the old series, listed next
to a duplicate, and on a synced calendar the edit was lost (#158).getEvent resolves all-day recurring instance IDs (it always
returned null) and returns a recurring master's real end date instead of a
zero-length one (#122).Synced calendars
Listing events
listEvents returns an all-day event when the window is a sub-day
slice of its date (e.g. 10:00–11:00), and orders all-day events by their
local midnight among timed events in non-UTC zones, as iOS does (#122).listEvents rejects an endDate before startDate with ArgumentError,
like the other date-range methods, and answers an empty range
(endDate == startDate) with no events on both platforms (#162).Calendars
updateCalendar and deleteCalendar throw the documented readOnly for a
calendar that can't be modified, on both platforms. iOS used to surface a
refused delete as operationFailed; Android renamed or deleted any row it
was handed (#126).createCalendar refuses a non-local accountType with readOnly,
as listSources already reports and iOS already does for non-creatable
sources, instead of leaving a phantom calendar the account's sync adapter
can wipe (#126).createCalendar / updateCalendar throw ArgumentError for a colorHex
that isn't #RRGGBB (the # optional) instead of storing it silently as
black, and forward the canonical #RRGGBB to the platform (#126).deleteCalendar('') throws ArgumentError, like the other mutations (#126).listCalendars no longer crashes on a provider row with a NULL
display name (#126).CalendarSource.supportsCalendarCreation, CreateCalendarOptionsIos and
CreateCalendarOptionsAndroid describe what the code actually does: iOS
creates under iCloud or local, Android under the local account type (#126).Platform packages: device_calendar_plus_android 0.8.0, device_calendar_plus_ios 0.8.0.
updateEvent and deleteEvent without a timestamp refuse
a recurring series with INVALID_ARGUMENTS and write nothing; series-wide
changes go through updateRecurring / deleteRecurring (#175).updateRecurring forwards a reminders patch. A thisAndFollowing split
that clears the rule keeps the occurrence's reminders on the standalone
event it leaves, as Android does (#175).updateRecurring(allEvents) switching a timed series to all-day shifts the
start in local time, where EventKit puts all-day events. It shifted in the
series' stored zone, so a UTC-stored series landed on UTC midnight, which
west of UTC is the day before: the series gained an extra first occurrence
off its BYDAY and lost its last one. The day-move check reads each date in
its own zone too (#187).updateRecurring and deleteRecurring with thisAndFollowing refuse a
non-recurring event with INVALID_ARGUMENTS and write nothing, as Android
does. A timestamp that fell inside the event matched it, so the whole event
was edited or deleted and the call reported success (#124).updateRecurring refuses a start move with no new rule when it breaks any
day the rule pins, as Android does. It checked only BYDAY when the rule
had one, so a yearly BYMONTH=11;BYDAY=4TH series could move to a
Thursday in December (#188).showEventModal/showCreateEventModal
while one is showing fails OPERATION_FAILED instead of orphaning the
first reply; swiping the view modal down resolves it; a modal is presented
from the top of the presentation stack, so an app sheet that's already up
no longer swallows it; and a missing root view controller fails
OPERATION_FAILED instead of crashing with fatalError.createEvent refuses a recurrence rule it can't parse (a FREQ other than
DAILY/WEEKLY/MONTHLY/YEARLY, or malformed input) with
INVALID_ARGUMENTS and writes nothing, as updateRecurring already does.
It used to drop the rule and save a one-off event (#125).writeOnly rather than notDetermined, so a createEvent fired
straight after the prompt passes its permission gate. The request now waits
briefly for the OS status to catch up with an ungranted answer (#137).Per-event color lands, plus one rename to swallow.
Per-event color lands, plus one rename to swallow.
Event.colorHex — the event's custom color as #RRGGBB, with a parsed Event.color getter (read-only, mirrors Calendar.colorHex). Android reads it from EVENT_COLOR; null when the event just uses its calendar's color, and always null on iOS (EventKit has no per-event colors). No write support (#117).WeeklyRecurrence's wkst field and constructor parameter are renamed to weekStart, matching the spelled-out naming of the other recurrence fields. The emitted RRULE is unchanged (still WKST=). Update WeeklyRecurrence(wkst: …) call sites and .wkst reads to weekStart.Ships device_calendar_plus 0.8.0 and device_calendar_plus_android 0.7.1. The platform interface and iOS packages are unchanged.
updateRecurring with a new rule anchors the series on the first day that
rule generates. Changing a weekly series to another weekday left its start
on the old day, so the first occurrence was stranded there. A rule that
generates no occurrence at all is refused with INVALID_ARGUMENTS and the
series is left untouched (#140).deleteCalendar refuses a calendar EventKit marks immutable or read-only
with READ_ONLY before asking the store, instead of surfacing the refused
remove as OPERATION_FAILED. updateCalendar now checks isImmutable
too, EventKit's own flag for "can't be edited or deleted" (#126).Docs + packaging polish. No code or behaviour changes.
Docs + packaging polish. No code or behaviour changes.
device pub.dev topic (dropped federated to stay within the five-topic limit).doc/.EKEventStore.authorizationStatus still reports
.notDetermined. On iOS 17+ the live status can lag the request handler, so
the first call after a fresh grant failed its permission gate until the app
restarted. The tier the OS confirmed is now remembered for the process and
consulted only when it outranks a stale live status; a terminal denied /
restricted always wins, so a Settings revocation is never masked (#134).showCreateEventModal is gated only below iOS 17, where the editor runs
in-process. On iOS 17+ EKEventEditViewController is out-of-process and
needs no calendar access (#121).NSCalendarsFullAccessUsageDescription
(what the OS demands) rather than the legacy key, and only when a prompt will
actually fire — already-granted and terminal states get their status back
without a configuration error (#121).createEvent with a named calendarId under write-only access reports
permissionDenied instead of notFound (#121).CalendarAuthorization seam:
CalendarAccess normalises EventKit's status across the iOS 17 divide and
PermissionService holds policy only. Swift unit tests cover the grant,
revocation and configuration paths (#134).Feature release. App-facing API is additive; device_calendar_plus_platform_interface has breaking signature changes for platform implementers.
Feature release. App-facing API is additive; device_calendar_plus_platform_interface has breaking signature changes for platform implementers.
requestPermissions(level: CalendarAccessLevel.writeOnly) for the gentler add-only prompt (#89).DeviceCalendar.instance.autoPermissions = AutoPermissionMode.asNeeded | .full; methods request access on first use (#90).calendarId — omit it on createEvent to write to the default calendar (#88).reminders: List<Duration> on create, Patch<List<Duration>> on update, Event.reminders read back; minute-granular relative offsets (#87).permissionDenied (not "no writable calendar") when a default can't be resolved (#112); tighter denial reporting (#108).All four packages bumped 0.6.0 → 0.7.0 in lockstep.
requestWriteOnlyAccessToEvents (iOS 17+). It is not a
permanent ceiling — a later full request re-prompts and upgrades the app
in-app (#89).createEvent with no calendarId writes to defaultCalendarForNewEvents
(#88).EKAlarm(relativeOffset:) on EKEvent.alarms (#87).chore(release): prepare 0.6.0
chore(release): prepare 0.6.0
updateRecurring takes the anchored occurrence's new start
(newStartMillis) instead of startMinuteOfDay. shiftStart translates the
series anchor by the wall-clock delta (calendar-day count + time-of-day) in
the event's EKEvent.timeZone, so a move can change the day and time
together and stays correct across DST (#103).updateRecurring rejects a start that moves the day of a series whose
EKRecurrenceRule pins it (daysOfTheWeek / daysOfTheMonth /
monthsOfTheYear) unless a new rule is also supplied
(dayMoveConflictsWithRule).EventKit reads and writes now run on a background serial queue instead of the main thread, so operations on large calendars no longer stall the UI
listEvents over a span longer than EventKit's ~4-year predicate limit now
chunks the query into windows and de-duplicates recurring instances across
window boundaries, so long ranges return every event exactly once, sorted
(#94)createCalendar now fails with a clear error on sources that can't hold
calendars (e.g. subscribed/holiday sources) instead of an opaque EventKit
failure (#96)updateRecurring(thisAndFollowing, recurrenceRule: Patch.clear()) now splits
the series — truncating the master before the occurrence and detaching a
standalone non-recurring event at the split point — instead of collapsing the
whole series into a single event. Matches Android's behavior (#93)iOS: fix showEventModal(edit: true) crash
showEventModal(edit: true) no longer crashes with NSInvalidArgumentException
("Pushing a navigation controller is not supported"). EKEventEditViewController
is a UINavigationController subclass and is now presented directly instead of
being wrapped in another navigation controller (#77)Breaking: recurring-edit split — updateRecurring / deleteRecurring accept only allEvents and thisAndFollowing (both EKSpan.futureEvents); single occur
updateRecurring / deleteRecurring
accept only allEvents and thisAndFollowing (both EKSpan.futureEvents);
single occurrences go through updateEvent / deleteEvent with an
occurrence timestamp (EKSpan.thisEvent)updateRecurring time changes preserve each occurrence's date, replacing
only the time-of-day componentsEKEvent; an edit whose
startDate passes the occurrence's untouched end now fails with
invalidArguments (matching Android) instead of saving an inverted eventupdateRecurring() — series-level recurring-event edits with EventSpan (allEvents / thisAndFollowing / thisInstance), backed by EKSpan.futureEvents and
updateRecurring() — series-level recurring-event edits with EventSpan (allEvents / thisAndFollowing / thisInstance), backed by EKSpan.futureEvents and EKSpan.thisEventdeleteRecurring() — same EventSpan semantics on EKEventStore.removeurl field on events via EKEvent.urlPatch<T> support in updateEvent() — null leaves a field unchanged, Patch.set writes, Patch.clear nils the field on the EKEventedit flag on showEvent() — presents EKEventEditViewController instead of EKEventViewControllerCalendar source lookup fallback when default source is unavailable
createCalendar default fallback prefers iCloud over other CalDAV sources (#33)Swift Package Manager support (CocoaPods continues to work as before)
Fixed parsing of instanceId for events with @ in their event ID (e.g., Google Calendar IDs like abc123@google.com)
instanceId for events with @ in their event ID (e.g., Google Calendar IDs like abc123@google.com)feat(android): add CreateCalendarOptionsAndroid for custom account na…
feat(android): add CreateCalendarOptionsAndroid for custom account na…
createCalendar() signature updated to accept optional platformOptions parameter (ignored on iOS)showEvent() now properly stores result callback and calls it in eventViewController(_:didCompleteWith:) delegate method after modal is dismissed
showEvent() now properly stores result callback and calls it in eventViewController(_:didCompleteWith:) delegate method after modal is dismissedchore: bump version and update changelogs
chore: bump version and update changelogs
deleteEvent() now always deletes entire series for recurring events using EKSpan.futureEvents on master event (removed deleteAllInstances parameter)updateEvent() now always updates entire series for recurring events using EKSpan.futureEvents on master event (removed updateAllInstances parameter)NOT_SUPPORTED error code (no longer needed)openAppSettings() implementation using UIApplication.openSettingsURLString
openAppSettings() implementation using UIApplication.openSettingsURLStringgetPlatformVersion() implementation (unused boilerplate)Version sync with other packages. No functional changes.
Version sync with other packages. No functional changes.
Initial release.
Initial release.
One column per month.