Re: Issue 68 in kolab-android: SyncException: Unable to find XML Document

[kolab-...@googlecode.com]

Updates:
Summary: SyncException: Unable to find XML Document

Comment #12 on issue 68 by arthur.z...@gmail.com: SyncException: Unable to
find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

Renaming case

[kolab-...@googlecode.com]

Updates:
Labels: -Priority-Medium Priority-High

Comment #13 on issue 68 by arthur.z...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

(No comment was entered for this change.)

[kolab-...@googlecode.com]

Comment #14 on issue 68 by 8muelle...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

Arthur, thanks for your response and trying to reproduce the issue with my
test data.
I just tried again with version 0.9.1 both on my HTC Desire running rooted
Android 2.3.3 and Desire S running 2.3.5 - the problem remains.

I do some software developments occasionally, but so far not for Android.
I could send further logs, maybe it helps if you make them more verbose.

[kolab-...@googlecode.com]

Comment #15 on issue 68 by arthur.z...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

I'll implement a verbose version. Hopefully this week

[kolab-...@googlecode.com]

Comment #16 on issue 68 by arthur.z...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

I've just release a 0.9.2 version with more verbose logging. Please enable
Diag Log in your settings and submit the logcat.

[kolab-...@googlecode.com]

Comment #17 on issue 68 by 8muelle...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

Thanks; the log is attached.

Attachments:
SyncKolab_0.9.2.log 127 KB

[kolab-...@googlecode.com]

Comment #18 on issue 68 by arthur.z...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

Looks like diagnostic log was not enabled in kolab droid settings...

[kolab-...@googlecode.com]

Comment #19 on issue 68 by arthur.z...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

I was expecting the messages:


Downloading item ...
extractXml
mainDataSource is a
containing ? items
0: ......
1: ......

[kolab-...@googlecode.com]

Comment #20 on issue 68 by 8muelle...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

Oops, I was not aware of the diagnostic log option.
Please find enclosed the more detailed log.

Attachments:
SyncKolab_0.9.2.log 155 KB

[kolab-...@googlecode.com]

Comment #21 on issue 68 by arthur.z...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

0.9.4 has been released - even more logging.

[kolab-...@googlecode.com]

Comment #22 on issue 68 by 8muelle...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

All right, here is an updated log.

Attachments:
SyncKolab_0.9.4.log 98.8 KB

[kolab-...@googlecode.com]

Comment #23 on issue 68 by arthur.z...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

Looks like, it is not a problem with the class loader or DCHFactory. Please
- can anyone with this problem debug the app? We cannot reproduce it!

Thanks!

[kolab-...@googlecode.com]

Comment #24 on issue 68 by arthur.z...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

I've created a new version 0.9.5. I've cleaned up some javax.mail code.
Maybe this will help. Please tell me, if it did & we can close this case!

Thanks, Arthur

[kolab-...@googlecode.com]

Comment #25 on issue 68 by 8muelle...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

Thanks Arthur for giving it another try!

Unfortunately, I still get the same error.
I enclose KolabDiagDump.txt and the logcat output.

Regards,
David


Attachments:
KolabDiagDump.txt 2.2 KB
Kolab-0.9.5.log 133 KB

[kolab-...@googlecode.com]

Comment #26 on issue 68 by zebol...@gmail.com: SyncException: Unable to

find XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

I had a similar problem while syncing my contacts and was trying to debug
it. I figured out that in my case it was a problem with the expected mime
type in AbstractSyncHandler.extractXml(). For contacts it should
be "application/x-vnd.kolab.contact" but somehow the detected mime type
was "application/x-vndkolabcontact" (so the same but without the dots).
When viewing the message source with thunderbird I got the correct mime
type:

Content-Type: application/x-vnd.kolab.contact; name="kolab.xml"

I added the changes from the attached patch and then it worked (for the
contacts). I did not check yet if there is also a problem with the mime
type of the calendar entries.

Hope this helps a little bit in finding the real problem. Just give me a
hint when I can test some new code.

Attachments:
mimetype.patch 779 bytes

[kolab-...@googlecode.com]

Comment #27 on issue 68 by DvO...@gmail.com: SyncException: Unable to find
XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

zebol...@gmail.com, could you please provide the .apk?

I just gave Kolab a try again, version 3.0.0 on Thunderbird and 0.9.5 on
Android (this time Android 4.1.1 on Samsung Galaxy Note 2). Still the same
compatibility problem: the Android part can sync to Thunderbird, but not
vice versa.

I did not check the Android system log this time,
but found that Menu -> Diag. Dump says:
"no such column: displayName(code 1): ,
while compiling : SELECT name,
displayName, _sync_account,
_sync_account_type FROM Calendars"

I noticed that the message attachments look quite different!
Those produced on Thunderbird start like this:
Content-Type: application/vcard+xml;
name="kolab.xml"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="kolab.xml"

As opposed to those produced on Android:
Content-Type: application/x-vnd.kolab.contact; name=kolab.xml
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=kolab.xml

BTW, the Android side gives a wrong app version:
User-Agent: kolab-android 0.1

Moreover, I did not find in the documentation for the Android app any hint
whether the Thunderbird side should produce VCard/Kolab1, Xml/Kolab2, or
Xml/Kolab3 format.

[kolab-...@googlecode.com]

Comment #28 on issue 68 by DvO...@gmail.com: SyncException: Unable to find
XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

Arthur, I just found what actually causes the trouble:
The Thunderbird add-on does not produce the header line

MIME-Version: 1.0

[kolab-...@googlecode.com]

Comment #29 on issue 68 by DvO...@gmail.com: SyncException: Unable to find
XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

Well, that's the problem for address book entries.
For Calendar entries there must be some further issue.

[kolab-...@googlecode.com]

Comment #30 on issue 68 by DvO...@gmail.com: SyncException: Unable to find
XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

I attach a patched Thunderbird extension that simply adds the missing MIME
version line. After setting the Contact Format to Xml/Kolab2, contact sync
now works fine.

Yet calendar sync with Android is still broken, in particular for ICS and
beyond (Android 4+). See also issue 79.

Attachments:
synckolab_3.0.0-DvO.xpi 1.3 MB

[kolab-...@googlecode.com]

Comment #31 on issue 68 by DvO...@gmail.com: SyncException: Unable to find
XML Document
http://code.google.com/p/kolab-android/issues/detail?id=68

Meanwhile I filed a bug and provided a patch on the Thunderbird extension:
https://www.mozdev.org/bugs/show_bug.cgi?id=25271

BTW, note that the corrected version does not affect already existing IMAP
folder entries. What I did to correct these is: disable kolab syncing,
manually remove the broken entries via Thunderbird, re-enable kolab
syncing, and manually sync. Be careful as entries may be lost - better
backup your address book first.

@Arthur, I wonder why you could/can not reproduce this problem. Did you for
instance actually insert as an IMAP folder entry the attachment I provided
on June 23:
http://kolab-android.googlecode.com/issues/attachment?aid=680010000&name=kolab.eml&token=2_T8af5yX3BNz0v55rWVUP8RwI8%3A1355702960750
I enclose a further item, this time a contact (rather than event).

Would be nice if synckolab also worked without seeing the "MIME-Version:
1.0" line.

Attachments:
sk-vc-DC8B4D3D87CA6184.eml 1.6 KB