Can't accept calendar event



  • Hi.

    I’m on iOS 13 but this also affects 12. I can send a calendar invite but the invitee cannot accept it, nor can I accept calendar invites sent to me.

    iOS displays the message “your response to the invitation cannot be sent”. On the inviter’s phone, it says there is a scheduling conflict and suggests other times. Accepting works from the WebApp.

    z-push logs include the lines

    19/09/2019 23:56:51 [10165] [ INFO] [alex] StatusException: SyncCollections->CheckForChanges(): Timeout forced after 11s from 713s due to other process - code: 3 - file: /usr/share/z-push/lib/core/synccollections.php:579
    19/09/2019 23:56:51 [10165] [ INFO] [alex] cmd='Ping' memory='2.52 MiB/4.00 MiB' time='11.06s' devType='iPhone' devId='tvlcldbl8l7er4icliccrsbb68' getUser='alex' from='fd69:35e7:3fbf:3a10:70e9:dec8:f2f0:bc3e' idle='11s' version='2.5.0-0ubuntu1' method='POST' httpcode='200'
    
    19/09/2019 23:56:54 [14670] [ INFO] [alex] StatusException: BackendKopano->MeetingResponse('2a5bfc81fcca4867ba324e0545137903b28f03000000','2a5bfc81fcca4867ba324e05451379033f0000000000', '2'): Error, attempt to respond to non-meeting request - code: 2 - file: /usr/share/z-push/backend/kopano/kopano.php:912
    
    19/09/2019 23:56:54 [14670] [ INFO] [alex] cmd='MeetingResponse' memory='1.98 MiB/4.00 MiB' time='0.30s' devType='iPhone' devId='tvlcldbl8l7er4icliccrsbb68' getUser='alex' from='fd69:35e7:3fbf:3a10:70e9:dec8:f2f0:bc3e' idle='0s' version='2.5.0-0ubuntu1' method='POST' httpcode='200'
    19/09/2019 23:56:54 [12824] [ INFO] [alex] cmd='Sync' memory='1.98 MiB/2.00 MiB' time='0.25s' devType='iPhone' devId='tvlcldbl8l7er4icliccrsbb68' getUser='alex' from='fd69:35e7:3fbf:3a10:70e9:dec8:f2f0:bc3e' idle='0s' version='2.5.0-0ubuntu1' method='POST' httpcode='200'
    

    z-push is 2.5.0 (I know there’s 2.5.1 but I didn’t see anything in the changelogs relating to this but in the meantime I will update anyway. It will take me a few days to complete testing)

    Kopano is 8.7.5.

    Thanks



  • And I’ve just tested with z-push 2.5.1 and the same issue happens.


  • Kopano

    Hi @amaccuish,

    please provide WBXML level log with the incoming meeting request and response for the user experiencing the issue.

    Manfred



  • Hi @Manfred I have a wbxml log. Can I send that via email? :)


  • Kopano

    Hi @amaccuish,

    if you have a valid Kopano subscription open a new issue with the support and attach the log to it. Otherwise you can upload it somewhere and send me the link.

    Manfred



  • I’ve read through and actually there’s nothing sensitive I think so here you go: pastebin log


  • Kopano

    Hi @amaccuish,

    the log you’ve provided is not sufficient. There is no incoming meeting request. I want to see the following:

    • Organizer sends meeting request. It’s synced to the mobile device as an incoming email. Probably also a tentative calendar entry is created on the server and synced to the mobile.
    • Attendee reads the meeting request on his mobile device.
    • Attendee accepts the meeting request on his mobile device. A meeting response request is sent to the server and possibly also an email to the organizer.

    Manfred



  • Ahh apologies. I’ll get that done in the next hour or so.



  • Ok done. The link is to a .zip file containing two log files. The user cashmere is the meeting creator and the user alex is the invitee.

    The link is: https://send.firefox.com/download/45788f89284d0ec1/#Fk2AfJPamF8kYV0gT4mb-w

    It will expire after one download.


  • Kopano

    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


  • Kopano

    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.


  • Kopano

    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



  • @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!!




Log in to reply