-
Notifications
You must be signed in to change notification settings - Fork 173
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
Support multiple type declaration #942
Comments
Hello, I understand this issue is related to the way iOS handles wrongly vCard types when set as a value list (e.g. doesn't handle the syntax like |
Something new in here? |
@Nemental still waiting for kewisch/ical.js#388 |
FIX HAVE BEEN MERGED 🎉 |
Waiting for new ical.js release now |
Next contacts release will fix this :D |
Please help test the new release (link in first post): #1579 |
I'm in the same boat as apastuszak. Tried editing an existing contact & even creating a new one, but still seeing the same issue. I can run through & document all the steps again, but still has not been working for me. Nextcloud 18.0.3 |
Here is what I am seeing. If I create a new contact in Nextcloud and then iOS syncs it, and I export it as vcf, I see this line:
And the iPhone displays "HOME If I then edit the contact and change the phone type to home on the iPhone, the vcf export from Nextcloud shows this:
Either vcf format displays correctly in Nextcloud. |
Yep, the issue is the quote now. Also, this is not released as far as I recall |
How is this progressing? I really cant migrate away from iCloud contacts until this works :-) Good job everybody - sadly i can’t contribute with :[ |
Yes I would also like to know how the status of this is? Currently on NC 20.0.2 and iOS 14.2: |
Any update on this? I see the issue is closed but it's still not resolved. |
Can we get this re-opened since the issue is not resolved? |
This has been an issue for a long time and still is with all current releases as of Feb 5, 2021. Would love for this to get reopened and possibly resolved. |
Looking at the rfc: https://tools.ietf.org/html/rfc6350#section-6.4.1
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: