-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Number labels are shown as "HOME, "CELL or "WORK on iOS if created in WebGUI #25485
Comments
I believe this is a duplicate of nextcloud/contacts#942 |
When I create or modify a contact and download this from the contact app as vcf-file I get this:
As written in the mentioned issue #942 in the RFC 6350 - Section 6.4.1 the line with the telephone number is correct (Value-List with quotation mark), but in https://tools.ietf.org/html/rfc6350#section-6.7.9 is the version field defined with this value: So I take a look in this RFC 2426 - Section 3.6.9 and here is specified, that the value-list doesn't have quotion-marks. So I think there is a bug in cration of the vcf-structure. It must be checked if this should correspond to the RFC 6350 (V 4.0) or to RFC 2426 (V3.0). I tried to change the Version-Attribute to 4.0 - With this modification iOS will import the contact correct. |
Is there any hope of a solution to the problem? Or is this feature only used by a few people? |
See german discussion in forums as well https://help.nextcloud.com/t/auf-handy-steht-statt-mobil-nun-cell-usw/52601 |
This issue might be a duplicate of nextcloud/contacts#1107 and #25485 Since this issue affects probably all ios users - and users of other popular clients like EM too - it should be investigated with a higher priority. Won't it be enough to set the version attribute in the vcards to "4.0" or alternatively remove the quotes from the value lists? |
same problem. No solution yet? |
No, the nextcloud developers continue to sleep soundly and have been doing so since 2018. |
I have just upgraded from NextCloud 13.x to NextCloud 20.0.2 on my personal webspace instance. To be more precise, I did a new clean install and then moved the data of two users manually by exporting the address book and re-importing it. After having done this the iOS devices re-synced the contacts and now I also see those strange labels on every contact card, which is quite annoying! So this issue is new to me and it is sad to see that this issue and the related ones are pending since 2018 :-/ |
Lets track this in nextcloud/contacts#1107 |
How to use GitHub
General Information to this issue
This issue is also discussed in the nextcloud forum (https://help.nextcloud.com/t/auf-handy-steht-statt-mobil-nun-cell-usw/52601).
Because it seems to be an issue with CardDAV it needs to be reported here and not at nextcloud/contacts.
Steps to reproduce
Expected behaviour
The labels should be "Privat", "Mobil" and "Arbeit" as they are called in the WebGUI and in the contacts that have been created in the iOS contacts app.
Actual behaviour
The labels are called "HOME, "CELL or "WORK in iOS contacts app. (All starting with an apostrophe)
Server configuration
Operating system: Ubuntu 20.04 LTS (Linux 5.4.0-65-generic x86_64)
Web server: Apache/2.4.41 (Ubuntu)
Database: maria db 10.3.25
PHP version: PHP 7.4.3
Nextcloud version: 20.0.7
Updated from an older Nextcloud/ownCloud or fresh install: fresh install
Where did you install Nextcloud from: https://nextcloud.com/install/#instructions-server (Archive File)
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: no, internal
Are you using encryption: no
Are you using an external user-backend, if yes which one: none
Client configuration - WebGUI
Browser: Google Chrome Version 88.0.4324.146 (Offizieller Build) (64-Bit)
Operating system: Windows 10 Home 20H2
Client configuration - iOS
Operating system: iOS 14.3 / iPhone 11 Pro
Logs
Because it seems that there is not an exception or error but an issue in the data, I do not provide logs for now. If you need the logs to investigate I will try to create a clean log, without connection tries of other devices.
The text was updated successfully, but these errors were encountered: