Issues when updating a meeting

[jcasares]

Recently, whenever I get an update to a meeting I have accepted, the changes are not merged into the calendar. I click the ICS and accept the new date/time and it sends the reply to the sender but the calendar is not modified. I process it again and this time it doesn't let me send the reply but it allows me to add the new meeting time. The problem is that the old one remains.

It is getting quite confusing. Do someone observe this same issue or know what could be happening?
I don't know when it started because I know it worked before (some months ago).

[Kostya Vasilyev]

Is it consistently reproducible?

This is an IMAP account, not EWS, correct?

[Kostya Vasilyev]

And one other thing, is this a recurring meeting by any chance? And say, the update is for one specific recurrence?

Or a single (stand-alone, no repeating) meeting?

[jcasares]

It's an IMAP account.
It's a standalone meeting (non repeating).
It happened to all the recent meeting updates I got. Will try to verify if I can consistently reproduce it and report back to you.

[jcasares]

I did a quick and simple test with a friend and it worked as expected so I need to track what was different about the other requests. I believe it was with always the same person. If I can reproduce it with him will check what the ICS files look like and maybe sent them to you for further analysis.

Could it be also an issue with Google Calendar services? Transient maybe?

Because I believe that nothing changed in Aquamail between the time it worked and when it stopped working.

[jcasares]

Spoke too soon. The test I did reverted to the old date after a while. Now I believe it has something to do with Google Calendar Service and not Aquamail.

[Kostya Vasilyev]

Re: The test I did reverted to the old date after a while

The "after a while" means it's not AquaMail, which only writes data to Calendar right in the "event view" dialog.

Re: Now I believe it has something to do with Google Calendar Service and not Aquamail

Darn. Still if you have a reproducible case, or just more detailed instructions, I'll be happy to take a look.

[Kostya Vasilyev]

Finally got a chance to look at it today.

It was a Google bug from hell

Fixed (found a workaround), and yes it was getting broken specifically by the *sync* from the device to Google's servers.

Will post tonight as version 1.7.0-x-dev under "development builds".