I have encountered a bug concerning events that specify a TZID in their DTSTART or DTEND. According to the iCalender specification, this should be valid, and it is also working correctly when I subscribe to the ICS file through Google Calendar instead of ICSDroid, so I’m thinking the problem lies with ICSDroid.
I am linking two ICS files each containing one event, one that shows the event at the correct date and time, and one that doesn’t. The only difference between the two files is this:
DTEND;TZID=Europe/Berlin;VALUE=DATE-TIME:20180723T114500
DTSTART;TZID=Europe/Berlin;VALUE=DATE-TIME:20180723T081500
vs.
DTEND;VALUE=DATE-TIME:20180723T114500
DTSTART;VALUE=DATE-TIME:20180723T081500
See also: the screenshot below. One event is showing at the correct time, and the other is showing the day before at 11pm. The “11pm the day before” pattern seems to be constant for all events with a TZID in their DTSTART or DTEND, no matter what their actual start or end time should be.
I’d be grateful if you could check this out. Thanks!
Hello,
Probably this one: https://github.com/ical4j/ical4j/issues/230
I wonder whether it works with a VTIMEZONE with both STANDARD and DAYLIGHT components… unfortunately, this would require debugging ical4j/2.x and 3.x has just been released (which is not useable with Android <7).
Can still replicate this bug with 1.8.2 and e.g. https://cfp.linuxwochen.at/de/LWW19/public/schedule.ics
Anything that can be done to help resolve this?
@akallabeth Nothing has been changed in 1.8.2 regarding this. - Yes, fix https://github.com/ical4j/ical4j/issues/230 
I have sent an updated ICSx⁵ APK over email. Can you please tell me whether it works for you?
Should be fixed with 1.8.4.
