Contacts: Migration does not include special characters

[theTux]

Hi,

some time ago I migrated my data as far as possible from an old Murena device to a new one. Contacts have been migrated almost successfully via the built-in backup/restore feature as described in the migration howto[1].

Today I saw that there is one special contact which didn’t get restored correctly. The contact contains a service number used to fetch some provider information. The service number starts with a star sign and ends with a hash sign. Both have not been migrated, but the rest of the number is still there. Is this easily fixable?

[1] How to Backup and Restore your /e/OS phone

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

[tcecyk]

worth a bugreport. If you have export .vcf from the old phone still around, the full vcard entry (obfuscated with other numbers etc) from begin: to end: would help to file the bug

BEGIN:VCARD
VERSION:4.0
PRODID:+//IDN bitfire.at/..
FN:Firstname Lastname
N: Lastname;Firstname;;;
TEL;TYPE=cell:+41 123 456
END:VCARD

[theTux]

I deleted everything from the migration after everything worked. But it should be easy to reproduce this if the issue appears on every service number. In my case its *144# which was reduced to 144 within the migration.

[tcecyk]

gave this a try and added that number, it did import properly though

BEGIN:VCARD
VERSION:4.0
PRODID:+//IDN bitfire.at/..
FN:Firstname Lastname
N: Lastname;Firstname;;;
TEL;TYPE=cell:*144#
END:VCARD

(it’s handled by these rfcs: RFC 6350: vCard Format Specification / RFC 3966: The tel URI for Telephone Numbers )

[theTux]

Thank you for testing this. I could imagine that this is only an issue between the two affected versions. Export ran on 3.4 (Murena Two), import on 3.5 (Fairphone 6).