Davdroid stopped working in purchased version

---

Hi,

i’m a little bit lost in space. After buying davdroid via amazon, the whole thing stops working. Steps i have done so far:

• installing davdroid OSE from fdroid:
• configured and synced with SOGo:
• good feeling:
• purchased davdroid via amazon:
• uninstalled davdroid OSE:
• installed puchased version of davdroid:
• configured the purchased version the same way as OSE before:

Adressbook and calendar gets detected but thats all. The account doesn’t show up in my contact sources. I have restarted my Phone, restarted my SOGo server, disabled Afwall and XPrivacy, but nothing happend. It still doesn’t work. In contrast to the OSE version, i have only one ‘davdroid’ account instead of two accounts before. ‘davdroid’ and ‘davdroid adressbook’.

• bad feeling

If i enter my account data, i see some PROPFIND request. But after hitting ‘sync’ nothing happens in my server logs.

I own a Xiaomi MI2S, if this matters.

Gernot

Thank you for the purchase! Thats very strange - all our versions are almost identical, there are only very few changes between them… Which version of DAVdroid do you have?

We’ve also tested it with our Amazon account - it works flawlessly without problems. Without a debug information and logs that show the error we can’t help you… Logs can be written from withihn DAVdroid (navigation drawer in the app). The debug info is also found there. You can post them here or send them to us by email: play@bitfire.at

OK, here we go.

--- BEGIN DEBUG INFO ---

SOFTWARE INFORMATION
Package: at.bitfire.davdroid
Version: 1.6.1.1 (151) Fri Jun 16 18:47:55 MESZ 2017
Installed from: com.amazon.mShop.android
JB Workaround installed: no

CONFIGURATION
android.permission.READ_CONTACTS permission: granted
android.permission.WRITE_CONTACTS permission: granted
android.permission.READ_CALENDAR permission: granted
android.permission.WRITE_CALENDAR permission: granted
org.dmfs.permission.READ_TASKS permission: granted
org.dmfs.permission.WRITE_TASKS permission: granted
System-wide synchronization: automatically
Account: gernot@tenchio.de
  Address book sync. interval: 15 min
  Calendar     sync. interval: 15 min
  OpenTasks    sync. interval: —
  WiFi only: false
  [CardDAV] Contact group method: GROUP_VCARDS
  [CalDAV] Time range (past days): 90
           Manage calendar colors: true

SQLITE DUMP
android_metadata
	|  locale |
	|  de_DE |
----------
settings
	|  setting | value |
	|  logToExternalStorage | 1 |
----------
services
	|  _id | accountName | service | principal |
	|  1 | gernot@tenchio.de | carddav | https://www.tenchio.de/SOGo/dav/gernot/ |
	|  2 | gernot@tenchio.de | caldav | https://www.tenchio.de/SOGo/dav/gernot/ |
----------
sqlite_sequence
	|  name | seq |
	|  services | 2 |
	|  homesets | 5 |
	|  collections | 8 |
----------
homesets
	|  _id | serviceID | url |
	|  4 | 1 | https://www.tenchio.de/SOGo/dav/gernot/Contacts/ |
	|  5 | 2 | https://www.tenchio.de/SOGo/dav/gernot/Calendar/ |
----------
collections
	|  _id | serviceID | url | readOnly | displayName | description | color | timezone | supportsVEVENT | supportsVTODO | sync |
	|  6 | 1 | https://www.tenchio.de/SOGo/dav/gernot/Contacts/directory/ | 0 | Local Database | <null> | <null> | <null> | <null> | <null> | 1 |
	|  7 | 1 | https://www.tenchio.de/SOGo/dav/gernot/Contacts/personal/ | 0 | Persönliches Adressbuch | <null> | <null> | <null> | <null> | <null> | 1 |
	|  8 | 2 | https://www.tenchio.de/SOGo/dav/gernot/Calendar/personal/ | 0 | Persönlicher Kalender | <null> | -5592406 | <null> | 1 | 1 | 1 |
----------

SYSTEM INFORMATION
Android version: 5.0.2 (xiaomi.eu)
Device: Xiaomi MI 2SC (aries)

--- END DEBUG INFO ---

The problem is, the davdroid account isn’t visible in my calendar app.

I’ve testet my SOGo server with cadaver. Everything seems to work like a charme.

dav:/SOGo/dav/> ls /SOGo/dav/gernot/Contacts
Listing collection `/SOGo/dav/gernot/Contacts/': succeeded.
Coll:   directory                              0  Jun 22  2017
Coll:   personal                               0  Jun 22  2017
dav:/SOGo/dav/> ls /SOGo/dav/gernot/Contacts/personal
Listing collection `/SOGo/dav/gernot/Contacts/personal/': succeeded.
        2674-59485600-1-60EA0800             211  Jun 20 02:53
        2674-59485600-11-60EA0800            203  Jun 20 02:53
        2674-59485600-13-60EA0800            116  Jun 20 02:53
        2674-59485600-15-60EA0800            116  Jun 20 02:53
        ...
dav:/SOGo/dav/>

The problem is, the davdroid account isn’t visible in my calendar app.

Did you try to enable it in the calendar app? Most calendar apps have an option to enable/disable specific calendars.

However, if calendars and contacts really don’t show up, I guess there’s some problem with a privacy guard. Verbose DAVdroid logs would probably contain more useful information.

Yes, i dit. It worked after installing davdroid OSE the first time. But the davdroid account isn’t visible after the update anymore. I’ve tried to reinstall davdroid OSE, but nothing happened. Reinstalled the purchased version again, with the same result. I’ll post more verbose logs tomorrow. Thanks so far.

It seems that this must be something with your device itself… I just tested our versions (incl. OSE and Amazon) with 4 different devices and there were no problems.

Can you try the following:

• Uninstall DAVdroid
• Restart the device
• Reinstall DAVdroid
• Create the account
• Go to DAvdroid system settings -> Error search / Activate logs
• Go to the account and press the Sync button
• Stop the logs and send them to us or post them here (anonymized)

Then we can better detect if there is some problem with DAVdroid or not.

I’ve played a lot and finally i got it working. Unfortunately, it is not really reproducible. It seems, after reinstalling davdroid all granted rights were lost, especially access to the adressbook. I’ve ‘regranted’ them, ‘redetected’ adressbook and calendar and viola, everything works as expected.

Anyway, a meaningful error message would have been helpful. Nevertheless, thank you for time, I’m happy now.

Good that you solved it Happy to hear that. We already implented permissions checks to help users grant them, but as your debug info said they were already granted…