Bug 338743

Summary: Google Cal. Event Not Changed after being edited
Product: [Frameworks and Libraries] Akonadi Reporter: Donovan Hoare <donovan>
Component: Google ResourceAssignee: Daniel Vrátil <dvratil>
Status: RESOLVED UNMAINTAINED    
Severity: major CC: donovan, kdepim-bugs
Priority: NOR    
Version: 4.13   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Donovan Hoare 2014-09-02 02:51:20 UTC
Good day all.
Im using kubuntu 14.04 with kde 4.13.3

In 4.13.0 there was a problem wit adding calendar entries but that has been fixed.
I can add a item and it will show in my google cal, which syncs with my phone and tablet.

However if i decided to EDIT an event after it was synced it will not change
Example. I create an event call test from 1pm to 2pm. that will show on google cal.
Should i then edit the event and change the time from 1pm to 4pm. that will not sync.

I have turned on debugging on using theese steps from a previous / other post
===
Please open kdebugdialog and enable "LibKGAPI" and "LibKGAPI (raw data)", then restart Akonadi from console (akonadictl restart).
===
in my output after editing i get the following

akonadi_googlecalendar_resource_0(9420)/LibKGAPI (raw data) KGAPI2::Job::Private::_k_replyReceived: "{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "required",
    "message": "Missing end time."
   }
  ],
  "code": 400,
  "message": "Missing end time."
 }
}
"
akonadi_googlecalendar_resource_0(9420)/LibKGAPI KGAPI2::Job::Private::_k_replyReceived: Bad request, Google replied ' "{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "required",
    "message": "Missing end time."
   }
  ],
  "code": 400,
  "message": "Missing end time."
 }
}



Reproducible: Always

Steps to Reproduce:
1. as stated above create and event then edit
2.
3.

Actual Results:  
No edit on google cal

Expected Results:  
Expected event to be updated
Comment 1 Denis Kurz 2016-09-24 20:37:53 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:09:46 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.