Calendar sync incomplete: some events missing and new events don't appear

[hyper-charlie]

Description

Calendar events are not syncing consistently to Hyprnote. Some existing events display, but others don't. Newly created events don't appear at all, even after waiting and restarting the app.

Steps to Reproduce

1. Grant Hyprnote calendar access in System Settings → Privacy & Security → Calendar
2. View calendar in Hyprnote and compare to macOS Calendar app
3. Note that some events are visible but others are missing (no clear pattern—includes recurring and non-recurring events)
4. Create new test events in macOS Calendar app
5. Observe that new events don't appear in Hyprnote calendar view

Expected Behavior

All events from macOS Calendar should be visible in Hyprnote. New events should appear after creation.

Actual Behavior

• Some existing events display in Hyprnote, others don't (affects recurring and non-recurring events)
• Newly created events do not appear in Hyprnote
• All events (including missing ones) are visible in the native macOS Calendar app
• Issue persists across multiple calendar sources

Environment

• Platform: macOS 26.3.1
• App Version: 1.0.15
• Architecture: aarch64
• Build: 2b111d3
• Locale: en-US
• User ID: beaea632-8ba0-4a5e-bf07-784fd9b23eb3

Troubleshooting Attempted

• Revoking and re-granting calendar permissions in System Settings
• Restarting Hyprnote
• Testing with multiple calendar sources
• No cache clearing or manual sync options found in Hyprnote settings

[devin-ai-integration]

Codebase Analysis: Calendar Sync Architecture

Explored the calendar sync code to identify potential causes for missing events. Here's what I found.

Relevant Files

Sync orchestration (frontend — this is the primary sync path for the desktop app):

• apps/desktop/src/services/calendar/index.ts — Entry point (syncCalendarEvents), iterates provider connections
• apps/desktop/src/services/calendar/ctx.ts — Creates sync context, manages calendar tracking ID mappings, defines time window
• apps/desktop/src/services/calendar/fetch/incoming.ts — Fetches events from providers via Tauri commands
• apps/desktop/src/services/calendar/fetch/existing.ts — Reads current events from TinyBase store
• apps/desktop/src/services/calendar/process/events/sync.ts — Computes add/update/delete plan by matching tracking IDs
• apps/desktop/src/services/calendar/process/events/execute.ts — Applies sync plan to TinyBase store
• apps/desktop/src/services/task-manager.tsx — Triggers sync every 60s + on CalendarChangedEvent

Apple EventKit integration (native layer):

• crates/apple-calendar/src/apple/handle.rs — EventKit access, event fetching with retry (3x, 100ms backoff on XPC failures)
• crates/apple-calendar/src/apple/notifications.rs — Listens for EKEventStoreChangedNotification
• crates/calendar/src/convert.rs — Converts Apple events to unified CalendarEvent type

Calendar display:

• apps/desktop/src/calendar/hooks.ts — useCalendarData() builds event-by-date map from TinyBase query results

Potential Root Causes

1. Calendar enablement gate (likely contributor)
In ctx.ts:34, createCtx only includes calendars where enabled === true (via the enabledCalendars TinyBase query). New calendars default to enabled: false (ctx.ts:155). If the user hasn't explicitly enabled all their calendars in the sidebar settings, those calendars' events won't sync. This would explain partial sync — some calendars enabled, others not.

2. Silent event drop when calendarTrackingIdToId has no entry
In execute.ts:45-50, when adding new events, if the event's tracking_id_calendar isn't found in calendarTrackingIdToId, the event is silently skipped (continue). This can happen if:

• The calendar sync hasn't completed before events sync
• A calendar was recently added but not yet in the store

3. fetchIncomingEvents error aborts entire provider sync
In incoming.ts:41-43, if any calendar fetch fails (e.g., CalendarNotFound for a deleted calendar), it throws CalendarFetchError. The catch in index.ts:68-73 then aborts the entire provider sync — meaning all other calendars for that provider also lose their sync for that cycle.

4. Recurring event .expect() panic risk
In convert.rs:275-276, there's an .expect() that will panic if an Apple event has has_recurrence_rules: true but recurrence is None. If this is hit, it would crash the Tauri command handler for that sync cycle. This is in the backend path (used by CLI sync), but worth noting.

5. Time window constraint
Events are only fetched within a hardcoded window: 7 days past → 30 days future (ctx.ts:169-176). Events outside this range won't appear.

6. Notification delivery may not trigger sync
In notifications.rs:45-47, the notification observer thread uses std::thread::park() in a loop. The EKEventStoreChangedNotification is dispatched via NSNotificationCenter which requires a run loop. The park()-based loop doesn't pump a run loop — this could mean the notification callback never fires on macOS, so new events created in Calendar.app would only appear on the next 60-second poll.

7. Ignored events filtering
In hooks.ts:80-81, events are filtered by the isIgnored() check, which hides events the user has previously dismissed. If the user dismissed a recurring series, all instances are hidden.

Recent Relevant Changes

• 4aad46c08 — "fix: allow syncing calendar even with unreachable providers" — Changed error handling so remote provider failures don't block Apple calendar sync. This is recent and relevant.
• 552a22376 — "fix(calendar): fix recurring event sync and recurrence_series_id population" — Fixed recurring events overwriting each other due to shared event_identifier. Uses composite key now.
• 7061647a8 — "fix: prevent organizer to be added as duplicate attendee during sync"

Suggested Debugging Steps

1. Check which calendars are enabled: Open the calendar settings sidebar (gear icon) and verify all desired calendars have their toggle on. New calendars default to disabled.
2. Check console logs: Look for [calendar-sync] Error syncing or [calendar-sync] Aborting messages that would indicate fetch failures.
3. Check if events are within time window: Verify the missing events fall within the -7 to +30 day range.
4. Check if events are in the "ignored" list: The ignored_events and ignored_recurring_series values in the TinyBase store could be filtering them out.

Additional Information That Would Help

• Are the missing events from specific calendars, or spread across all calendars?
• Are the affected calendars enabled in the Char calendar sidebar?
• Are any of the missing events recurring?
• Do the missing events fall within the -7 to +30 day window?
• Any error messages in the app's dev console?