Can't accept calendar event
-
Hi @amaccuish,
the issue is that the device sends meeting response to the calendar entry id instead of meeting request id. In alex-[devid].log line 101 is the calendar entry id (Uc4693:…). At line 473 there’s meeting request id (Ued522:…). Meeting response starting at line 1304 sends ids of the calendar folder and the calendar item instead of the ids of the inbox and the meeting request.
We’ll test if it’s possible to workaround this issue.
Manfred
-
Hi @Manfred
Thanks for the quick response. If you need anything tested let me know!
In the meantime, the Outlook app seems to handle meeting requests fine :)
Alex
-
@Manfred also I don’t know if it’s relevant but re responding to the calendar item and not meeting request, I’m accepting the meeting request from the calendar app on iOS and not from the email app. It has its own “inbox” and shows requests from the mail app.
-
@amaccuish said in Can't accept calendar event:
@Manfred also I don’t know if it’s relevant but re responding to the calendar item and not meeting request, I’m accepting the meeting request from the calendar app on iOS and not from the email app. It has its own “inbox” and shows requests from the mail app.
just as a follow up for good measure, the same error happens if I accept from the email and not from the calendar app
-
Hi @amaccuish,
I’ve created a JIRA issue to track this: https://jira.z-hub.io/browse/ZP-1524. If you want to test a fix, here’s the link to the commit: https://stash.z-hub.io/projects/ZP/repos/z-push/commits/413d10986f7bfccf977cb972af4403c0bf9cab54.
Manfred
-
I’ll have a go shortly! :)
-
Ok so that’s fixed it. A few things to note.
I noticed on the bug report you said the accepted email is not sent: "Additionally those devices seem not to send the accepted email anymore. " It does still seem to be sent and received on the inviter phone.
Second, before the acceptance arrives to the inviter, the phone displays a “scheduling conflict”, which then is replaced with a tick when the meeting response arrives.
Finally, these errors were logged:
24/09/2019 20:47:58 [32230] [WARN] [cashmere] SyncAppointment->Check(): Parameter 'organizername' and 'organizeremail' should be set for a meeting request 24/09/2019 20:48:24 [ 6927] [WARN] [cashmere] /usr/share/z-push/backend/kopano/kopano.php:2629 Uninitialized string offset: 337 (8) 24/09/2019 20:48:24 [ 6927] [WARN] [cashmere] /usr/share/z-push/backend/kopano/kopano.php:2629 Uninitialized string offset: 338 (8) 24/09/2019 20:48:24 [ 6927] [WARN] [cashmere] /usr/share/z-push/backend/kopano/kopano.php:2629 Uninitialized string offset: 339 (8) 24/09/2019 20:48:24 [ 6927] [WARN] [cashmere] /usr/share/z-push/backend/kopano/kopano.php:2629 Uninitialized string offset: 340 (8)Hope that helps!
EDIT: changing the meeting response does not work and displays the same error.
-
Hi amaccuish,
@amaccuish said in Can't accept calendar event:
I noticed on the bug report you said the accepted email is not sent: "Additionally those devices seem not to send the accepted email anymore. " It does still seem to be sent and received on the inviter phone.
The organizer receives the accepted email because I added a fix for it as well.
Second, before the acceptance arrives to the inviter, the phone displays a “scheduling conflict”, which then is replaced with a tick when the meeting response arrives.
Could you provide a screenshot for it? I don’t recall observing that in my tests.
Finally, these errors were logged:
24/09/2019 20:47:58 [32230] [WARN] [cashmere] SyncAppointment->Check(): Parameter 'organizername' and 'organizeremail' should be set for a meeting request 24/09/2019 20:48:24 [ 6927] [WARN] [cashmere] /usr/share/z-push/backend/kopano/kopano.php:2629 Uninitialized string offset: 337 (8) 24/09/2019 20:48:24 [ 6927] [WARN] [cashmere] /usr/share/z-push/backend/kopano/kopano.php:2629 Uninitialized string offset: 338 (8) 24/09/2019 20:48:24 [ 6927] [WARN] [cashmere] /usr/share/z-push/backend/kopano/kopano.php:2629 Uninitialized string offset: 339 (8) 24/09/2019 20:48:24 [ 6927] [WARN] [cashmere] /usr/share/z-push/backend/kopano/kopano.php:2629 Uninitialized string offset: 340 (8)I also didn’t observe the “Uninitialized string offset” error in my tests. Please provide the complete WBXML level log for that request. Regarding organizername and organizeremail it’s because the device doesn’t send those attributes even if they are required.
EDIT: changing the meeting response does not work and displays the same error.
What exactly do you mean by “changing the meeting response”? Accept and then decline? In such case you have to be aware that after accepting or declining the meeting request, it is removed from the inbox and there’s the corresponding calendar item only. You should be able to delete the calendar item though and send the notification email to the organizer.
Manfred
-
The organizer receives the accepted email because I added a fix for it as well.
Thank you! :)
I also didn’t observe the “Uninitialized string offset” error in my tests. Please provide the complete WBXML level log for that request. Regarding organizername and organizeremail it’s because the device doesn’t send those attributes even if they are required.
I’ve checked after the tests you just asked for and that uninitialized string offset error hasn’t happened again so maybe it was a transient glitch.
EDIT: changing the meeting response does not work and displays the same error.
What exactly do you mean by “changing the meeting response”? Accept and then decline? In such case you have to be aware that after accepting or declining the meeting request, it is removed from the inbox and there’s the corresponding calendar item only. You should be able to delete the calendar item though and send the notification email to the organizer.
I’m doing it from the calendar app. So after having accepted a meeting, then going to the calendar app and changing the response, the error “cannot send response” is shown.
I’ve included in the zip the logs and screenshots you asked for. I created an event, then enabled logging, accepted, deleted, created another, accepted, changed reponse and then deleted. I will post the link when I can get firefox send to accept the file.
-
Sadly send.firefox.com is still not working so I’ll send everything through in the morning (BST). Sorry!!
-
-
Hi @amaccuish,
@amaccuish said in Can't accept calendar event:
EDIT: changing the meeting response does not work and displays the same error.
What exactly do you mean by “changing the meeting response”? Accept and then decline? In such case you have to be aware that after accepting or declining the meeting request, it is removed from the inbox and there’s the corresponding calendar item only. You should be able to delete the calendar item though and send the notification email to the organizer.
I’m doing it from the calendar app. So after having accepted a meeting, then going to the calendar app and changing the response, the error “cannot send response” is shown.
That’s not going to work. Once you accepted the meeting request, you’re only able to delete the corresponding appointment and send email to the organizer.
Second, before the acceptance arrives to the inviter, the phone displays a “scheduling conflict”, which then is replaced with a tick when the meeting response arrives.
I’m going to guess here that either the organizer or the attendee have another appointment which overlaps with this one. The device requests free-busy information for both the organizer and the attendee and the way free-busy works is that it only says which time slots are busy. So it’s even possible that one of them is busy because of this same appointment, but the device isn’t able to distinguish it.
Manfred
-
That’s not going to work. Once you accepted the meeting request, you’re only able to delete the corresponding appointment and send email to the organizer.
Is that not part of the activesync spec? Say I’ve accepted, when I go into the iOS calendar app it shows the accept button highlighted and allows me to change my choice to tentative or refuse. This works with an Office 365 account but still not with z-push and kopano.
I’m going to guess here that either the organizer or the attendee have another appointment which overlaps with this one. The device requests free-busy information for both the organizer and the attendee and the way free-busy works is that it only says which time slots are busy. So it’s even possible that one of them is busy because of this same appointment, but the device isn’t able to distinguish it.
No. Both the test appointments I did were at times where both people were free, hence it is confusing if the person hasn’t responded yet to show a scheduling conflict.
-
Hi @amaccuish,
@amaccuish said in Can't accept calendar event:
That’s not going to work. Once you accepted the meeting request, you’re only able to delete the corresponding appointment and send email to the organizer.
Is that not part of the activesync spec? Say I’ve accepted, when I go into the iOS calendar app it shows the accept button highlighted and allows me to change my choice to tentative or refuse. This works with an Office 365 account but still not with z-push and kopano.
I’ve checked it again and there was no request to the server from the device. I don’t know how iOS does it internally, but it probably searches for the meeting request in the inbox and fails because it’s not able to find it. I mistakenly assumed that it would send another MeetingResponse request which wouldn’t have worked.
I’m going to guess here that either the organizer or the attendee have another appointment which overlaps with this one. The device requests free-busy information for both the organizer and the attendee and the way free-busy works is that it only says which time slots are busy. So it’s even possible that one of them is busy because of this same appointment, but the device isn’t able to distinguish it.
No. Both the test appointments I did were at times where both people were free, hence it is confusing if the person hasn’t responded yet to show a scheduling conflict.
Well, that’s how the device displays it, Z-Push has no influence here except providing free-busy information. The attendee status is “No response”.
Manfred
-
Thanks for getting back!
Just to let you know, I’m having quite a lot of problems with iOS 13.E.g.
28/09/2019 17:14:21 [16745] [WARN] [cashmere] /usr/share/z-push/backend/kopano/kopano.php:1399 mapi_table_queryrows() expects parameter 1 to be resource, boolean given (2) 28/09/2019 17:14:21 [16745] [WARN] [cashmere] /usr/share/z-push/backend/kopano/kopano.php:1402 count(): Parameter must be an array or an object that implements Countable (2) 28/09/2019 17:14:21 [16745] [FATAL] [cashmere] WBXML 10K debug data: AwFqAAAPRUdIA01haWxib3gAAUlTAABQA0VtYWlsAAFSA1VkMGQxYwABAA9VA2ZfcHJpdGNoYXJkQHh0cmEuY28ubnoAAVoAAg8AD1IDMjAxMC0wMy0xNlQwMToyMDozNS4wMDBaAAEBAQFKSwMwLTk5AAEAEUVGAzEAAUcDNTAwAAFIAzAAAQEAAGIDMAABAA8XGQEBAQ== 28/09/2019 17:14:21 [16745] [FATAL] [cashmere] Exception: (StatusException) - BackendKopano->Fetch('',''): Error getting entryid: 0xFFFFFFFF80070057 28/09/2019 17:14:29 [18943] [ERROR] [cashmere] LoopDetection->ProcessLoopDetectionPreviousConnectionFailed(): Command 'Search' at 28/09/2019 17:14:21 with pid '17726' terminated unexpectedly or is still running. 28/09/2019 17:14:29 [18943] [ERROR] [cashmere] Please check your logs for this PID and errors like PHP-Fatals or Apache segmentation faults and report your results to the Z-Push dev team. -
Hi @amaccuish,
please provide the WBXML level log for the Search request (pid 16745). Are there errors in apache and kopano logs as well?
Manfred
