You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Get a vcard that includes a custom label for a phone number. The custom label must have lower and upper case characters, for example Custom Label.
Import the vcard.
Notice that the custom label has become all lowercase, for example custom label.
Expected behavior
The custom label should be preserved verbatim. In the example, it would be Custom Label.
Actual behavior
The custom label is changed to all lowercase, for example custom label.
Screenshots/Screen recordings
No response
Additional information
My use case is exporting all my contacts from one phone and importing them on another phone, both using Fossify Contacts. I have verified that export is correct; the .vcf file contains the custom label as written in the app. Import is buggy as described above.
I have tested this both with my actual contact data and with a specially prepared test vcard. The test vcard is attached for your convenience (zipped to allow GitHub upload). It only contains one contact, with name set to "AAAAName AAAALastname".
We rely for parsing on ez-vcard library and it returns the lowercased type. Probably that's a bug there, or it's done on purpose - in the vCard specification, type is always lowercased.
Checklist
Affected app version
1.1.0
Affected Android/Custom ROM version
GrapheneOS
Affected device model
Google Pixel 8
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
Custom Label
.custom label
.Expected behavior
The custom label should be preserved verbatim. In the example, it would be
Custom Label
.Actual behavior
The custom label is changed to all lowercase, for example
custom label
.Screenshots/Screen recordings
No response
Additional information
My use case is exporting all my contacts from one phone and importing them on another phone, both using Fossify Contacts. I have verified that export is correct; the .vcf file contains the custom label as written in the app. Import is buggy as described above.
I have tested this both with my actual contact data and with a specially prepared test vcard. The test vcard is attached for your convenience (zipped to allow GitHub upload). It only contains one contact, with name set to "AAAAName AAAALastname".
test_vcard_AAAA.zip
The text was updated successfully, but these errors were encountered: