[horde] Problem with iPhone / Calendar App and Horde

[Michael J Rubinsky]

Quoting Andy Sloane <andrewsloane19887 at gmail.com>:

> On Thu, 21 May 2020 at 17:50, Michael J Rubinsky <mrubinsk at horde.org> wrote:
>
>>
>> Quoting Andy Sloane <andrewsloane19887 at gmail.com>:
>>
>> > This is a bit of a strange one.
>> >
>> >
>> > My Horde worked for a while with my iPhone.  I could add an event in
>> > Kronolith on the GUI, and it would appear on my iPhone in the 'Calendar'
>> > app.  And of course, vice versa.
>> >
>> >
>> > Now, I have a problem.
>> >
>> >
>> > For the Calendar app, I can now add an event on the GUI, and it will
>> appear
>> > on the iPhone.  So far, so good.  But if I leave the device alone, with
>> the
>> > Calendar app on display, then after about 10-12 seconds, every single
>> event
>> > from the Horde, vanishes.   If I then leave it alone for a minute or so,
>> > the events all come back.   And so on.  Vanishing .. coming back...
>> > vanishing .. coming back.
>>
>> Sounds like some kind of sync loop. They are usually caused by some
>> error in the data being sent to the client that causes the client to
>> re-pair the sync connection.  The only way we can help diagnose this
>> is with a synclog.  You enable/configure these in the ActiveSync tab
>> of the base horde admin screen. These can be large-ish, so feel free
>> to email to me directly.
>>
>>
>>
> hi Mike.
>
> Thank you for this.  Sorry not to have responded sooner.  I switched on
> logging when I read your e-mail, and forgot about it until this morning.
>  :-)  So it's now  a bit under 10 gig.
>
> What should I be looking for?

What I would do is delete the log, and recreate the activesync account  
on your device. That way the log is fresh and will be much easier to  
find any issues.

If there are no outright "ERR" entries in the log, it's hard to  
explain what to look for, as you'd really have to know the eas  
protocol to know if anything is out of place. What I'd be probably be  
looking for is the submission of the same synckey over and over again,  
then looking for the first time that sync key was issued. Typically  
that would mean there is some kind of data or protocol issue during  
that request. Another possibility is to look for the device making a  
sync request with a synckey of '0' - this indicates the device is  
resetting the sync pairing. Then I look at the few requests before  
that request to see if there was any reason for the reset (some status  
codes sent from the server would trigger this etc...).

ANyway, once you have a smaller sync log, I can take a look...






-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 9272 bytes
Desc: PGP Public Key
URL: <https://lists.horde.org/archives/horde/attachments/20200526/3c63d1de/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 851 bytes
Desc: PGP Digital Signature
URL: <https://lists.horde.org/archives/horde/attachments/20200526/3c63d1de/attachment.sig>