Error: Couldn't parse iCalendar - debug included #123

Brog33 · 2023-02-24T11:50:06Z

Brog33
Feb 24, 2023

Trying to add sync for the Premier League webcal.
webcal://ics.ecal.com/ecal-sub/63f8a348cdeb72000e0ca89f/English%20Premier%20League.ics

Which results in the following error:

Couldn't parse iCalendar

at.bitfire.ical4android.InvalidCalendarException: Couldn't parse iCalendar
	at at.bitfire.ical4android.ICalendar$Companion.fromReader(ICalendar.kt:83)
	at at.bitfire.ical4android.Event$Companion.eventsFromReader(Event.kt:82)
	at at.bitfire.icsdroid.ui.AddCalendarValidationFragment$ValidationModel$validate$downloader$1.onSuccess(AddCalendarValidationFragment.kt:126)
	at at.bitfire.icsdroid.CalendarFetcher.fetchNetwork$icsx5_64_2_0_3_standardRelease(CalendarFetcher.kt:157)
	at at.bitfire.icsdroid.CalendarFetcher$fetchNetwork$1.invokeSuspend(Unknown Source:11)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
Caused by: net.fortuna.ical4j.data.ParserException: Error at line 133:Text cannot be parsed to a Duration
	at net.fortuna.ical4j.data.CalendarParserImpl.parse(CalendarParserImpl.java:172)
	at net.fortuna.ical4j.data.CalendarBuilder.build(CalendarBuilder.java:197)
	at net.fortuna.ical4j.data.CalendarBuilder.build(CalendarBuilder.java:185)
	at at.bitfire.ical4android.ICalendar$Companion.fromReader(ICalendar.kt:81)
	... 10 more
Caused by: j$.time.format.DateTimeParseException: Text cannot be parsed to a Duration
	at j$.time.Duration.parse(SourceFile:5)
	at net.fortuna.ical4j.model.TemporalAmountAdapter.parse(TemporalAmountAdapter.java:145)
	at net.fortuna.ical4j.model.TemporalAmountAdapter.parse(TemporalAmountAdapter.java:132)
	at net.fortuna.ical4j.model.property.Trigger.setValue(Trigger.java:253)
	at net.fortuna.ical4j.model.property.Trigger.<init>(Trigger.java:166)
	at net.fortuna.ical4j.model.property.Trigger$Factory.createProperty(Trigger.java:301)
	at net.fortuna.ical4j.model.property.Trigger$Factory.createProperty(Trigger.java:291)
	at net.fortuna.ical4j.model.PropertyBuilder.build(PropertyBuilder.java:76)
	at net.fortuna.ical4j.data.DefaultContentHandler.endProperty(DefaultContentHandler.java:159)
	at net.fortuna.ical4j.data.CalendarParserImpl$PropertyParser.parse(CalendarParserImpl.java:309)
	at net.fortuna.ical4j.data.CalendarParserImpl$PropertyParser.access$1100(CalendarParserImpl.java:241)
	at net.fortuna.ical4j.data.CalendarParserImpl$PropertyListParser.parse(CalendarParserImpl.java:226)
	at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.parse(CalendarParserImpl.java:446)
	at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.access$900(CalendarParserImpl.java:422)
	at net.fortuna.ical4j.data.CalendarParserImpl$PropertyListParser.parse(CalendarParserImpl.java:224)
	at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.parse(CalendarParserImpl.java:446)
	at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.access$900(CalendarParserImpl.java:422)
	at net.fortuna.ical4j.data.CalendarParserImpl$PropertyListParser.parse(CalendarParserImpl.java:224)
	at net.fortuna.ical4j.data.CalendarParserImpl.parseCalendar(CalendarParserImpl.java:128)
	at net.fortuna.ical4j.data.CalendarParserImpl.parseCalendarList(CalendarParserImpl.java:194)
	at net.fortuna.ical4j.data.CalendarParserImpl.parse(CalendarParserImpl.java:163)
	... 13 more

