Feature Request: Preserve unsupported VCF fields during import/export to avoid data loss

[iddq]

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Feature description

Currently, Fossify Contacts discards unsupported VCF fields (e.g., PHOTO). This causes data loss when exporting contacts again.
Suggestion: Keep all unsupported fields in the database even if they are not shown in the UI, so they can be preserved on export

Why do you want this feature?

avoid data loss

Additional information

No response

[naveensingh]

Currently, Fossify Contacts discards unsupported VCF fields (e.g., PHOTO).

PHOTO is not discarded. Please provide some example fields that were discarded in your case.

[iddq]

It is definitely an export problem. The photo is visible.

[Aga-C]

@iddq In which storage the contact is stored?

[iddq]

fossify contacts' internal storage

[Aga-C]

In Phone storage (not visible by other apps)?

[iddq]

Yes, correct. I would like to note that currently this runs under the name 'Phone Storage' in the program, which is quite misleading, and I would rather recommend introducing the name mentioned above!

[Aga-C]

This is a known bug: #209.

Are there any other fields that are not preserved during import/export?

[iddq]

Alright. Maybe there’s nothing else. But I’ll let you know once the photo is exported. As I mentioned, it would be good if the unknown fields aren’t discarded during the import either

[naveensingh]

I checked. There are some fields that are not yet supported. Will post later.

[naveensingh]

Those missing fields will be handled as part of #85. Closing this as PHOTO is working as expected.