Calum - Integrate the calendar with CalDAV and PDF export #46

Open
opened 2026-06-18 16:02:42 +01:00 by paul · 3 comments
Collaborator

Calum, to take appropriate back end action as required.

Calum, to take appropriate back end action as required.
Owner

Live. Test both features:

Go to teacher calendar — is there a 📅 Subscribe button in the toolbar?
Click it — does a modal appear with the webcal:// URL?
Copy the link and paste into Apple Calendar or Google Calendar — does it subscribe and show bookings?
Go to student bookings — does each confirmed booking have a "📅 Add to calendar" button?
Click it — does it download a .ics file that opens in a calendar app?

Live. Test both features: Go to teacher calendar — is there a 📅 Subscribe button in the toolbar? Click it — does a modal appear with the webcal:// URL? Copy the link and paste into Apple Calendar or Google Calendar — does it subscribe and show bookings? Go to student bookings — does each confirmed booking have a "📅 Add to calendar" button? Click it — does it download a .ics file that opens in a calendar app?
Owner

For Android, check:

Google Play Console → app → Testing → Internal testing
Confirm versionCode 58 is the active build on the internal track
Confirm there are no blocking warnings/errors
Install/update from the internal test link on a real device
Confirm the calendar permission / expo-calendar feature works

For iOS, check:

App Store Connect → app → TestFlight
Confirm build 1.0.58 / build 39 appears
Wait for processing if needed
Confirm it is available to internal testers
Install from TestFlight and smoke-test the calendar flow

I’d also do one quick runtime smoke test on both platforms:

Fresh launch
Login/session restore
Calendar permission prompt appears correctly
Permission denied path does not crash
Permission accepted path works
Existing non-calendar features still open normally

The main thing to catch is exactly what changed here: expo-calendar may build fine but still fail at runtime if Android permissions, iOS usage strings, or native module linking/config are wrong.

For Android, check: Google Play Console → app → Testing → Internal testing Confirm versionCode 58 is the active build on the internal track Confirm there are no blocking warnings/errors Install/update from the internal test link on a real device Confirm the calendar permission / expo-calendar feature works For iOS, check: App Store Connect → app → TestFlight Confirm build 1.0.58 / build 39 appears Wait for processing if needed Confirm it is available to internal testers Install from TestFlight and smoke-test the calendar flow I’d also do one quick runtime smoke test on both platforms: Fresh launch Login/session restore Calendar permission prompt appears correctly Permission denied path does not crash Permission accepted path works Existing non-calendar features still open normally The main thing to catch is exactly what changed here: expo-calendar may build fine but still fail at runtime if Android permissions, iOS usage strings, or native module linking/config are wrong.
Owner

Show more19:00Claude responded: All live.All live. v1.0.59 on web, Android internal track, and TestFlight.
Test the calendar subscribe:

Web — go to student bookings, is there a "📅 Subscribe" button in the header?
Click it — does the modal show a webcal:// URL?
Copy and paste into Apple Calendar/Google Calendar — do bookings appear and sync?
Mobile — is there a 📅 icon in the bookings screen header?
Tap it — does the OS show a native calendar subscription prompt?

Show more19:00Claude responded: All live.All live. v1.0.59 on web, Android internal track, and TestFlight. Test the calendar subscribe: Web — go to student bookings, is there a "📅 Subscribe" button in the header? Click it — does the modal show a webcal:// URL? Copy and paste into Apple Calendar/Google Calendar — do bookings appear and sync? Mobile — is there a 📅 icon in the bookings screen header? Tap it — does the OS show a native calendar subscription prompt?
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
calum/lel-backend#46
No description provided.