Recurring event edge cases are more reliable, custom field extraction can now reach an event's UID and URL, and a security advisory in the calendar-parsing library is resolved. This beta specifically needs testing on mobile — see the note below.
What changed for you
- Recurring events landing exactly on their last occurrence now show up. A biweekly (or any interval) series whose final occurrence falls exactly on its
UNTILdate was being dropped; it's now included, per the ICS spec. getEvents()now exposesuidandurldirectly on each event, so custom field extraction and Templater templates can use an event's calendar UID or ICS URL without hunting throughextractedFields.- Templater docs now show a date-range example —
getEvents()already accepted a range of dates at once, it just wasn't documented. - Security fix: upgraded the underlying calendar-parsing library, resolving a known vulnerability. As a side effect, this also fixes real, previously-reported recurrence and Microsoft 365 timezone bugs (still gathering confirmation on the timezone one — see below).
- Discard-changes prompts now use Obsidian's own dialog style instead of the browser's native popup.
Please test on mobile if you can
This release upgrades a core dependency that internally requires a fairly modern JavaScript engine. Desktop Obsidian (and most current Android devices) should be unaffected, but older iOS versions could hit a parsing error where none existed before. If that happens, you'd see an "Error processing calendar" notice rather than a crash — but I'd like to know if it happens at all before this goes to a stable release. If you're on mobile, please try importing your calendars and let me know either way.
Also in this release
- Custom field extraction can no longer misinterpret a location/description that carries ICS parameters (a rare but real edge case)
- General internal type-safety and code-quality cleanup to align with Obsidian's plugin review guidelines (no user-visible change expected, but flagging in case anything looks different)
If you were affected by these issues, please confirm here:
- #190 (recurring event dropped on its last occurrence)
- #192 (Microsoft 365 timezone parsing error) — I don't have a repro file for the specific error still being reported; if this affects you, a sample (anonymized)
.icsfile would help a lot - #198 (multi-day events only showing on the first day) — the core bug was already fixed in 1.12.1; this beta doesn't change that further