calendar sync fails after introducing an event in the Google calendar on the smartphone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Calendar App |
New
|
High
|
Renato Araujo Oliveira Filho |
Bug Description
The bug happens when I try to introduce a new event in the calendar through the phone, not when a new event is introduced through the web interface at https:/
I am logged into Google not with a ...@gmail.com address, but with my own ...@romanliturg
Steps to reproduce the wrong behaviour:
1. Open the calendar app on the phone
2. First sync, just to be sure that the bug is starting to happen after the operations below. Sync should work.
3. Create a new event.
4. Sync (look at the time).
5. Wait 5 min. You can see the app is syncing by tapping on the menu icon above right: when the sync process is running, the first entry in the menu is a loop arrow and the label "Syncing" grayed out. Otherwise, you just see the label "Sync".
6. After 5 mins, (keep watching and prevent the screen the dim out, the message is disappearing very quickly) you get a message saying sync has failed.
7. Go to the web interface https:/
What should happen:
1. Sync shouldn't fail and the new event should appear
What happens:
1. Sync is failing and the newly created event should show up in Google calendar, but it doesn't.
Workaround:
1. Since I am running version 0.5.858 of the calendar, it happened to be enough to sync and sync again, until it worked, with the hassle that you have to wait 5 mins each time sync is failing.
2. If you keep out of sync, like it was the case with previous versions, you have to remove your Google account and creating it again. Syncing goes amazing fast in the case you have to retrieve the complete calendar from the cloud.
Complementary information:
Content of file .cache/
status = 500
error = error code from SyncEvolution fatal error (remote, status 500): REPORT 'meta data': bad HTTP status: <status 1.1, code 500, class 5, Internal Server Error>
start = 1470831255, 2016-08-10 14:14:15 +0200
end = 1470831576, 2016-08-10 14:19:36 +0200
source-
source-
source-
source-
source-
source-
Content of file .cache/
Sounds like jibel's issue we need to get to bottom of this.