Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default alert is not set for events with RECURRENCE-ID #327

Closed
ArnyminerZ opened this issue May 16, 2024 Discussed in #248 · 1 comment · Fixed by #328
Closed

Default alert is not set for events with RECURRENCE-ID #327

ArnyminerZ opened this issue May 16, 2024 Discussed in #248 · 1 comment · Fixed by #328
Labels
bug Something isn't working question Further information is requested

Comments

@ArnyminerZ
Copy link
Member

Discussed in #248

Originally posted by VS-X March 15, 2024
Hi, I noticed that some events do not have a default calendar alert I set in the app, even on version 2.2. After some investigation, RECURRENCE-ID seems to be the culprit. If I remove that line from the .ics file and import it in icsx5, then the alert is correctly set to 3 minutes.
Below is a sample event that reproduces for me:

BEGIN:VEVENT
UID:***
RECURRENCE-ID;TZID=FLE Standard Time:20240312T110000
SUMMARY:Test Event
DTSTART;TZID=FLE Standard Time:20240313T150000
DTEND;TZID=FLE Standard Time:20240313T160000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20240315T091733Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION:
END:VEVENT
```</div>
@ArnyminerZ ArnyminerZ added bug Something isn't working question Further information is requested labels May 16, 2024
@ArnyminerZ ArnyminerZ linked a pull request May 16, 2024 that will close this issue
4 tasks
@ArnyminerZ
Copy link
Member Author

Turns out we were adding the default alarm only for the event itself, but not the exceptions. Fixed in #328

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant