davx5 ignores when the user is invited to a single event of a recurrent serie

[ArnY]

Hello,

Not sure this is the proper way of reporting bugs, if not, sorry about that.

We noticed today that when a user is invited to a single instance of a recurrent event by the owner of the event, while the exceptional event shows properly in the user's calendar in Zimbra or Thunderbird, davx5 ignores it and the event never shows up in the user's calendar on Android. In the log file:

03-23 13:59:51.303 3080 6158 I davx5 : [syncadapter.CalendarSyncManager] Received VCALENDAR with not exactly one VEVENT with UID and without RECURRENCE-ID; ignoring 000eaace-36f8-4351-ad21-321f4f0e56f3.ics

I'm using davx5 4.2.0.1-ose with Zimbra.

Arnaud

[devvv4ever]

Hello Arnaud,

thank you. This is a complicated bug - that has appeared a few times lately. We don't know why this suddenly appears because we did not change anything in the last years here... Can you provide more details on how the recurring event got to Zimbra? Was it imported via Outlook or something like this? Is this reproducible on your Zimbra? Can you provide a test instance on your Zimbra maybe?

Bug is already tracked internally here for reference: https://github.com/bitfireAT/davx5/issues/58

Thanks!

[devvv4ever]

Additional question: Is this a real use or did this happen when testing very special use cases?

[ArnY]

This is a real use case. My manager actually missed a meeting (gasp!) because he had been exceptionally invited into one meeting of a recurrent serie that didn't show up in his phone's agenda.

After he reported the problem to me, I actually created a recurrent event using a test account in our zimbra and invited myself into one, creating an exception to the serie and noticed that davx5 never picked it up just as it happened to my manager. So there's no import or anything involved there.

The one thing is that we are using a old zimbra version 6.0 (we are actually in the process of replacing it, but without any ETA yet) and it could be related to this. I could indeed provide a test account if it can help fixing the problem and if you can provide an email for me to send the details.

Thanks.

[devvv4ever]

We could identify and reproduce it internally now, but thanks! We've made a fix for this and hopefully it works with the next version. Can I send you the apk so that you test your case on your server and tell me if it works? You'll find the email at the top of @bitfireAT Thanks!