Answered by rfc2822

Apr 25, 2023

ACKNOWLEDGED::20230422T070339Z

This is an invalid format. Correct would be ACKNOWLEDGED:20230422T070339Z. Thus :20230422T070339Z has to be parsed as date, so the error occurs.

Please fix the iCalendar on server side.

View full answer

rfc2822 · 2023-02-25T10:19:19Z

rfc2822
Feb 25, 2023
Maintainer

Hi,

Your eCal event is broken. We have included some workarounds for broken versions in the next version, which is currently in beta. Do you have ICSx⁵ from Google Play?

3 replies

Brog33 Feb 25, 2023
Author

Ok! I managed to sync the calendar in Google Calendar and Proton Calendar without a hitch, so I didn't think it was broken.

Got ICSx5 from F-Droid (somehow Google refuse my bank card so I looked for alternatives).

rfc2822 Feb 25, 2023
Maintainer

Ok! I managed to sync the calendar in Google Calendar and Proton Calendar without a hitch, so I didn't think it was broken.

Got ICSx5 from F-Droid (somehow Google refuse my bank card so I looked for alternatives).

We'll release the next version in the next days, hopefully it will then work for your calendar, too.

Brog33 Feb 25, 2023
Author

Great! Looking forward to it. Will report back then.

Brog33 · 2023-02-27T08:28:53Z

Brog33
Feb 27, 2023
Author

Installed the 2.1 apk from github and it correctly added "English Premier League" to My subscriptions. But it says "not synchronized yet", and it's been like that for a while. I've tried to set the sync interval to every 15 minutes and then only manually. However there is no manual sync button there? I have disabled the battery optimizer for the app, and sync is enabled for the app in android's accounts settings, so idk why it doesn't sync.

Maybe I'm missing something crucial here? :)

7 replies

Brog33 Feb 27, 2023
Author

Perhaps I could provide some debug info, or feel free to try to sync the URL yourself :)

rfc2822 Feb 27, 2023
Maintainer

Strange, syncing works here. @ArnyminerZ Do you have an idea?

ArnyminerZ Feb 27, 2023
Maintainer

I'm having the same issue with all of my Subscriptions, noticed this morning. I'll take a look asap

ArnyminerZ Feb 27, 2023
Maintainer

For some reason the provider is not inserting the calendar entries.

ArnyminerZ Feb 27, 2023
Maintainer

I have created #129

Brog33 · 2023-03-01T06:45:43Z

Brog33
Mar 1, 2023
Author

Installed v2.1.1-rc.1 and can confirm it works now! Good job!

0 replies

drahnr · 2023-04-25T07:56:02Z

drahnr
Apr 25, 2023

I am using https://posteo.de and on a ONEPLUS A5010 with Android 10, I am getting parsing errors still. APK retrieved from google play, Version 2.1.1-gplay.

Whe retrieving with curl -L https://posteo.de/../ics/... it starts with

BEGIN:VCALENDAR
PRODID;X-RICAL-TZSOURCE=TZINFO:-//com.denhaven2/NONSGML ri_cal gem//EN
CALSCALE:GREGORIAN
VERSION:2.0
BEGIN:VTIMEZONE
TZID;X-RICAL-TZSOURCE=TZINFO:Europe/Berlin
BEGIN:STANDARD
DTSTART:20221020T030000
RDATE:20221020T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20230226T020000
RDATE:20230226T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTEND;TZID=Europe/Berlin;VALUE=DATE-TIME:20230215T100000
STATUS:CONFIRMED
DTSTART;TZID=Europe/Berlin;VALUE=DATE-TIME:20230215T090000
DTSTAMP;VALUE=DATE-TIME:20230210T135628Z
UID:040000008200E00074C5B7101A82E0080000000040EF6E6F5F53D9010000000000000
 000100000009378A991E47ED345A67DEA50F38E4B81
