Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.3.0

Affected Android/Custom ROM version

Android 15 (GrapheneOS Build 2025060200)

Affected device model

Pixel 6

How did you install the app?

GitHub releases

Which calendar service or provider do you use, if any?

Baikal

Which sync adapter app do you use for calendar synchronization, if any?

DAVx5

Steps to reproduce the bug

For setup:

1. Install Fossify Calendar, DAVx5 and configure it to sync with a Selfhosted Baikal CalDav Server.
2. Disable battery optimization for both Fossify Calendar and DAVx5.
3. Make sure CalDAV sync is enabled within Fossify Calendar's settings.

Scenario 1: Create Event in Fossify Calendar:

1. Open Fossify Calendar.
2. Create a new event.
3. Try to manually refresh the calendar within Fossify Calendar (e.g., pulldown gesture).
4. Notice that changes on the server (Baikal) or another synced client are not showing up.
5. Go into DAVx5 app and manually refresh.
6. Notice the changes are immediately reflected on the server side

Scenario 2: Creating an event elsewhere:

1. Create an from some other synchronized client, and make sure it shows up on the Baikal server (it will).
2. Open Fossify Calendar.
3. Try to manually refresh the calendar within Fossify Calendar (e.g., pulldown gesture).
4. Notice the new event will not show up.
5. Go into DAVx5 app and manually refresh.
6. Notice that changes are immediately reflected in the Fossify calendar app.

Expected behavior

The event created in Fossify Calendar should synchronize with the CalDAV server (Baikal) either immediately or upon manual refresh (pulldown gesture). Other synced clients should then reflect this new event.
Changes made on the CalDAV server (Baikal) or another synced client should be retrieved and reflected in the Fossify Calendar app either automatically (based on sync intervals) or upon manual refresh (pulldown gesture).

Actual behavior

Fossify Calendar is failing to synchronize calendar events with DAVx5, both for events created within Fossify Calendar and for events created externally. Manual refreshing within Fossify Calendar (e.g., via pulldown gesture) and automatic synchronization intervals are not triggering the sync. Synchronization only occurs when manually initiated from the DAVx5 application.

Screenshots/Screen recordings

No response

Additional information

No response