Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

DAVdroid crashes when using wrong values in the SIP address field

devvv4ever last edited by
DAVdroid crashes when using wrong values in the SIP address field in the contacts app.

Steps to reproduce:
- Edit a contact
- Add “internet call” field
- enter “Skype: blahblah” as value
- Force a sync
DAVdroid crashes unexpectedly.
Reply Quote 0
1 Reply Last reply
devvv4ever last edited by

For Skype please use the appropriate field for “Instant messenger” or “Chat”. There is a label named Skype there.
Reply Quote 0
1 Reply Last reply

2
Posts

606
Views

Log in to reply

Similar topics

B

Task sync error with DAVdroid 1.2.2
DAVx⁵ • solved bug • • bugreporter

2

1
Votes

2
Posts

1072
Views

R

Thanks for the report. This has been fixed with eb70f8690f1b04a1104d3729843ddcf881fa8ee0 and should be working again in DAVdroid 1.2.3.
A

No Calendarsync for inifinite events
DAVx⁵ • bug • • AutoImport-ragged

12

0
Votes

12
Posts

2046
Views

A

I built it myself and tested it. I’ve found another error. I tested the following cases: Create an event at ownCloud, sync it to the phone, edit it at the phone and sync it back: works Create an event at my phone, sync it to ownCloud, edit it there and sync it back to my phone: works But: If I create an Event at KOrganizer it will be synced correctly to ownCloud and my phone. If I edit it at my phone and sync it back to ownCloud nothing happens. There is still the old ical generated from KOrganizer. The ical: https://gist.github.com/magcks/027381e5cb774e72e774 Edit: It doesn’t work on non-recurring events too, I will open up a new issue: #103.
A

2-way sync logic
DAVx⁵ • bug • • AutoImport-napfi

5

0
Votes

5
Posts

1303
Views

R

Also, one of my statements above is wrong: If you delete the entry on the server and change it on your device, the next time DAVdroid syncs it: tries to upload the contact, which will succeed, syncs all entries from the service to the device, including the newly uploaded. “DAVdroid wins” Correct is (I have just tested it): If you delete the entry on the server and change it on your device, the next time DAVdroid syncs it: tries to upload the contact, replacing exactly the old version that is referenced by its ETag, which will not succeed becaues this precondition fails (because the event is gone), syncs all entries from the service to the device, resulting in the locally-changed event to be deleted. “Server wins” So, the server always wins, which is the desired strategy.

1 / 1