#120 Sync calendar data older than two weeks

[explorer129]

I'm using a few Android phones/tables with z-push Zimbra activesync connection and wondered if there is a limit on fetching old calendar appointments. I notice that all calendar appointments older than two weeks aren't shown and trying to figure out if this is an Android 'issue' or z-push (backend) related. I have no setting on my phone that controls the amount of days that it goes back in time for the calendar, only for email.

Do you have any info regarding this? Or perhaps some leads for me to debug requested calendar data.

[LiverpoolFCfan]

I have taken a quick look at this and you are correct. It is only ever returning 2 weeks. The issue lies somewhere in the core z-push diffbackend functionality as that is always passing 2 weeks to the backend regardless of what is configured on the Sync request.

I have opened a ticket with the z-push developers to see if they can fix it.

In the meantime I will move this to Tickets->Support Requests as it is not a bug in the backend.

[LiverpoolFCfan]

Ticket moved from /p/zimbrabackend/bugs/56/

[LiverpoolFCfan]

Just a clarification: I noticed you said in your post there is no setting in your client so specify how far to go back. In this case you will still likely just get 2 weeks back as that is a default. The testing I did was with an iPhone which allows you to select multiple different ranges, and making changes there did not impact what got passed to the backend.

[explorer129]

Correct, so I also want to check what value my phone requests on the server

[LiverpoolFCfan]

By the way,on my android 5.01 Galaxy S4 - I can find the period to sync the calendar under

Settings->Accounts->Microsoft Exchange ActiveSync->Settings->(Zimbra Account)->MORE SETTINGS->Period to sync Calendar

[explorer129]

I have no such setting, I guess it is removed in 5.1.1 or yours uses a custom Samsung provided service for the activesync part.

Is there any way for me to check what period my phone requests to zpush?

[LiverpoolFCfan]

If you turn debugging up to WBXML level - look for an incoming Sync request for folder F10 (default calendar). It will look like this

24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I  <Synchronize>
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I   <Folders>
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I    <Folder>
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I     <SyncKey>
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I      {61fb747f-ba6a-4d24-824e-15aae67f8dbf}1
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I     </SyncKey>
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I     <FolderId>
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I      f10
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I     </FolderId>
24/08/2015 14:45:32 [ 9000] [DEBUG] [myUser] [myDevice] ZPush::GetFolderClassFromFolderType('8'): Calendar
24/08/2015 14:45:32 [ 9000] [DEBUG] [myUser] [myDevice] GetFolderClassFromCacheByID from Device Manager: 'Calendar' for id:'f10'
24/08/2015 14:45:32 [ 9000] [DEBUG] [myUser] [myDevice] SyncCollections->AddCollection(): Folder id 'f10' : ref. PolicyKey '1', ref. Lifetime '10', last sync at ''
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I     <GetChanges/>
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I     <WindowSize>
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I      25
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I     </WindowSize>
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I     <Options>
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I      <FilterType>
24/08/2015 14:45:32 [ 9000] [DEBUG] [myUser] [myDevice] SyncParameters->UseCPO('DEFAULT')
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I       7
24/08/2015 14:45:32 [ 9000] [WBXML] [myUser] [myDevice] I      </FilterType>

The FolderId field identifies the folder, and the FilterType field identifies the period.

0 = All
1 = 1 day
2 = 3 days
3 = 1 week
4 = 2 weeks (default)
5 = 1 month
6 =3 months
7 = 6 months

[explorer129]

As suspected it returns the default of two weeks, so your thoughts with the two weeks default are correct unfortunately. I'll look into changing the sync period in the meanwhile so I can re-test this if/when core zpush is fixed

[LiverpoolFCfan]

An update on the issue. It is not a bug, it is an override in my config file that is limiting the window to 2 weeks. I was under the impression that the setting SYNC_FILTERTIME_MAX was for email only. In fact it controls the calendar too (which would have been obvious if I fully read the description). I changed mine from 2 weeks to 1 month and immediately got a further two and a half weeks of events synchronized.

So, unfortunately it looks like it is just a limitation on your android client version.

Do you have any other clients you can test with to confirm that it works ok for you?

[explorer129]

Just tested it with a different client "Nine" where I can change the calendar sync period, works perfectly. Sorry for reporting this, and thanks for your help!

[LiverpoolFCfan]

Thanks for confirming. I will close out the ticket.