[Tickets #14142] Re: Horde Sync with Samsung Note 2 logs errors

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/14142
------------------------------------------------------------------------------
  Ticket             | 14142
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Horde Sync with Samsung Note 2 logs errors
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
-State              | Unconfirmed
+State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2015-10-18 13:15) wrote:

> One of our users with a Samsung Note 2 using ActiveSync produces  
> errors, although synchronization works ok.
>
> Here relevant part of Horde-ActiveSync-Log :
>
> 2015-10-18T11:08:46+02:00 INFO: [27709] Handling SYNC command.
> 2015-10-18T11:08:46+02:00 INFO: [27709] Checking policykey for  
> device: SEC111ABCDABCDAB user: myuser
> 2015-10-18T11:08:46+02:00 INFO: [27709] Policykey: 0 verified.
> 2015-10-18T11:08:46+02:00 INFO: [27709] Creating new  
> Horde_ActiveSync_SyncCache.
> 2015-10-18T11:08:46+02:00 DEBUG: [27709] I  <Synchronize>
> 2015-10-18T11:08:46+02:00 DEBUG: [27709] I   <Folders>
> 2015-10-18T11:08:46+02:00 DEBUG: [27709] I    <Folder>
> 2015-10-18T11:08:46+02:00 DEBUG: [27709] I     <SyncKey>
> 2015-10-18T11:08:46+02:00 DEBUG: [27709] I       0
> 2015-10-18T11:08:46+02:00 DEBUG: [27709] I     </SyncKey>
> 2015-10-18T11:08:46+02:00 DEBUG: [27709] I     <FolderId>
> 2015-10-18T11:08:46+02:00 DEBUG: [27709] I       




> 2015-10-18T11:08:46+02:00 ERR: [27709] Unmatched end tag:
> 2015-10-18T11:08:46+02:00 ERR:
> 2015-10-18T11:08:46+02:00 ERR: Protocol error

This is exactly what the error states, a Protocol error. The client is  
sending an empty value for the FOLDERID node, which is not allowed and  
actually makes no sense since this is the only way to identify the  
folder the client is requesting a sync for.