DESCRIPTION:xyz\n[cid:[email protected]
 8780]\n
 il: +123 9 |  Tel.: +123 0  |  Fax: +123 1
 \[email protected]<mailto:[email protected]>
SUMMARY: Foo
LOCATION: None of your darn business
END:VEVENT
BEGIN:VEVENT
DTEND;TZID=Europe/Berlin;VALUE=DATE-TIME:20230423T003000
STATUS:CONFIRMED
...

the resulting ICSx5 error is:

Couldn't parse iCalendar

at.bitfire.ical4android.InvalidCalendarException: Couldn't parse iCalendar
	at at.bitfire.ical4android.ICalendar$Companion.fromReader(ICalendar.kt:91)
	at at.bitfire.ical4android.Event$Companion.eventsFromReader(Event.kt:79)
	at at.bitfire.icsdroid.ui.AddCalendarValidationFragment$ValidationModel$validate$downloader$1.onSuccess(AddCalendarValidationFragment.kt:126)
	at at.bitfire.icsdroid.CalendarFetcher.fetchNetwork$icsx5_72_2_1_1_gplayRelease(CalendarFetcher.kt:157)
	at at.bitfire.icsdroid.CalendarFetcher$fetchNetwork$1.invokeSuspend(CalendarFetcher.kt:0)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
Caused by: net.fortuna.ical4j.data.ParserException: Error at line 646:Unparseable date: ":20230422T070339Z"
	at net.fortuna.ical4j.data.CalendarParserImpl.parse(CalendarParserImpl.java:172)
	at net.fortuna.ical4j.data.CalendarBuilder.build(CalendarBuilder.java:197)
	at net.fortuna.ical4j.data.CalendarBuilder.build(CalendarBuilder.java:185)
	at at.bitfire.ical4android.ICalendar$Companion.fromReader(ICalendar.kt:89)
	... 10 more
Caused by: java.text.ParseException: Unparseable date: ":20230422T070339Z"
	at java.text.DateFormat.parse(DateFormat.java:362)
	at net.fortuna.ical4j.model.DateTime.setTime(DateTime.java:418)
	at net.fortuna.ical4j.model.DateTime.<init>(DateTime.java:349)
	at net.fortuna.ical4j.model.property.DateProperty.setValue(DateProperty.java:140)
	at net.fortuna.ical4j.model.property.Acknowledged.<init>(Acknowledged.java:100)
	at net.fortuna.ical4j.model.property.Acknowledged.<init>(Acknowledged.java:69)
	at net.fortuna.ical4j.model.property.Acknowledged$Factory.createProperty(Acknowledged.java:134)
	at net.fortuna.ical4j.model.property.Acknowledged$Factory.createProperty(Acknowledged.java:124)
	at net.fortuna.ical4j.model.PropertyBuilder.build(PropertyBuilder.java:76)
	at net.fortuna.ical4j.data.DefaultContentHandler.endProperty(DefaultContentHandler.java:159)
	at net.fortuna.ical4j.data.CalendarParserImpl$PropertyParser.parse(CalendarParserImpl.java:309)
	at net.fortuna.ical4j.data.CalendarParserImpl$PropertyParser.access$1100(CalendarParserImpl.java:241)
	at net.fortuna.ical4j.data.CalendarParserImpl$PropertyListParser.parse(CalendarParserImpl.java:226)
	at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.parse(CalendarParserImpl.java:446)
	at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.access$900(CalendarParserImpl.java:422)
	at net.fortuna.ical4j.data.CalendarParserImpl$PropertyListParser.parse(CalendarParserImpl.java:224)
	at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.parse(CalendarParserImpl.java:446)
	at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.access$900(CalendarParserImpl.java:422)
	at net.fortuna.ical4j.data.CalendarParserImpl$PropertyListParser.parse(CalendarParserImpl.java:224)
	at net.fortuna.ical4j.data.CalendarParserImpl.parseCalendar(CalendarParserImpl.java:128)
	at net.fortuna.ical4j.data.CalendarParserImpl.parseCalendarList(CalendarParserImpl.java:194)
	at net.fortuna.ical4j.data.CalendarParserImpl.parse(CalendarParserImpl.java:163)
	... 13 more

