Name changes lost when using CardDAV and UI

[nWRqenkF]

Steps to reproduce

1. Create a new contact using Android contact app with the name "Aaaa Test" (use the single input field). (After this step android automagically fills the first name with "Aaaa" und the last name with "Test")
2. Synchronize Android with OC
3. Edit the name of the contact in OC UI to "Bbbb Btest"
4. Synchronize Android with OC
5. View contact in Android contact app

Expected behaviour

The contact is shown as "Bbbb Btest" (or "Btest, Bbbb" depending on your app preferences) in the android contact app in the contacts list and in the contact detail view.

Actual behaviour

The contact is still displayed as "Aaaa Test" in the android contacts app contact list.
When you edit the contact, you can see, that OC changed the name field to "Bbbb Btest", but left the first and last name fields unchanged.
As the android contact app (at least my cyanogenmod 12.1) shows the fields first name and last name in the contact list and in the contact detail view, the changes in the OC UI are well hidden.

Server configuration

Operating system: Debian Wheezy

Web server: nginx

Database: MySql

PHP version: 5.6.17

ownCloud version: (see ownCloud admin page) 9.0.0

Contacts version: (see ownCloud apps page) 1.0.0.0

Updated from an older ownCloud or fresh install: Updated from 8.2 from official apt-repositories

Client configuration

Browser: Firefox 44.0

Operating system: Windows 7

CardDAV-clients: DavDroid

[DeepDiver1975]

Oh - yes - this is the missing sync of FN and N - THX for reporting

[macmeck]

I think it's the same issue if you create a contact in the OC UI and then sync it to Thunderbird using the SoGo connector. First name and last name fields are empty, only display name is being set. Therefore Thunderbird cannot display the contact properly.

[sebastianhaberey]

+1 for fixing this. As a first-time ownCloud user, I thought I was going crazy today. Naturally, I assumed I was not using ownCloud right. Turns out it's a bug.

[phsc84]

Shouldn't this issue be fixed with #437?

[phsc84]

Ping... This is fixed with #437, isn't it? Furthermore, I think that #437 alone would justify a new release as it affects the CardDAV sync, which probably is widely used.

[DeepDiver1975]

Ping... This is fixed with #437, isn't it?

form my pov it's at least one step closer ....