Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CardDAV / DAVdroid / Contacts-App issue #1537

Closed
AndyScherzinger opened this issue Sep 27, 2016 · 11 comments
Closed

CardDAV / DAVdroid / Contacts-App issue #1537

AndyScherzinger opened this issue Sep 27, 2016 · 11 comments

Comments

@AndyScherzinger
Copy link
Member

The following review/issue has been reported on the Play store for the Android app but is not related to the app itself, since we "just" help setting up DAVdroid, so this is rather related to a combination of CardDAV / DAVdroid / Contacts-App. So looping in @rfc2822 for the DAVdroid side of life.

Very chic but CardDAV problems The new integration with DavDroid must still be considered an experiment as long as the interaction with the Contacts app are shot to pieces on the server Before / surnames and birthdays

Original review

Sehr schick aber CardDAV Probleme Die neue Integration mit DavDroid muss noch als Experiment angesehen werden solang im Zusammenspiel mit der Contacts-App auf dem Server Vor/Nachnamen und Geburtstage zerschossen werden

@nickvergessen
Copy link
Member

I guess there is no further information what was "shot to pieces"?

@AndyScherzinger
Copy link
Member Author

Unfortunately no, I replied to the play store review also referencing to this tracker issue and can ask if he would be willing to join this discussion here.

@Po2le
Copy link

Po2le commented Sep 28, 2016

Hi,

I'm the original reviewer. I wanted to point out that the combination of DAVdroid/NextCloud
might damage contacts.

The bugs seem to be well known, but it might not be clear which component is causing them in all cases.

owncloud/contacts#466
owncloud/contacts#276
owncloud/contacts#324

Even if this is all the fault of owncloud/contacts or DAVdroid, it is still the solution the
nextcloud-android-app is "advertising" at the moment.

@AndyScherzinger
Copy link
Member Author

AndyScherzinger commented Sep 28, 2016

Hi @Po2le thanks for joining the discussion. I didn't intent to leave the impression that the Android development team is explaining away, rather than pushing the discussion/search into the right direction as-in server-side/app-related. @jancborchardt know anyone who could get involved here? The contacts app doesn't seem to be maintained by the Nextcloud community but to some extend by oC

@nickvergessen
Copy link
Member

I will have a look at those 3 issues

@tessus
Copy link

tessus commented Oct 5, 2016

Yep, the contacts app is a mess. I opened an issue owncloud/contacts#435, where I explained the problems, but guess what. It was closed and all my valid points ignored.

This is one of the reasons why I still use oc 8.2.7. I can't afford to screw up my contacts. Otherwise I would have migrated to oc 9.x (back then) or nextcloud (now) a long time ago.

@Po2le
Copy link

Po2le commented Dec 15, 2016

Hi, just tested with NC11 and DAVdroid 1.3.4.1 and as far as I am concerned all issues solved 😃

Thanks for the great work you are doing

@jancborchardt
Copy link
Member

@Po2le awesome, great to hear! :)

@AndyScherzinger As far as I know @LukasReschke and @rullzer work on the server side of this. And the Contacts app is done by @nextcloud/contacts :)

@jancborchardt
Copy link
Member

jancborchardt commented Dec 15, 2016

@tessus the correct link to the Contacts app is https://github.com/nextcloud/contacts ;) – also, in the issue you linked everything was explained. It helps to be friendly, and calling the app which was developed by awesome volunteers »a mess« is not really cool.

@tessus
Copy link

tessus commented Dec 15, 2016

@jancborchardt Great, thanks. This looks very promising. I will try to do a test migration from oc 8.2.7 to nc 11.0.0. I hope I find a way to do this somehow. Cheers.

@MorrisJobke
Copy link
Member

This issue seems to be resolved -> closing :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants