Tickets :: [#14682] sync broken on contacts

6.0.0-beta1

7/26/25

Summary	sync broken on contacts
Queue	Synchronization
Queue Version	FRAMEWORK_5_2
Type	Bug
State	Resolved
Priority	2. Medium
Owners	mrubinsk (at) horde (dot) org
Requester	mirko (at) mucko (dot) de
Created	08/13/2017 (2904 days ago)
Due
Updated	08/24/2017 (2893 days ago)
Assigned	08/14/2017 (2903 days ago)
Resolved	08/20/2017 (2897 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

08/24/2017 12:31:03 PM	Git Commit	Comment #9	Reply to this comment
Changes have been made in Git (master): commit 9441ab3d624db8cadd0d8cfd879926a3036eba7d Author: Jan Schneider <jan@horde.org> Date: Thu Aug 24 14:29:46 2017 +0200 Be more permissive on not perfectly valid date strings. ~~Bug: #14682~~ framework/ActiveSync/lib/Horde/ActiveSync/Message/Base.php \| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) http://github.com/horde/horde/commit/9441ab3d624db8cadd0d8cfd879926a3036eba7d

08/20/2017 05:07:00 PM	Michael Rubinsky	Comment #8 Assigned to Michael Rubinsky State ⇒ Resolved	Reply to this comment
Nothing we can do about the broken birthdays, but we can prevent it from killiing the sync.

08/20/2017 05:05:13 PM	Git Commit	Comment #7	Reply to this comment
Changes have been made in Git (master): commit b447879d1c7e5d254667aa2b551dd5ac68cbeed4 Author: Michael J Rubinsky <mrubinsk@horde.org> Date: Sun Aug 20 13:03:32 2017 -0400 ~~Bug #14682~~ Don't fatal out on non-parsable date strings. framework/ActiveSync/lib/Horde/ActiveSync/Message/Contact.php \| 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) http://github.com/horde/horde/commit/b447879d1c7e5d254667aa2b551dd5ac68cbeed4

08/20/2017 04:58:24 PM	Michael Rubinsky	Comment #6	Reply to this comment
[Show Quoted Text - 9 lines][Hide Quoted Text] value being passed is complely. Can you put a Horde::debug($ts); on that line and report the result? To be correct, the output is (now another record): 2017-08-20T14:55:29+00:00 DEBUG: Variable information: string(23) "1991-06-4T00:00:00.000Z" But in fact, it affects each and every record wich has a birthday filled in. If this is truly what the client is sending, it's broken. That is not a valid datetime string. The day of month portion must be two characters long.

08/20/2017 04:57:18 PM	Michael Rubinsky	Comment #5	Reply to this comment
Horde::debug() documentation: http://wiki.horde.org/Doc/Dev/DebugH4 This link is no longer valif. No, but the search functionality on the site is still valid ;) https://wiki.horde.org/Doc/Dev/Debug

08/20/2017 02:57:08 PM	mirko (at) mucko (dot) de	Comment #4	Reply to this comment
value being passed is complely. Can you put a Horde::debug($ts); on that line and report the result? To be correct, the output is (now another record): 2017-08-20T14:55:29+00:00 DEBUG: Variable information: string(23) "1991-06-4T00:00:00.000Z" But in fact, it affects each and every record wich has a birthday filled in.

08/20/2017 09:47:05 AM	mirko (at) mucko (dot) de	Comment #3	Reply to this comment
value being passed is complely. Can you put a Horde::debug($ts); on that line and report the result? [14471][2017-08-20T09:44:13+00:00] I: <POOMCONTACTS:Birthday> [14471][2017-08-20T09:44:13+00:00] I: 1942-06-4T00:00:00.000Z is the only thing I see in the corresponding activesync.log. horde.log shows nothing more then the error mentioned above. If I can help in any way, let me know! Horde::debug() documentation: http://wiki.horde.org/Doc/Dev/DebugH4 This link is no longer valif.

08/14/2017 11:05:49 AM	Jan Schneider	Comment #2 Priority ⇒ 2. Medium State ⇒ Feedback Patch ⇒ No	Reply to this comment
It would be helpful to see what this: #0 /usr/share/php/Horde/ActiveSync/Message/Base.php(457): Horde_ActiveSync_Message_Contact->_parseDate('1942-06-4T00:00...') value being passed is complely. Can you put a Horde::debug($ts); on that line and report the result? Horde::debug() documentation: http://wiki.horde.org/Doc/Dev/DebugH4

08/13/2017 12:13:05 PM	mirko (at) mucko (dot) de	Comment #1 Priority ⇒ 3. High Type ⇒ Bug Summary ⇒ sync broken on contacts Queue ⇒ Synchronization Milestone ⇒ Patch ⇒ Yes State ⇒ Unconfirmed	Reply to this comment
if at least one contact has set a birthday and is changed, no longer any contact is synced (show stopper). Removing the lines 408 and 409 solves this issue: if ($date->timezone != 'UTC') { $date->setTimezone('UTC'); error report is: 2017-08-13 11:29:46 EMERG: HORDE Error: Call to a member function setTimezone() on boolean in /usr/share/php/Horde/ActiveSync/Message/Contact.php:408 Stack trace: #0 /usr/share/php/Horde/ActiveSync/Message/Base.php(457): Horde_ActiveSync_Message_Contact->_parseDate('1942-06-4T00:00...') #1 /usr/share/php/Horde/ActiveSync/Request/Sync.php(934): Horde_ActiveSync_Message_Base->decodeStream(Object(Horde_ActiveSync_Wbxml_Decoder)) #2 /usr/share/php/Horde/ActiveSync/Request/Sync.php(751): Horde_ActiveSync_Request_Sync->_parseSyncCommands(Array) #3 /usr/share/php/Horde/ActiveSync/Request/Sync.php(186): Horde_ActiveSync_Request_Sync->_parseSyncFolders() #4 /usr/share/php/Horde/ActiveSync/Request/Base.php(249): Horde_ActiveSync_Request_Sync->_handle() #5 /usr/share/php/Horde/ActiveSync.php(839): Horde_ActiveSync_Request_Base->handle() #6 /usr/share/php/Horde/Rpc/ActiveSync.php(143): Horde_ActiveSync->handleRequest('Sync', '1502619555857') #7 /var/www/horde/rpc.php(160): Horde_Rpc_ActiveSync->getResponse(NULL) #8 {main} [pid 24736 on line 74 of "/usr/share/php/Horde/ErrorHandler.php"] sync tool on client site if "Tzpush" for Thunderbird/Lightning. Seen on HORDE 5.2.21.