Cannot convert XProperty to Uid

[TheIvan]

I’m getting the error

net.fortuna.ical4j.model.property.XProperty cannot be cast to net.fortuna.ical4j.model.property.Uid

on 1.8.3 from this public URL: https://www.yi-zentrum.at/veranstaltungen/list/?ical=1&tribe_display=list

I tried to downgrade via F-Droid, but it didn’t work. I don’t recall if this error started happening after a recent update.

[rfc2822]

Hello,

Is there a way to reproduce this? Which Android version etc. did you use? Does the error always appear or only sometimes etc? We need much more information, becuase this Webcal URL works with ICSx⁵ here without problems.

[TheIvan]

I could reproduce this 100% of the time during the last two days, but today it works!

Android Version is 7.0, Baseband Verison G920FXXU6ERF6, Kernel Verison 3.10.61-13830439, Build Number NRD90M, Security Patch level 1 June 2018

[rfc2822]

@TheIvan Thanks for the update. If you can find a way to reproduce the problem, just let us know.

[rfc2822]

Does reinstalling ICSx5 work around the problem?

[sprickw]

@TheIvan @rfc2822 Same problem persists with me for days, Android 7.0.

[sprickw]

@sprickw Version 1.8.4 as of yesterday fixed the problem, tx tx tx.

[TheIvan]

Reinstalling does not work around the problem.
The only thing that helps is rebooting my phone.
The error does not occure more often than once every 1-2 weeks.

[rfc2822]

Is it possible that the server sends an invalid feed 1 – 2 times a week?

[TheIvan]

@rfc2822 If that were the case, then a refresh or restart of the app would fix the issue, but the only thing that helps is a reboot.

[rfc2822]

I see. Unfortunately, I can’t say anything more about this unless I’m able to reproduce the problem. I use ICSx⁵ for myself but I have never seen this message.

[sprickw]

@rfc2822 I installed version 1.8.4 as of yesterday this morning and everything ist fine again. tx

[sprickw]

@rfc2822 I also use the calender with nextcloud and evolution (linux desktop) and had no problems.

[TheIvan]

@sprickw @rfc2822 I’ll try to go from 1.8.3. to 1.8.4 and see if this removes the problem (I had it again yesterday)