[BUG] .ics exports wrong day on repeated whole day events

[Nurgotora]

EssentialPIM Pro 11.6 (but also on previous versions)
Windows 10

Exporting a whole day event yields the following wrong ics entry:

BEGIN:VEVENT
UID:230211047488802904
LAST-MODIFIED:20211025T063637Z
DTSTART;VALUE=DATE:20160620
DTEND;VALUE=DATE:20160621
SUMMARY:A Birthday of someone
CLASS:PUBLIC
DTSTAMP:20230707T065712Z
RRULE:FREQ=YEARLY;BYMONTH=6;BYMONTHDAY=19
END:VEVENT

The import then places this even on the 19th

[admin]

Please open the event in EPIM and share a screenshot of the dialog window with us so that we can review the event properties. Thank you.

[Nurgotora]

You need to enter at least 10 characters.

[admin]

Thanks for providing the information, although we still couldn't reproduce the problem. Please check the problem with the new EPIM database file. Will there be the same issue? If so, forward us the test database file, please.

[Nurgotora]

I've cleaned the database down to one single event demonstrating the issue.

Mark and export the Event on June 20th, 2023. This will yield the incorrect ics entry (BYMONTHDAY=19).

In the original database out of 65 such whole day repeat events 61 exported wrongly in this way.

I have sent the two files by PM to admin

[admin]

Thank you, the problem reproduced and should be addressed in the next minor update of EPIM.

UPDATE: It seems that there is an issue with the specific event. You can try opening it up as a series, then save it. In this case, the export should work correctly.