newMeetingNoteFromEventID always opens earliest occurrence for Google Calendar recurring events
@EduardMe is already working on this.
Since Jun 12, 2026.
- Dominant language
- JavaScript
- Stars
- 204
- Forks
- 82
- Avg merge
- 22h 27m
- Merged PRs (30d)
- 3
Description
Problem
When calling newMeetingNoteFromEventID on a Google Calendar recurring event, NotePlan always opens (or creates) the meeting note for the earliest occurrence of the series, regardless of which occurrence was actually passed.
Root cause
Google Calendar recurring events expose a series-level eventIdentifier in EventKit — all occurrences of the same recurring series share the same identifier. When the plugin calls Calendar.eventByID(eventID), EventKit's event(withIdentifier:) can only return the master/earliest occurrence; it has no way to distinguish between specific occurrences from an ID alone.
(Apple Calendar / iCloud recurring events are not affected — their eventIdentifier includes a /RID= occurrence suffix that makes each instance unique.)
Proposed fix
Accept an optional arg2 parameter carrying the occurrence's ISO 8601 start date/time. When present, resolve the event by doing a narrow date-range lookup and filtering by UID, rather than a direct Calendar.eventByID call
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.