CalDAV VALARM from tasks.org not interpreted correctly?

[oktayacikalin]

Describe the bug
I tested tasks.org on Android some days ago and added a due date, don't remember whether I removed it afterwards. Now I've seen that the due date is wrong and also won't show up in Nextcloud Tasks.

To Reproduce
Steps to reproduce the behavior:

1. Add and remove a due date or alarm to a task using tasks.org (Android)
2. View the event in Planify and Nextcloud Tasks
3. Due date is wrong and not shown in Nextcloud

Expected behavior
Planify should either ignore the malformed VALARM or propose to remove it.

Screenshots

BEGIN:VTODO
DTSTAMP:20240320T081235Z
UID:0d8ad92f-eec0-4cb3-8e7e-f61a67fa77ee
SEQUENCE:3
CREATED:20240318T220730Z
LAST-MODIFIED:20240320T081233Z
SUMMARY:GP 192 / LR41 bestellen
PRIORITY:5
STATUS:NEEDS-ACTION
RELATED-TO;RELTYPE=PARENT:93a0e54d-545f-49f0-8e06-3a4c9e02d8e8
PERCENT-COMPLETE:0
BEGIN:VALARM
TRIGGER;RELATED=END:PT0S
ACTION:DISPLAY
DESCRIPTION:Default Tasks.org description
END:VALARM
END:VTODO

BEGIN:VTODO
DTSTAMP:20240319T075130Z
UID:93a0e54d-545f-49f0-8e06-3a4c9e02d8e8
CREATED:20240319T075130Z
LAST-MODIFIED:20240319T075130Z
SUMMARY:Bestellen
PRIORITY:5
STATUS:NEEDS-ACTION
PERCENT-COMPLETE:0
END:VTODO

Desktop:

• Latest GNOME Shell on Fedora Workstation 39
• Planify 4.5.8 from flathub

Additional context
I'm sorry that I cannot really remember how it came to this state, but somehow tasks.org put this VALARM into the VTODO. And I don't understand how Planify comes to this due date seen on the screenshot. 🤷‍♂️
Any idea how this came to be?