Every appointment is a group appointment

[Marc246]

Thanks for this statement.
I would agree. Sounds interesting what you have found. I think it should be set to true too. Your arguments are understandable and i would say we should test it with this solution. Is this workaround implemented in the DavDroid Version 0.9.1?

Best regards,
Marc

[rfc2822]

@Marc246 said:

Is this workaround implemented in the DavDroid Version 0.9.1?

If the second interpretation is true (and I believe so), it’s not even a workaround. And it’s implemented in DAVdroid 0.9.1, but it will of course only be applied to events received after updating to 0.9.1 (i.e. not for events that are already in the calendar provider).

Can you please verify this?

[Marc246]

@rfc2822
Bad news.
It doesn’t work with DavDroid 0.9.1.

This is the content of my .ics file

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN
BEGIN:VTIMEZONE
TZID:Europe/Berlin
TZURL:http://tzurl.org/zoneinfo/Europe/Berlin
END:VTIMEZONE
BEGIN:VEVENT
CLASS:PUBLIC
CREATED:20151112T073836
DESCRIPTION:
DTEND;TZID="Europe/Berlin;":20151112T081500
DTSTAMP:20151112T073836
DTSTART;TZID="Europe/Berlin;":20151112T074500
LAST-MODIFIED:20151112T073836
LOCATION:
ORGANIZER;CN=XXX:mailto:XXX
PRIORITY:1
SEQUENCE:1
STATUS:Tentative
SUMMARY:test123
UID:770F1ED52A27483EB6E01F610CF9F1B8
END:VEVENT
END:VCALENDAR

Is it possible that the problem is the organizer?
This event is created in another client and the DavDroid account on our test client was recreated.

Any other tips?

Thank you in advance.

Best regards,
Marc

[rfc2822]

@Marc246 It works here (just tested again to be sure). Is the organizer email address your account name?

Also, I have tested with Etar. Maybe other calendar apps (S Planner) don’t behave like that.

Is your device rooted? Then you could have a look whether HAS_ATTENDEE_DATA is set to 1 directly in the database.

[Marc246]

@rfc2822 The organizer email address and my account name are different.

My device is rooted. Can you send me via chat short instructions to look for the HAS_ATTENDEE_DATA ?

[rfc2822]

@Marc246 said:

@rfc2822 The organizer email address and my account name are different.

In this case, the response radio group is always shown, see case 2 in my list above: »I.e. the response radio group will always appear if the user is not the organizer (makes sense, because if the user is not the organizer, (s)he must be another participant and is thus eligible to respond).«

My device is rooted. Can you send me via chat short instructions to look for the HAS_ATTENDEE_DATA ?

I guess this is not required anymore, but it’s always fun. Just use your file manager (with root) to copy /data/data/com.android.providers.calendar/databases/calendar.db to the external storage (or fetch it with root adb), then send it to your PC and open it with an SQLite GUI.

[Marc246]

@rfc2822 said:

@Marc246 said:

@rfc2822 The organizer email address and my account name are different.

In this case, the response radio group is always shown, see case 2 in my list above: »I.e. the response radio group will always appear if the user is not the organizer (makes sense, because if the user is not the organizer, (s)he must be another participant and is thus eligible to respond).«

Now i tested it with the same value for the organizer and for the account - but i get still the display of accepting or declining the event.

My device is rooted. Can you send me via chat short instructions to look for the HAS_ATTENDEE_DATA ?

I guess this is not required anymore, but it’s always fun. Just use your file manager (with root) to copy /data/data/com.android.providers.calendar/databases/calendar.db to the external storage (or fetch it with root adb), then send it to your PC and open it with an SQLite GUI.

I think i have to test this proposal. Maybe i will test also that i remove the organizer for a normal event.

[rfc2822]

Now i tested it with the same value for the organizer and for the account - but i get still the display of accepting or declining the event.

That’s strange, because it works here as expected. What’s your account name, and what’s your organizer? Did you create a new event with ORGANIZER:mailto:accountname?

[Marc246]

Ok sorry that was my fault.
There was a trailing whitespace in the organizername.
Now it works! Thank you @rfc2822

Edit: I can’t set the thread to solved.

[devvv4ever]

Thanks for the update and telling us the cause of the problem