[Tickets #9837] Re: kronolith ActiveSync
bugs at horde.org
bugs at horde.org
Sun May 1 00:46:16 UTC 2011
BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE
E-MAIL-ADRESSE WERDEN NICHT GELESEN.
Ticket-URL: http://bugs.horde.org/ticket/9837
------------------------------------------------------------------------------
Ticket | 9837
Aktualisiert Von | stephan at skleber.de
Zusammenfassung | kronolith ActiveSync
Warteschlange | Synchronization
Version | Git master
Typ | Bug
Status | Feedback
Priorität | 1. Low
Milestone |
Patch |
Zuständige | Michael Rubinsky
+Neue Anlage | failedActiveSync-Calendar.txt
------------------------------------------------------------------------------
stephan at skleber.de (2011-05-01 00:46) hat geschrieben:
I can confirm the described problem. At my end contacts sync well,
whereas calendar fails to do so on three devices tested:
Android 2.2: HTC Desire: Geräte-ID:HTCAnd3062b66b
iOS 4.2.1 (jailbreaked): iPod touch 2G: Geräte-ID:Appl1A840UK5201
iOS 4.2.1: iPhone 4 (no log)
Log is attached.
The Desire reports "problems" after syncing. iOS-Devices simply do not
show anything. The Exchange calendar is displayed in the list of
calendars on Android as well as iOS but neither does contain anything.
I used horde without and with the changes described in this Ticket:
Horde 4.0.1
kronolith 3.0.1
turba 3.0.1
The complete Horde database was created from cratch by the
configuration panel in the Administration Menu directly prior to the
test. I then created one contact and three events for the user I tried
syncing for.
>> That did it.
> Great.
>
>> Does not work with Android 2.3 Mail (exchange) by itself I had to use
>> touchdown as the syncing never started it authenticates, but never
>> starts to download contacts or calendar.
>
> Hm. Works perfectly here on 2.3.3 (Cyanogen 7). What happens if you
> force the sync in the Accounts and Sync settings screen?
>
>> I'm not sure where to make the change on the
>> framework/ActiveSync/lib/Horde/ActiveSync/State/History.php
>> To give you more error logging.
>
> That change shouldn't affect your issue, it was related to the
> original poster's problem, but you just need to add the new line
> within the catch block (after line 226).
More information about the bugs
mailing list