How quickly the removal will reflect on the phone is down to the individual phone and how quickly it issues a FolderSync request. Once the next FolderSync occurs the folder will disappear.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It must be something in the new Android client that is not liking the removal. I just resteted with my iPod, and after normal sync had been established, removing a new calendar from the Web client was notified immediately to the iPhone and was removed immediately by the phone.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Moved ticket to Support Requests as I don't believe this is a bug in the backend.
If you want to generate a WBXML level debug log, I can check it for you to see if the FolderSync is happening, and if the phone is being notified of the Calendar Removal. After that it is down to the client to act on the instruction.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do not believe it is a bug at this time. I am quite happy to take a look at a log file for you to see if the right messages are going back and forward. You would need to set the log level to WBXML level in the z-push config.php file, then reproduce the issue.
I would also suggest that after a period of time post reproducing the issue, you turn your phone off completely. Wait a couple of minutes then turn it back on, as most activesync clients perform a FolderSync when they are starting up. This might force the change to be recognized if the phone is not acting on the change notification already.
If you want to try this, you can send me a private message using the link to the left of this post including a real email address for yourself. I will reply telling you where you can send the logs for me to view them.
If you don't want to try, then go ahead and close out the ticket.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How quickly the removal will reflect on the phone is down to the individual phone and how quickly it issues a FolderSync request. Once the next FolderSync occurs the folder will disappear.
It has been 2 days though, not sure if that's normal?
Shouldn't take that long. What is the device?
Nexus 5, Android 4.4.4
It must be something in the new Android client that is not liking the removal. I just resteted with my iPod, and after normal sync had been established, removing a new calendar from the Web client was notified immediately to the iPhone and was removed immediately by the phone.
Ticket moved from /p/zimbrabackend/bugs/42/
Moved ticket to Support Requests as I don't believe this is a bug in the backend.
If you want to generate a WBXML level debug log, I can check it for you to see if the FolderSync is happening, and if the phone is being notified of the Calendar Removal. After that it is down to the client to act on the instruction.
Do you need any more help with this? Otherwise I will close out the ticket.
While i would like to get to the bottom of this, if it's not a real bug, we might just drop it for now. :)
I do not believe it is a bug at this time. I am quite happy to take a look at a log file for you to see if the right messages are going back and forward. You would need to set the log level to WBXML level in the z-push config.php file, then reproduce the issue.
I would also suggest that after a period of time post reproducing the issue, you turn your phone off completely. Wait a couple of minutes then turn it back on, as most activesync clients perform a FolderSync when they are starting up. This might force the change to be recognized if the phone is not acting on the change notification already.
If you want to try this, you can send me a private message using the link to the left of this post including a real email address for yourself. I will reply telling you where you can send the logs for me to view them.
If you don't want to try, then go ahead and close out the ticket.
No further response. Closing ticket.