[Tickets #9100] Re: corrupted turba photos

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9100
------------------------------------------------------------------------------
  Ticket             | 9100
  Updated By         | thomas at trethan.net
  Summary            | corrupted turba photos
  Queue              | SyncML
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


thomas at trethan.net (2010-06-17 08:15) wrote:

Basically syncing contacts works fine in both directions. Contact  
photos get synced from the phone to Turba, but unfortunately they  
won't get synced back when modifying contacts in Turba. The result is,  
that contact photos are deleted on the phone and remain in Turba,  
regardless of any further syncs.

/tmp/sync/data.txt lists the photo data in both sections "received  
from backend" and "converted for client":
BEGIN:VCARD
VERSION:2.1
NICKNAME:
BDAY:
PHOTO;ENCODING=b;TYPE=JPEG:w7/DmMO/w6AAEEpGSUYAAQEBAHoAegAAw7/DmwBDAAg...

/tmp/sync/log.txt show nothing out of the ordinary:
DEBUG:? Sending 1 server changes for client URI contacts
DEBUG:? Sending replace from server:  
20100221132611.33961m958i82mulc at mydomain.com
DEBUG:? Sending <Final> to client
DEBUG:? Return message completed

About my environment:
Horde 3.3.6 (stable), Turba 2.3.3, running with https
Samsung OmniaLite GT-B7300, Windows Mobile 6.5, Synthesis SyncML  
Client STD 3.0.2.24

After doing a lot of tests together with the Synthesis crew they sent  
me the following explanation:

1) The Horde devInf is wrong. The correct type name is text/vcard,
as  sent with the items (which have the correct type). But the
devInf shows  text/directory, which is not correct.
(our client ignores that, this is not the main reason for the problem)

2) We decoded the sent photo information. All the sent photos are
completely corrupted and can't be displayed therefore. It looks like
a  wrong conversion from ANSI to UTF-8, e.g. the type is something
like  JFIF (not JPEG). So the server sends complete garbage within
the photo  field.

A real JPG starts with:
FF D8 DD E0 00 10 4A

What we get is:
C3 BF C3 98 C3 BF C3 A0 00 10 4A

The starting C3 BF is simply FF in UTF-8.