Couldn't parse iCalendar / Text cannot be parsed to a Duration

[shoneg]

Hey everyone,
I'm getting the following error for some weeks:

EXCEPTION at.bitfire.ical4android.InvalidCalendarException: Couldn't parse iCalendar
  at at.bitfire.ical4android.ICalendar$Companion.fromReader(ICalendar.kt:143)
  at at.bitfire.ical4android.ICalendar$Companion.fromReader$default(ICalendar.kt:6)
  at at.bitfire.ical4android.Task$Companion.tasksFromReader(Task.kt:10)
  at at.bitfire.davdroid.sync.TasksSyncManager.processVTodo(TasksSyncManager.kt:3)
  at at.bitfire.davdroid.sync.TasksSyncManager.downloadRemote$lambda$7$lambda$6$lambda$5(TasksSyncManager.kt:96)
  at at.bitfire.davdroid.sync.TasksSyncManager.$r8$lambda$_eXCc6mGtZGmx812Cf4KQ973ya4(TasksSyncManager.kt:1)
  at at.bitfire.davdroid.sync.TasksSyncManager$$ExternalSyntheticLambda6.invoke(R8$$SyntheticClass:5)
  at at.bitfire.davdroid.sync.SyncException$Companion.wrapWithRemoteResource(SyncException.kt:6)
  at at.bitfire.davdroid.sync.TasksSyncManager.downloadRemote$lambda$7$lambda$6(TasksSyncManager.kt:22)
  at at.bitfire.davdroid.sync.TasksSyncManager.$r8$lambda$je_KUSDj0piNK8t4YaP8Z5kkUM4(TasksSyncManager.kt:1)
  at at.bitfire.davdroid.sync.TasksSyncManager$$ExternalSyntheticLambda1.onResponse(R8$$SyntheticClass:3)
  at at.bitfire.dav4jvm.Response$Companion.parse(Response.kt:321)
  at at.bitfire.dav4jvm.DavResource.processMultiStatus$parseMultiStatus(DavResource.kt:51)
  at at.bitfire.dav4jvm.DavResource.processMultiStatus(DavResource.kt:16)
  at at.bitfire.dav4jvm.DavResource.processMultiStatus(DavResource.kt:9)
  at at.bitfire.dav4jvm.DavCalendar.multiget(DavCalendar.kt:69)
  at at.bitfire.dav4jvm.DavCalendar.multiget$default(DavCalendar.kt:12)
  at at.bitfire.davdroid.sync.TasksSyncManager.downloadRemote$lambda$7(TasksSyncManager.kt:18)
  at at.bitfire.davdroid.sync.TasksSyncManager.$r8$lambda$kgXEXj4wzX3jY3Qka2brMmyDl44(TasksSyncManager.kt:1)
  at at.bitfire.davdroid.sync.TasksSyncManager$$ExternalSyntheticLambda3.invoke(R8$$SyntheticClass:5)
  at at.bitfire.davdroid.sync.SyncException$Companion.wrapWithRemoteResource(SyncException.kt:6)
  at at.bitfire.davdroid.sync.TasksSyncManager.downloadRemote(TasksSyncManager.kt:54)
  at at.bitfire.davdroid.sync.SyncManager$syncRemote$1$download$1.invokeSuspend(SyncManager.kt:14)
  at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
  at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:107)
  at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:76)
  at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source:105)
  at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source:3)
  at at.bitfire.davdroid.sync.SyncManager.syncRemote(SyncManager.kt:39)
  at at.bitfire.davdroid.sync.SyncManager.performSync(SyncManager.kt:428)
  at at.bitfire.davdroid.sync.TaskSyncer.syncCollection(TaskSyncer.kt:11)
  at at.bitfire.davdroid.sync.TaskSyncer.syncCollection(TaskSyncer.kt:1)
  at at.bitfire.davdroid.sync.Syncer.syncCollectionContents$davx5_ose_4_4_4_oseRelease(Syncer.kt:59)
  at at.bitfire.davdroid.sync.Syncer.sync$davx5_ose_4_4_4_oseRelease(Syncer.kt:42)
  at at.bitfire.davdroid.sync.Syncer.invoke(Syncer.kt:144)
  at at.bitfire.davdroid.sync.worker.BaseSyncWorker$doSyncWork$2.invokeSuspend$lambda$0(BaseSyncWorker.kt:1)
  at at.bitfire.davdroid.sync.worker.BaseSyncWorker$doSyncWork$2.$r8$lambda$MnrEU1_WtQZTTPjmMRztfG3Y7fo(BaseSyncWorker.kt:1)
  at at.bitfire.davdroid.sync.worker.BaseSyncWorker$doSyncWork$2$$ExternalSyntheticLambda0.invoke(R8$$SyntheticClass:3)
  at kotlinx.coroutines.InterruptibleKt$runInterruptible$2.invokeSuspend(Interruptible.kt:58)
  at kotlinx.coroutines.InterruptibleKt$runInterruptible$2.invoke(Interruptible.kt:13)
  at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:5)
  at kotlinx.coroutines.BuildersKt.withContext(Unknown Source:44)
  at kotlinx.coroutines.InterruptibleKt.runInterruptible$default(Interruptible.kt:9)
  at at.bitfire.davdroid.sync.worker.BaseSyncWorker$doSyncWork$2.invokeSuspend(BaseSyncWorker.kt:341)
  at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
  at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:107)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
  at java.lang.Thread.run(Thread.java:919)