10 replies

drahnr Apr 25, 2023

What do you mean which URL?

EDIT: An empty dummy calendar feed https://posteo.de/calendars/ics/5d3cjc6win7jggkv1kydn21wjvahex28
EDIT: Added one event for today

BEGIN:VCALENDAR
PRODID;X-RICAL-TZSOURCE=TZINFO:-//com.denhaven2/NONSGML ri_cal gem//EN
CALSCALE:GREGORIAN
VERSION:2.0
BEGIN:VEVENT
DTEND;VALUE=DATE-TIME:20230425T084500Z
DTSTART;VALUE=DATE-TIME:20230425T083000Z
DTSTAMP;VALUE=DATE-TIME:20230425T080507Z
CATEGORIES:Keine
UID:4a1c81d3857fc8815b678aef7d01686b-Paaf9vI
DESCRIPTION:+123 | ABC\nTEST [email protected]
SUMMARY:borksed
LOCATION:Virgin Islands
SEQUENCE:1682409907
END:VEVENT
END:VCALENDAR

rfc2822 Apr 25, 2023
Maintainer

What do you mean which URL?

Sorry I thought your posting was related to the original topic of the discussion. Seems that it is a completely different problem; unfortunately, Github has no split discussion function. :(

The error message:

Caused by: net.fortuna.ical4j.data.ParserException: Error at line 646:Unparseable date: ":20230422T070339Z"

Looks like there is something like DTSTART::20230422T070339Z in line 646 of your calendar. Can you please provide the lines around line 646?

drahnr Apr 25, 2023

The relevant lines with some context. There is no ACKNOWLEDGED::20230422T070339Z in line 646.

 630   │ ACTION:DISPLAY
 631   │ END:VALARM
 632   │ END:VEVENT
 633   │ BEGIN:VEVENT
 634   │ DTEND;TZID=Europe/Berlin;VALUE=DATE-TIME:20230421T190000
 635   │ STATUS:CONFIRMED
 636   │ DTSTART;TZID=Europe/Berlin;VALUE=DATE-TIME:20230421T180000
 637   │ DTSTAMP;VALUE=DATE-TIME:20230415T193409Z
 638   │ LAST-MODIFIED;VALUE=DATE-TIME:20230422T070339Z
 639   │ UID:ee123f4a-8421-4b60-a312-225d61cabf0f
 640   │ SUMMARY:Foobar
 641   │ BEGIN:VALARM
 642   │ TRIGGER;RELATED=START:-PT15M
 643   │ DESCRIPTION:Baz
 644   │ ACTION:DISPLAY
 645   │ X-EVOLUTION-ALARM-UID::38cda30d31b13ccbe5a6c28ba011b99a803f7041
 646   │ ACKNOWLEDGED::20230422T070339Z
 647   │ END:VALARM
 648   │ END:VEVENT
 649   │ BEGIN:VEVENT
 650   │ DTEND;VALUE=DATE:20230626
 651   │ STATUS:CONFIRMED
 652   │ DTSTART;VALUE=DATE:20230622
 653   │ DTSTAMP;VALUE=DATE-TIME:20230223T213628Z
 654   │ UID:f8b267d4-1b57-41f2-bdb3-fd00e4be6467
 655   │ SUMMARY:Whatever
 656   │ END:VEVENT
 657   │ BEGIN:VEVENT
 658   │ DTEND;VALUE=DATE:20231014
 659   │ STATUS:CONFIRMED

rfc2822 Apr 25, 2023
Maintainer

ACKNOWLEDGED::20230422T070339Z

This is an invalid format. Correct would be ACKNOWLEDGED:20230422T070339Z. Thus :20230422T070339Z has to be parsed as date, so the error occurs.

Please fix the iCalendar on server side.

Answer selected by rfc2822

drahnr Apr 25, 2023

@rfc2822 thank you for looking into it and my apologies for hijacking. I'll contact my provider 🤞

slava-nat May 6, 2023

I get the very same error Unparseable date: ":20230427T125536Z" also with calendars on https://posteo.de/.

However, when I tried to subscribe to my Posteo calendar in Google Calendar or Apple Calendar, everything went smoothly. It is a bit strange that they both parse the calendar correctly. But maybe Google and Apple just ignore the ACKNOWLEDGED field. So, maybe ICSx5 should also ignore this? Or at least raise a warning and not an error?

Moreover, I used the calendar validation tool from the official iCalendar website (https://icalendar.org/validator.html) and it firstly found an error, but surprisingly not with the wrong date format but with the wrong line delimiters (the file had LF but must have CRLF). After changing LF to CRLF the file goes successfully trough the validation tool.

I am also going to write to the Posteo Support and explain the error. With the second complain maybe they will take it a bit more seriously 😄

For those interested, here is the link to the RFC 9074 standard, which explains the valid format for the field ACKNOWLEDGED:
https://datatracker.ietf.org/doc/html/rfc9074#name-acknowledged-property

rfc2822 May 7, 2023
Maintainer

So, maybe ICSx5 should also ignore this? Or at least raise a warning and not an error?

I wish we could do that. However we use the ical4j library to parse iCalendars, and that library throws errors on invalid data (although there are already less strict modes, which we use).

ical4j has recently been improved in that matter: ical4j/ical4j#454 – I hope it will also reduce errors like yours.

(The real error is still the invalid iCalendar and it should be fixed even if invalid values are ignored one day.)

drahnr May 8, 2023

@rfc2822 thank you for looking into it and my apologies for hijacking. I'll contact my provider crossed_fingers

For the record, I got a response and their SW dep will look into, I didn't have time to look into it, and I probably won't, since I had to move providers for calendar

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Couldn't parse iCalendar - debug included #123

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments 20 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

Error: Couldn't parse iCalendar - debug included #123

Brog33 Feb 24, 2023

Replies: 4 comments · 20 replies

rfc2822 Feb 25, 2023 Maintainer

Brog33 Feb 25, 2023 Author

rfc2822 Feb 25, 2023 Maintainer

Brog33 Feb 25, 2023 Author

Brog33 Feb 27, 2023 Author

Brog33 Feb 27, 2023 Author

rfc2822 Feb 27, 2023 Maintainer

ArnyminerZ Feb 27, 2023 Maintainer

ArnyminerZ Feb 27, 2023 Maintainer

ArnyminerZ Feb 27, 2023 Maintainer

Brog33 Mar 1, 2023 Author

drahnr Apr 25, 2023

drahnr Apr 25, 2023

rfc2822 Apr 25, 2023 Maintainer

drahnr Apr 25, 2023

rfc2822 Apr 25, 2023 Maintainer

drahnr Apr 25, 2023

slava-nat May 6, 2023

rfc2822 May 7, 2023 Maintainer

drahnr May 8, 2023

Brog33
Feb 24, 2023

Replies: 4 comments 20 replies

rfc2822
Feb 25, 2023
Maintainer

Brog33 Feb 25, 2023
Author

rfc2822 Feb 25, 2023
Maintainer

Brog33 Feb 25, 2023
Author

Brog33
Feb 27, 2023
Author

Brog33 Feb 27, 2023
Author

rfc2822 Feb 27, 2023
Maintainer

ArnyminerZ Feb 27, 2023
Maintainer

ArnyminerZ Feb 27, 2023
Maintainer

ArnyminerZ Feb 27, 2023
Maintainer

Brog33
Mar 1, 2023
Author

drahnr
Apr 25, 2023

rfc2822 Apr 25, 2023
Maintainer

rfc2822 Apr 25, 2023
Maintainer

rfc2822 May 7, 2023
Maintainer