fix: replace broken trigger duration string before prasing

[SebastianKrupinski]

Resolves: #10788

[kesselb]

The reason for #10788 is therefore nextcloud/calendar-js#790?

Can you still reproduce the issue on main and if yes, is it a different error message? If so, then the patch for calendar-js did not cover all cases.

Could you please invite Richard and me to such an outlook event?

[SebastianKrupinski]

The reason for #10788 is therefore nextcloud/calendar-js#790?

Ah... I didn't know that you had already been working on this.

Can you still reproduce the issue on main and if yes, is it a different error message? If so, then the patch for calendar-js did not cover all cases.

Yes, I reproduced it yesterday, while looking in to another issue.

Could you please invite Richard and me to such an outlook event?

Sure.

[kesselb]

Your invitation works for me.

Could you retry after running git switch main; git pull; npm ci; npm run dev?

[SebastianKrupinski]

Your invitation works for me.

Could you retry after running git switch main; git pull; npm ci; npm run dev?

Npm CI made the difference. I don't usually run this.

All good now, closing this PR.

[kesselb]

@SebastianKrupinski 👍

So it's fixed for main and stable4.3, but not for stable4.2. I assume it's possible to also backport the calendar-js update to stable4.2, but that's something for @ChristophWurst to decide. If backporting it not an option, we can still apply this change to stable4.2.

[ChristophWurst]

Let's backport