[Tickets #13038] Re: Error saving state for synckey - no Inbox synchronization

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13038
------------------------------------------------------------------------------
  Ticket             | 13038
  Updated By         | skaman.tx at gmail.com
  Summary            | Error saving state for synckey - no Inbox
                     | synchronization
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


skaman.tx at gmail.com (2014-03-24 21:59) wrote:

>>>>>> See attached log.  Includes error when running 2.13.2 and proper sync
>>>>>> once downgraded to 2.12.4.  Note that once I downgraded to 2.12.4 and
>>>>>> synced the email accounts on the device manually, then upgraded to
>>>>>> 2.13.2, the device sync'd just fine.  However, since I don't have
>>>>>> control over my email users devices, I'm downgrading back to 2.12.4
>>>>>> since I know it "just works."
>>>>>
>>>>> I'm not familiar with the Moto X, but since it's a fairly recent
>>>>> device I would imagine it uses EAS 14.1? Can you look at your logs
>>>>> when using 2.12.4 and see what the initial log entry says about the
>>>>> EAS version in  use?
>>>>
>>>> The log file I posted contains entries while running under 2.13.2 and
>>>> 2.12.4.  The 2.12.4 entry shows the following:
>>>>
>>>> equest being handled for device: ANDROIDC135954261, Supporting
>>>> protocol version: 12.1, Using Horde_ActiveSync v2.12.4
>>>
>>> The device uses EAS 12.1 and therefor will not work with the
>>> Horde_ActiveSync-2.13.2. So yes, if you revert this commit, it will
>>> most likely work if it worked with Horde_ActiveSync-2.12.4.
>>>
>>>> The 2.13.2 entry shows the following:
>>>>
>>>> Request being handled for device: ANDROIDC135954261, Supporting
>>>> protocol version: 14.1, Using Horde_ActiveSync v2.13.2
>>
>> Hmmm, then why is the same device using EAS 14.1 and now syncing just
>> fine under ActiveSync v2.13.2?
>
> The device isn't using EAS 12.1, Horde is using EAS 14.1. This will  
> work as long as Horde is not using something that wasn't available  
> in EAS 12.1. But as soon as it does, synchronization will break again.
>
>>  Recall from my previous post that
>> once I downgraded to 2.12.4, then manuall sync'd the device, then
>> upgraded to 2.13.2, the device works just fine.  Doesn't seem right
>> somehow.

OK, I see now what you are saying.  Is there a fix being contemplated/needed?