Tickets :: [#6949] Further Blackberry Funambol client issues

6.0.0-beta1

7/5/25

Summary	Further Blackberry Funambol client issues
Queue	Synchronization
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org
Requester	sblainey (at) chemop (dot) org
Created	06/18/2008 (6226 days ago)
Due
Updated	04/05/2009 (5935 days ago)
Assigned	09/22/2008 (6130 days ago)
Resolved	09/25/2008 (6127 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

04/05/2009 08:24:45 PM	CVS Commit	Comment #13	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/SyncML/SyncML.php?rt=horde&r1=1.21.10.18&r2=1.21.10.19&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Backend.php?rt=horde&r1=1.8.2.15&r2=1.8.2.16&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Backend/Horde.php?rt=horde&r1=1.8.2.16&r2=1.8.2.17&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Backend/Sql.php?rt=horde&r1=1.6.2.6&r2=1.6.2.7&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command.php?rt=horde&r1=1.4.10.12&r2=1.4.10.13&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Alert.php?rt=horde&r1=1.18.10.15&r2=1.18.10.16&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Final.php?rt=horde&r1=1.10.10.10&r2=1.10.10.11&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Get.php?rt=horde&r1=1.14.10.15&r2=1.14.10.16&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Map.php?rt=horde&r1=1.1.10.11&r2=1.1.10.12&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Put.php?rt=horde&r1=1.12.10.12&r2=1.12.10.13&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Sync.php?rt=horde&r1=1.17.10.17&r2=1.17.10.18&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/SyncElement.php?rt=horde&r1=1.3.2.9&r2=1.3.2.10&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/State.php?rt=horde&r1=1.17.2.17&r2=1.17.2.18&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Sync.php?rt=horde&r1=1.8.4.20&r2=1.8.4.21&ty=u http://cvs.horde.org/co.php/framework/SyncML/tests/testpacket.php?rt=horde&r=1.2.2.1 http://cvs.horde.org/diff.php/horde/docs/CHANGES?rt=horde&r1=1.515.2.522&r2=1.515.2.523&ty=u

04/05/2009 08:12:14 PM	CVS Commit	Comment #12	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Sync.php?rt=horde&r1=1.62&r2=1.63&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/SyncElement.php?rt=horde&r1=1.17&r2=1.18&ty=u http://cvs.horde.org/diff.php/horde/docs/CHANGES?rt=horde&r1=1.1222&r2=1.1223&ty=u

04/04/2009 12:56:49 PM	Jan Schneider	Comment #11	Reply to this comment
Obviously this didn't fix it. See ~~bug #6995~~ for a follow-up.

09/25/2008 09:10:03 AM	Jan Schneider	State ⇒ Resolved

09/22/2008 09:46:28 PM	Jan Schneider	Comment #10 State ⇒ Feedback	Reply to this comment
Please try the patch I just committed.

09/22/2008 09:46:23 PM	CVS Commit	Comment #9	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Sync.php?r1=1.59&r2=1.60&ty=u

07/14/2008 11:05:37 AM	Jan Schneider	State ⇒ Assigned

07/14/2008 11:04:36 AM	Jan Schneider	Deleted Original Message

07/14/2008 10:38:00 AM	sblainey (at) chemop (dot) org	Comment #8 New Attachment: client_xml_data.txt	Reply to this comment
Please provide the client.xml log for that message too. Attached... Just realised the client files are from a different session, so here is the corresponding data.txt

07/14/2008 10:35:01 AM	sblainey (at) chemop (dot) org	Comment #7 New Attachment: client_xml.zip	Reply to this comment
Please provide the client.xml log for that message too. Attached...

07/14/2008 10:23:19 AM	Jan Schneider	Comment #6 State ⇒ Feedback	Reply to this comment
Please provide the client.xml log for that message too.

07/14/2008 09:34:27 AM	sblainey (at) chemop (dot) org	Comment #5 New Attachment: Sync4j.diff	Reply to this comment
And here is a patch to allow Horde to sync data from the blackberry running Funambol.

07/14/2008 09:29:10 AM	sblainey (at) chemop (dot) org	Comment #4 New Attachment: data.txt	Reply to this comment
Duplicate of ~~bug #6995~~. Only issue 1 is the same as ~~bug 6995~~ - there is still the issue with Horde not decoding the base64 encoded data sent by the blackberry funambol. I have attached data.txt from /tmp/sync showing that the data sent by the client is not converted correctly.

07/13/2008 09:17:17 AM	Jan Schneider	Comment #3 State ⇒ Duplicate	Reply to this comment
Duplicate of ~~bug #6995~~.

07/06/2008 05:26:05 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
Please provide the syncml log files from /tmp/syncml instead.

06/18/2008 09:56:13 PM	Jan Schneider	Assigned to Jan Schneider State ⇒ Assigned

06/18/2008 11:43:13 AM	sblainey (at) chemop (dot) org	Comment #1 Priority ⇒ 2. Medium State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ Synchronization Summary ⇒ Further Blackberry Funambol client issues Type ⇒ Bug	Reply to this comment
Using the v6.06 Funambol Blackberry client After applying the fix suggested in defect 6939 for the RespURI issue I came across the following two issues: 1) Horde does not recognise the Blackberry Funambol client as the device id returned is 'fbb-xxx' rather than 'sc-pim-xxx' and the client id cannot be edited within the Blackberry edition of Funambol. The fix for this is to update the getDevice function within State.php to recognise 'fbb-' as a sync4j client. 2) Horde does not decode the base64 data provided by the Funambol client in the sync (interestingly enough, it does encode data it sends to the client). The fix for this is to update the convertClient2Server function within Device/Sync4j.php to call base64_decode to decode $content before calling sif2vcard. The above fixes allow me to sucessfully sync my Blackberry address book with Turba. I have not tried calendar, notes or todo as I do not use them. I can provide patches if required.