When I open the Flock app on my Android device, I tap Begin, select that I want to use Flock Sync, and hit Next. I'm asked whether I have a Flock account. I do, so I tap Yes, log me in and enter my username and (long) password then tap Next. A swirly status indicator appears in the top right corner of the Flock window, then an Android overlay appears, saying

Unknown cryptography error, please send debug logs.

I'm unable to log into my Flock account using the app on my device. What can I do to log in an try to troubleshoot this issue? Where can I find the debug logs from my client?

I recently updated my version of Flock, and there's a notification that says "Migrating to new version. Replacing addressbook and calenders..."

It's been like that for like 12 hours. Doesn't seem to be a problem though.

Trying to set up Flock with a CardDav account in Zimbra fails with error message: "Server does not support CarDAV well-known URI or DAV: current-user-principal."

As agreed, I am filing a bug and I'll try to provide a debug log, when the feature will be available, in order to spot the cause of the issue!

I think Flock is nice and all, but for my particular use case it's rather useless because I need to sync my Calendars with the desktop (Windows and Linux, in my case) and apps that are supported there (e.g. Thunderbird with Lightning).

I think changing lots of Desktop clients and creating plugins for them might be way too much work. Therefore I propose that a bridging app should be written. It could simply be a local CardDAV/CalDAV server that is only available locally (and with user/password additionally to protect data from other accounts on the same machine). The local storage could then be synced with Flock.

Flock struck me as the best app to consider for distribution via F-Droid. (Please call me out if you disagree.) Reasons:

• small install base
• no GCM requirements

These are the main places where Moxie has explained what he would need to see to be comfortable with alternative distribution:

1. github.com/WhisperSystems/TextSecure/issues/127#issuecomment-13335689
2. github.com/WhisperSystems/TextSecure/issues/281#issuecomment-21762482
3. github.com/WhisperSystems/RedPhone/issues/143#issuecomment-19152664

Summarized:

• [ ] built-in crash reporting solution with a web interface (Pending: libsupplychain)
• [ ] built-in statistics gathering solution with a web interface
• [ ] built-in auto-update or "pester" feature in app (Pending: libsupplychain)
• [ ] build toggle for above features (Pending)
• [x] ~~server-side APK scanning (?)~~
• [x] server-side APK signature validation: developer's signatures and keys are preserved through reproducible builds
• [x] F-Droid should not expect users to enable "Settings > Security > Unknown sources"

