Closed cjeanneret closed 10 years ago
I can confirm the Secure XML processing is not supported
warning, which is also thrown when one tries to setup an (unsupported) DAV server:
08-04 08:28:45.425 656-656/org.anhonesteffort.flock D/org.anhonesteffort.flock.ServerTestsFragment﹕ handleStartTests()
08-04 08:28:45.425 656-656/org.anhonesteffort.flock D/org.anhonesteffort.flock.ServerTestsFragment﹕ startTests()
08-04 08:28:45.804 656-674/org.anhonesteffort.flock W/System.err﹕ [AsyncTask #1] WARN org.apache.jackrabbit.webdav.xml.DomUtil - Secure XML processing is not supported
08-04 08:28:45.804 656-674/org.anhonesteffort.flock W/System.err﹕ javax.xml.parsers.ParserConfigurationException: http://javax.xml.XMLConstants/feature/secure-processing
08-04 08:28:45.814 656-674/org.anhonesteffort.flock W/System.err﹕ at org.apache.harmony.xml.parsers.DocumentBuilderFactoryImpl.setFeature(DocumentBuilderFactoryImpl.java:101)
08-04 08:28:45.814 656-674/org.anhonesteffort.flock W/System.err﹕ at org.apache.jackrabbit.webdav.xml.DomUtil.createFactory(DomUtil.java:71)
08-04 08:28:45.814 656-674/org.anhonesteffort.flock W/System.err﹕ at org.apache.jackrabbit.webdav.xml.DomUtil.<clinit>(DomUtil.java:62)
08-04 08:28:45.814 656-674/org.anhonesteffort.flock W/System.err﹕ at org.apache.jackrabbit.webdav.client.methods.PropFindMethod.<init>(PropFindMethod.java:82)
08-04 08:28:45.814 656-674/org.anhonesteffort.flock W/System.err﹕ at org.apache.jackrabbit.webdav.client.methods.PropFindMethod.<init>(PropFindMethod.java:64)
08-04 08:28:45.814 656-674/org.anhonesteffort.flock W/System.err﹕ at org.anhonesteffort.flock.webdav.carddav.CardDavStore.getCurrentUserPrincipal(CardDavStore.java:92)
08-04 08:28:45.824 656-674/org.anhonesteffort.flock W/System.err﹕ at org.anhonesteffort.flock.ServerTestsFragment$2.handleCardDavTestCurrentUserPrincipal(ServerTestsFragment.java:231)
08-04 08:28:45.824 656-674/org.anhonesteffort.flock W/System.err﹕ at org.anhonesteffort.flock.ServerTestsFragment$2.doInBackground(ServerTestsFragment.java:621)
08-04 08:28:45.824 656-674/org.anhonesteffort.flock W/System.err﹕ at org.anhonesteffort.flock.ServerTestsFragment$2.doInBackground(ServerTestsFragment.java:205)
08-04 08:28:45.824 656-674/org.anhonesteffort.flock W/System.err﹕ at android.os.AsyncTask$2.call(AsyncTask.java:287)
08-04 08:28:45.824 656-674/org.anhonesteffort.flock W/System.err﹕ at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
08-04 08:28:45.824 656-674/org.anhonesteffort.flock W/System.err﹕ at java.util.concurrent.FutureTask.run(FutureTask.java:137)
08-04 08:28:45.834 656-674/org.anhonesteffort.flock W/System.err﹕ at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:230)
08-04 08:28:45.834 656-674/org.anhonesteffort.flock W/System.err﹕ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
08-04 08:28:45.834 656-674/org.anhonesteffort.flock W/System.err﹕ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
08-04 08:28:45.834 656-674/org.anhonesteffort.flock W/System.err﹕ at java.lang.Thread.run(Thread.java:856)
This warning is harmless but after a few months has grown to be very annoying, it is produced by using any one of a few select WebDAV string constants. Ideally there would be some LogCat blacklist to which I could add "org.apache.jackrabbit.webdav.xml.DomUtil" but I haven't figured out how to do this with gradle and all that silliness.
I'm going to close this for now because it is not related to any lack of or broken functionality in the Flock client but know that as soon as I figure out how to silence this warning I will :P
Hello,
Going deeper in my troubles with Flock and contact sync (see #43), I get this nice trace:
After that, it goes on, starting to sync, speaking of elements found upstream and so on… And then, crash, "Unfortunately, Flock has stopped"…
Trace again:
If I understand the error, it seems one of my contacts isn't properly encoded right?
After a second check, I get the same error on my other device. "Source" (where I imported contacts to Flock) runs CM11, "guest" (where I wanted to get contacts) runs Slimkat.
I've tried to drop all contacts and re-import them from my owncloud dump (vcf format in the standard contact app, then import it into Flock), but it seems there's a lock somewhere…
Weird thing: the problematic records isn't on the "source" device… Where does it come from then??
It would be great if we could get some web interface on Flock servers so that we can try to sort it out or, at least, understand. Yes, I know, contents are encrypted… but I'd like to be able to download the broken vcard in order to understand what's happening ;).