Caused by: net.fortuna.ical4j.data.ParserException: Error at line 36:Text cannot be parsed to a Duration
  at net.fortuna.ical4j.data.CalendarParserImpl.parse(CalendarParserImpl.java:17)
  at net.fortuna.ical4j.data.CalendarBuilder.build(CalendarBuilder.java:3)
  at net.fortuna.ical4j.data.CalendarBuilder.build(CalendarBuilder.java:2)
  at at.bitfire.ical4android.ICalendar$Companion.fromReader(ICalendar.kt:59)  ... 48 more
Caused by: j$.time.format.DateTimeParseException: Text cannot be parsed to a Duration
  at j$.time.Duration.parse(SourceFile:417)
  at net.fortuna.ical4j.model.TemporalAmountAdapter.parse(TemporalAmountAdapter.java:8)
  at net.fortuna.ical4j.model.TemporalAmountAdapter.parse(TemporalAmountAdapter.java:1)
  at net.fortuna.ical4j.model.property.Trigger.setValue(Trigger.java:8)
  at net.fortuna.ical4j.model.property.Trigger.<init>(Trigger.java:3)
  at net.fortuna.ical4j.model.property.Trigger$Factory.createProperty(Trigger.java:3)
  at net.fortuna.ical4j.model.property.Trigger$Factory.createProperty(Trigger.java:2)
  at net.fortuna.ical4j.model.PropertyBuilder.build(PropertyBuilder.java:43)
  at net.fortuna.ical4j.data.DefaultContentHandler.endProperty(DefaultContentHandler.java:24)
  at net.fortuna.ical4j.data.CalendarParserImpl$PropertyParser.parse(CalendarParserImpl.java:98)
  at net.fortuna.ical4j.data.CalendarParserImpl$PropertyParser.access$1100(CalendarParserImpl.java:1)
  at net.fortuna.ical4j.data.CalendarParserImpl$PropertyListParser.parse(CalendarParserImpl.java:47)
  at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.parse(CalendarParserImpl.java:37)
  at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.access$900(CalendarParserImpl.java:1)
  at net.fortuna.ical4j.data.CalendarParserImpl$PropertyListParser.parse(CalendarParserImpl.java:33)
  at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.parse(CalendarParserImpl.java:37)
  at net.fortuna.ical4j.data.CalendarParserImpl$ComponentParser.access$900(CalendarParserImpl.java:1)
  at net.fortuna.ical4j.data.CalendarParserImpl$PropertyListParser.parse(CalendarParserImpl.java:33)
  at net.fortuna.ical4j.data.CalendarParserImpl.parseCalendar(CalendarParserImpl.java:29)
  at net.fortuna.ical4j.data.CalendarParserImpl.parseCalendarList(CalendarParserImpl.java:15)
  at net.fortuna.ical4j.data.CalendarParserImpl.parse(CalendarParserImpl.java:13)  ... 51 more

I'd like to not present the whole ics file here, because it's more than 7000 lines long and includes many private tasks.

I'm aware of discussion #505 but I made sure that my ics doesn't contain a similar problem.

[sunkup]

You can send the ics file and a short explanation of the problem with link to this discussion to [email protected]. Then we can take a look without you having to show the file here.

[rfc2822]

at net.fortuna.ical4j.model.property.Trigger.setValue(Trigger.java:8)

It seems in any case be an alarm TRIGGER with a wrong duration.

[shoneg]

It seems in any case be an alarm TRIGGER with a wrong duration.

Hi rfc2822,
Thanks for your answer. I have searched for "trigger" in the whole ICS-file and these are all occurrences:

TRIGGER:-P1WT2H
TRIGGER:-PT2H
TRIGGER:-PT15M
TRIGGER:-P1WT2H
TRIGGER:-PT2H
TRIGGER:-PT15M
TRIGGER:-P1WT2H
TRIGGER:-PT2H
TRIGGER:-PT15M

I don't see any problem here. Do you see one or could the error be under another keyword?

[rfc2822]

TRIGGER:-P1WT2H

According to RFC 5545, DURATION can be

       dur-value  = (["+"] / "-") "P" (dur-date / dur-time / dur-week)

       dur-date   = dur-day [dur-time]
       dur-time   = "T" (dur-hour / dur-minute / dur-second)
       dur-week   = 1*DIGIT "W"
       dur-hour   = 1*DIGIT "H" [dur-minute]
       dur-minute = 1*DIGIT "M" [dur-second]
       dur-second = 1*DIGIT "S"
       dur-day    = 1*DIGIT "D"

So it can either be -P1W or P-T2H, but weeks and hours cannot be combined.