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

iOS contact sync is wrong #941

Closed
Olgsi opened this issue Feb 18, 2019 · 16 comments
Closed

iOS contact sync is wrong #941

Olgsi opened this issue Feb 18, 2019 · 16 comments
Labels
needs info Not enough information provided

Comments

@Olgsi
Copy link

Olgsi commented Feb 18, 2019

Hello, everyone,

I like to use nextcloud and would like to sync my contacts with iOS here.
That works too, but nextcloud shows me wrong fields in iOS. Zb Work or Home, instead of work and private.
If I create a new contact under iOS, nextcloud doesn't recognize the fields either.

Do you have the same problem?

@nextcloud-bot

This comment has been minimized.

@Olgsi
Copy link
Author

Olgsi commented Feb 18, 2019

No it's not the same. In the past i don't see it like "WORK or that contacts don't show the adress but iOS does.

@skjnldsv skjnldsv added bug Something isn't working needs info Not enough information provided labels Feb 19, 2019
@skjnldsv
Copy link
Member

Hello @Olgsi !
Thanks for your report. So if I understand, the name of the field si different for home and private?
Work is still properly displayed on both, right?

If so, this is just a difference of translations. Private and Home is the same.

@skjnldsv skjnldsv removed the bug Something isn't working label Feb 19, 2019
@Olgsi
Copy link
Author

Olgsi commented Feb 19, 2019

Hi @skjnldsv,

in attach I send you an example. :)
I create a new contact in iOS and this is what I get in nextcloud.

2019-02-19 10-15-46-1

2019-02-19 10-15-46-1

@Olgsi
Copy link
Author

Olgsi commented Feb 19, 2019

And that I got, when I create a new contact in nextcloud (another bug: when I create a new field for work number, nextcloud will change all fields and insert a mail adress to the new work phone number field).

2019-02-19 10-29-04-1

@Olgsi
Copy link
Author

Olgsi commented Feb 19, 2019

I think here is something strange. :D

@andreas51
Copy link

I noticed the same behaviour with my Nextcloud installation and iOS devices. Afair it started after the upgrade from Nextcloud 14 to 15 (and Contacts 2.x to 3.x). Could this be related to the way Apple groups vCard attributes by prefixing them with the string "item"? E.g.
ITEM1.EMAIL;TYPE=HOME:user1@example.com
item1.TEL;type=pref:+49 40 1234567

@skjnldsv
Copy link
Member

@Olgsi could you post the Test test 2 contact vcf file here?

For the ITEM.XXXX stuff this is a duplicate of #42

@Olgsi
Copy link
Author

Olgsi commented Feb 19, 2019

Of course.

Test Contact.zip

@skjnldsv
Copy link
Member

Got it, this is because we need support for multiple TYPE.
See the issue: kewisch/ical.js#343

Let me check if this is a duplicate issue :)

@skjnldsv
Copy link
Member

Created a dedicated ticket: #942

@Olgsi
Copy link
Author

Olgsi commented Feb 19, 2019

OK thanks. So I can't do anything and have to wait for an update right?

@skjnldsv
Copy link
Member

@Olgsi Well, the issue is not on our side and iOS is not helping by choosing a way to store things that are basically almost never used anywhere else :(

I'm curious to see what we could do.
The best would be to at least have things properly displayed on nextcloud, but that would mean repairing the failing contacts and therefore making it looks like this screenshot 😕

Could you try 852DCBCF-A2F3-44ED-A91F-353D478CA3ED.txt ? See how it looks on iOS?

@Olgsi
Copy link
Author

Olgsi commented Feb 19, 2019

In the past it works well, but when you can't do anything and iOS can't work with this format..than i have to wait until it will work.

In the preview it looks the same as before. :(
Siri can't handle "WORK.

2019-02-19 16-10-59-1

@Olgsi
Copy link
Author

Olgsi commented Feb 20, 2019

Now it's closed, but there is no solution right?

@skjnldsv
Copy link
Member

@Olgsi no, the ticket for this issue is in #942 now :)
More detailed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs info Not enough information provided
Projects
None yet
Development

No branches or pull requests

4 participants