Tickets :: Comment on [#11754] ActiveSync won't push new emails to mobile device

* Your Email Address
* Spam protection	Enter the letters below: .__.. .. . __.. . \| \|\| \|\| \|(__ \| \| \|__\\|/\\|\|/\\|.__)\|/\\|
Comment	>> I seem to have lost email syncing with Samsung Galaxy S3 <-> Horde >> git (e813ee5a85abc0a9a0aeada5ca417fea30ee8197): >> >> The combination has been working quite fine until git commit >> 33c28c5b3e4f09e6c7d750f276186336e7f3a8e0, after which I had some bug >> login problems and/or mail sending was completely broken for a while >> --> I was forced back to this commit again. >> >> Currently the problem is only related to email. For example calendar >> syncing works just fine. >> I can even send emails from my android phone and they get delivered >> properly (although a sent copy gets copied to sent base folder, not >> to the configured 2012 sub-folder) ---> However, the just sent email >> newer shows up on the phone. I checked the cyrus imapd communication, >> but I don't see any failures there, so I suspect that the error >> message about sync keys might be causing this problem itself. >> >> This is just to confirm that somebody else is also seend a similar >> problem with current activesync. >> >> 2012-11-30T17:25:12+00:00 INFO: [SEC155335ACE18C3] Folder server id: INBOX >> 2012-11-30T17:25:12+00:00 DEBUG: I </FolderId> >> 2012-11-30T17:25:12+00:00 DEBUG: I <DeletesAsMoves> >> 2012-11-30T17:25:12+00:00 DEBUG: I 1 >> 2012-11-30T17:25:12+00:00 DEBUG: I </DeletesAsMoves> >> 2012-11-30T17:25:12+00:00 DEBUG: I <GetChanges/> >> 2012-11-30T17:25:12+00:00 DEBUG: I <WindowSize> >> 2012-11-30T17:25:12+00:00 ERR: Unmatched content: >> 2012-11-30T17:25:12+00:00 ERR: Array >> ( >> [1] => 1 >> [2] => WindowSize >> [4] => 1 >> ) >> >> 2012-11-30T17:25:12+00:00 DEBUG: I 50 >> 2012-11-30T17:25:12+00:00 DEBUG: I </WindowSize> >> 2012-11-30T17:25:12+00:00 DEBUG: I <Options> >> 2012-11-30T17:25:12+00:00 DEBUG: I <FilterType> >> 2012-11-30T17:25:12+00:00 DEBUG: I 0 >> 2012-11-30T17:25:12+00:00 DEBUG: I </FilterType> >> 2012-11-30T17:25:12+00:00 DEBUG: I <AirSyncBase:BodyPreference> >> 2012-11-30T17:25:12+00:00 DEBUG: I <AirSyncBase:Type> >> 2012-11-30T17:25:12+00:00 DEBUG: I 2 >> 2012-11-30T17:25:12+00:00 DEBUG: I </AirSyncBase:Type> >> 2012-11-30T17:25:12+00:00 DEBUG: I <AirSyncBase:TruncationSize> >> 2012-11-30T17:25:12+00:00 DEBUG: I 0 >> 2012-11-30T17:25:12+00:00 DEBUG: I </AirSyncBase:TruncationSize> >> 2012-11-30T17:25:12+00:00 DEBUG: I </AirSyncBase:BodyPreference> >> 2012-11-30T17:25:12+00:00 DEBUG: I <AirSyncBase:BodyPreference> >> 2012-11-30T17:25:12+00:00 DEBUG: I <AirSyncBase:Type> >> 2012-11-30T17:25:12+00:00 DEBUG: I 4 >> 2012-11-30T17:25:12+00:00 DEBUG: I </AirSyncBase:Type> >> 2012-11-30T17:25:12+00:00 DEBUG: I </AirSyncBase:BodyPreference> >> 2012-11-30T17:25:12+00:00 DEBUG: I </Options> >> 2012-11-30T17:25:12+00:00 DEBUG: I </Folder> >> 2012-11-30T17:25:12+00:00 ERR: Incrementing counter, we saw this >> synckey before. >> 2012-11-30T17:25:12+00:00 DEBUG: I </Folders> >> 2012-11-30T17:25:12+00:00 DEBUG: I </Synchronize> >> 2012-11-30T17:25:12+00:00 DEBUG: Have syncable collections >> 2012-11-30T17:25:12+00:00 DEBUG: All synckeys confirmed. Continuing >> with SYNC > > Ok, this is quite an interesting problem. I most of the older mails > from Inbox to another sub-folder and it didn't solve the problem. > However, after I started bisecting the commits I figured out that > also the phone was somehow misbehaving ---> I restarted the phone > once again. ---> I continued bisecting and none of the tested commits > were bad anymore ---> Now the activesync works again even with the > latest commit and therefore I'm unable to re-produce the problem. I > even moved all the inbox mails back and the activesync still works > just fine. > > The obvious conclusion would be therefore that the problem was on > android client end, but I don't believe that is the real reason, as > rebooting the phone didn't help originally at all, until I emptied my > inbox and only after that the android reboot got the activesync > working again. In case the activesync gets stuck again, I'll try to > debug it again hopefully with better success. >
Attachment
Watch this ticket

Saved Queries