(Unhyperlinked so the back-references don't overtly attract superfluous comment.)

Hopefully this repo won't get inundated with peanut gallerians like the other issues :)

cc: @mikeperry-tor @mvdan

Right now all of the contacts on my phone are stored locally and are not part of any remote account, but Flock's options for importing contacts only lets you import from remote accounts so I can't auto-import them all.

I can easily export all my contacts from the Contacts app into a .vcf file, but I can't open that file with Flock to import them either. I think allowing importing local contacts and allowing importing from .vcf files would both be useful for people moving to Flock who have just been managing contacts locally in the past.

Hello,

Seems I'm unable to retrieve my contacts using latest Flock version (available on f-droid). Logs doesn't help much so far:

08-03 15:17:46.221  23302-23660/org.anhonesteffort.flock:flock D/org.anhonesteffort.flock.sync.AbstractDavSyncWorker﹕ pullRemotelyChangedComponents()
08-03 15:17:47.573  23302-23660/org.anhonesteffort.flock:flock D/org.anhonesteffort.flock.sync.AbstractDavSyncWorker﹕ found + 130 remote components
08-03 15:17:48.624  23302-23660/org.anhonesteffort.flock:flock D/org.anhonesteffort.flock.sync.AbstractDavSyncWorker﹕ pullRemotelyDeletedComponents()
08-03 15:17:49.835  23302-23660/org.anhonesteffort.flock:flock D/org.anhonesteffort.flock.sync.AbstractDavSyncWorker﹕ found 130 remote components
08-03 15:17:49.835  23302-23660/org.anhonesteffort.flock:flock D/org.anhonesteffort.flock.sync.AbstractDavSyncWorker﹕ found 0 local components
08-03 15:17:49.835  23302-23660/org.anhonesteffort.flock:flock D/org.anhonesteffort.flock.sync.AbstractDavSyncWorker﹕ remote ctag post pull remote: 317905_346204
08-03 15:17:49.835  23302-23660/org.anhonesteffort.flock:flock W/org.anhonesteffort.flock.sync.AbstractDavSyncWorker﹕ sync result has errors, will not save remote CTag to local collection

I'll try to add some more debug in the app in order to get some more information…

My all-day events are all synced as two day events now - '23rd of july 1:00am to 24rd of july 1:00am'.

The all-day toggle is selected on my google calendar and not on my newly created synced copy.

timezone or not accepting the allday flag?

Running calendarserver (3.2+dfsg-4+deb7u1) on Debian (wheezy), I was able to run through the tests across the local network over HTTP.

Rather than manage SSL directly in calendarserver, I added an Nginx proxy like so:

upstream calendar {
    server 127.0.0.1:8008;
}

server {
    listen 443 ssl;
    ssl on;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers "EECDH:EDH:!MEDIUM:!LOW:!EXP:!DSS:!aNULL:!eNULL:!RC4:!3DES:!SEED:!MD5";
    ssl_certificate /etc/ssl/certs/public.pem;
    ssl_certificate_key /etc/ssl/private/private.key;

    server_name myserver.name;
    root /var/www;

    location / {
        proxy_set_header   X-Real-IP        $remote_addr;
        proxy_buffering off;
        proxy_pass http://calendar/;
    }
}

Flock now fails with "Connection error, please check internet connection."

My initial thought was perhaps the DNS hasn't propagated. (I created a new record for this server.) Adding a hosts file entry does not resolve the issue.

I also considered that perhaps SNI is unsupported or the SSL parameters were invalid. Flock happily connected to another, similarly configured server with Nginx ngx_http_dav_module entry (though of course failed it on CardDAV/CalDAV).

All that remains seems to be the proxying, but it's entirely unclear what parameters should be changed. The same server can be used with Thunderbird/Lightning, so the proxy at least works to the satisfaction of some clients.

After Merging/Joining contacts and then syncing again using Flock the contacts are un-merged into two separate contacts again. This issue occurs on the Nexus 5 Flock version 0.8.7. Correct action is for merged/joined contacts to remain linked after sync.

If I configure flock and wait for it to sync, I immediately notice many new entries in my phone's address book. These new contacts represent people I have emailed in the past without adding to my contact list. Google shows these on the Contacts pane of the Gmail web interface under "Other Contacts". Google contacts sync omits them, but Flock seems to grab all of these and insert them into my local contacts. I don't want that!

Flock 0.7.7 on Nexus 5 / CyanogenMod 11 / Android 4.4.4

I somehow got into a state where I had a bunch of raw contacts, but they weren't real contacts (ie. not showing up in "People" app. Anyhow, Flock was trying to sync them all. Not sure how normal that is, but i resolved it by manually deleting all the raw_contacts from the sqlite db.

Anyhow, just a data point.

Heyo! Loaded up flock onto my grouper wifi tablet (no gapps), and it closes on first boot.

Looking at the catlog, a NullPointerException was raised at <etc>IntroductionFragment.initDescription(IntroductionFragment.java:76): https://github.com/WhisperSystems/Flock/blob/33fe753b91f2526ab578af71d5faafb137a5ea40/flock/src/main/java/org/anhonesteffort/flock/IntroductionFragment.java#L76

I was able to fix it by setting the screen dimensions manually:

~/repos/chef-textsecure (master ✘)✹✭ ᐅ adb shell wm size reset   
~/repos/chef-textsecure (master ✘)✹✭ ᐅ adb shell wm density reset # crashes
~/repos/chef-textsecure (master ✘)✹✭ ᐅ adb shell wm density      
Physical density: 213
~/repos/chef-textsecure (master ✘)✹✭ ᐅ adb shell wm size         
Physical size: 800x1280
~/repos/chef-textsecure (master ✘)✹✭ ᐅ adb shell wm size 798x1280 # doesn't crash
~/repos/chef-textsecure (master ✘)✹✭ ᐅ adb shell wm size 799x1280 # crashes

So yeah, seems it crashes only when the minimum width is around 800 (and for some reason that includes 799..?)

Anyhow, might mess around later and submit a PR if I fix it

Had bad signal, when registering. Registration succeeded and Flock is working since.

But the create user notification refuses to go home. Not sure if the log I took today is still helpful...

https://gist.github.com/0813373ee61797d1b8e7

Registered on 18th

Sorry for cross-posting, I also just posted this on your website but I'm not sure where you'd look at it first...

Got a weird bug on my xperia Z1, running android 5. If I create a new Flock contact and first add a picture before doing anything else, it does not store the name and leaves the contact in a weird, basically un-editable state.

See a video of the issue here: https://youtu.be/IN-0LnRC1Yk

The current version of jackrabbit-webdav is 2.10.1. Flock uses version 2.3.7. Shouldn't the library be updated? Perhaps this might help with issues #83 and #95.

I face a error when connected to a self-hosted DAV server. See:

• Log
• Screenshoot

My certificate hosted and certified by Gandi has been generated by the following command:

openssl req -new -newkey rsa:2048 -sha512 -nodes [...]

Everything works perfectly with DAVdroid and pass CAdroid tests