Skip to content
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

[Bug] Can display, but not edit, (birth)dates from old phone #201

Open
7 tasks done
PhoenixIV opened this issue Dec 30, 2024 · 12 comments · May be fixed by #202
Open
7 tasks done

[Bug] Can display, but not edit, (birth)dates from old phone #201

PhoenixIV opened this issue Dec 30, 2024 · 12 comments · May be fixed by #202
Labels
enhancement New feature or request

Comments

@PhoenixIV
Copy link

PhoenixIV commented Dec 30, 2024

Checklist

  • I can reproduce the bug with the latest version given here.
  • 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 bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected app version

1.1.0

Affected Android/Custom ROM version

Android 8.1.0 / LineageOS 15.1 AND Android 15 (GrapheneOS)

Affected device model

OnePlus ONE AND Pixel 8a

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

I switched from an old phone.

  1. Installed Fossify Contacts on both
  2. Exported on the old phone (only Fossify Contacts preserved contact image quality during export)
  3. Imported on new phone

Expected behavior

Birthdate also shows up when editing a contact

Actual behavior

Fossify contacts shows the correct birthday of contacts (even calculating the correct age). But when I click edit it suddenly disappears! As if there is no birthday set as soon as I enter edit mode.

This is true on my old and new phone.

This does not happen when I create a new contact.
This does not happen when I export and import a single contact.

Screenshots/Screen recordings

Additional information

No response

@PhoenixIV PhoenixIV added bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Dec 30, 2024
@Aga-C
Copy link
Member

Aga-C commented Dec 30, 2024

Please fill out all required fields in your bug report, not just add - if something's explicitly required.

Also, I have a few questions:

  1. "This is true on my old and new phone." - does it mean, that before exporting you had the same behavior on the old phone?
  2. From which contact source are you exporting contacts, and to which are you importing?
  3. Do you have CardDAV synchronization set on your new phone?

@Aga-C Aga-C added question Further information is requested waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. labels Dec 30, 2024
@PhoenixIV
Copy link
Author

PhoenixIV commented Dec 30, 2024

Please fill out all required fields in your bug report

I am surprised by your request, as this is fully redundant information. I took one or two bug reports in my own projects.
The required information is now added.

  1. Yes, on both phones the birthdays do not show up in edit mode
  2. The contacts were originally set up on my old phone in the default google app (Build-Version 1.7.21) that came with LineageOS. I exported the contacts from Fossify Contacts and imported them with Fossify Contacts.
  3. Yes. I added DAVx5 after deciding it will be easier to sync with my laptop than with .vcf backups

As the problem already exists on the old phone, the export and import could potentially be ignored.

@PhoenixIV
Copy link
Author

This issue becomes more convoluted: I just checked again and it seems only some contacts have this issue. Others don't.

I'd love to send you a data sample, as this is such an interesting bug. I just don't know how without exposing my whole address book.

If this only happens to me I am also fine with just setting up broken contacts again.
I already tried deleting all Fossify App Data and starting again.

@Aga-C
Copy link
Member

Aga-C commented Dec 30, 2024

I'd love to send you a data sample, as this is such an interesting bug. I just don't know how without exposing my whole address book.

VCF file is in a text format, so you can just send the contacts with this issue (entry starts with BEGIN:VCARD and ends with END:VCARD). If you anonymize the name and phone number (but leaving birthdays as they are), you can paste it here on GitHub.

The contacts were originally set up on my old phone in the default google app (Build-Version 1.7.21) that came with LineageOS.

As I understand, it wasn't synchronizing contacts with any account before adding DAVx5? This bug could happen because there were two instances of the same contact in two different contact sources, where one had a birthday set, the other doesn't.

Also, in Fossify Contacts, can you uncheck in Settings an option for merging duplicate contacts? Do you have only one instance of each contact?

@PhoenixIV
Copy link
Author

PhoenixIV commented Dec 30, 2024

I just updated the original report with screenshots.
Only then I noticed it was not only the birthdate, but also a second phone number field.

Editing other fields and saving the contact (e.g. change name from Henner to Henner2) preserved the bug: They were still not visible in edit view, but still in normal view.

I already had a look in the .vcf file. Nothing I saw.
I removed all contacts but two. One which worked, one with the bug. When I imported them into the phone account (Not DAV) both worked.

Unfortunately when I then removed the duplicates via Fossify, it also deleted them in the DAV account. When I added them again to the DAV account the bug was also gone.

By the way: When I used google contacts on my new phone the same contact that bugged with fossify worked with the other contacts app.

This bug could happen because there were two instances of the same contact

I made sure the contacts only exist in one account on the new phone.

@Aga-C
Copy link
Member

Aga-C commented Dec 30, 2024

I made sure the contacts only exist in one account on the new phone.

Telegram and Signal are also contact sources for Fossify Contacts. When you tap Edit, it opens the contact from the first source. It's possible that in your case, it turned on editing Signal or Telegram contact. If you still have this example from the screenshot, just scroll down a bit lower - it should show where the edited contact is stored. Is it your normal storage or Signal/Telegram?

@PhoenixIV
Copy link
Author

In case of my new phone it is always the DAV account.
I always excluded all other accounts from view and re-checked.

I'd be fine with closing this ticket as it seems I am the only one with this behaviour. I can help myself with alternative solutions. In case someone ever experiences this again I am happy if this ticket can be found.

@Aga-C Aga-C removed question Further information is requested waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. labels Dec 30, 2024
@leonp5
Copy link

leonp5 commented Jan 3, 2025

I have the problem too.
I always sync my contacts via DAVx5.
If I view a contact the address is shown. If I edit, the address is missing.
As @Aga-C said, if I scroll down, in my case WhatsApp is taken as contact source for editing and not the DAV Account.
Is there a workaround or a setting for this?

@Aga-C
Copy link
Member

Aga-C commented Jan 3, 2025

@leonp5

 As @Aga-C said, if I scroll down, in my case WhatsApp is the taken as contact source for editing and not the DAV Account.
Is there a workaround or a setting for this?

When viewing contact (not in the edit mode), at the bottom you can see all storages where the contact is saved. If you tap on any of them, you will enter the edit mode for this particular contact instance.

@leonp5
Copy link

leonp5 commented Jan 3, 2025

Thank you @Aga-C 🙂

@PhoenixIV
Copy link
Author

PhoenixIV commented Jan 3, 2025 via email

@Aga-C
Copy link
Member

Aga-C commented Jan 3, 2025

Probably the best solution for this issue is to change the behavior of the current edit button:

  • If the contact is stored in different sources than WhatsApp/Signal/etc., it shouldn't enter editing the messenger contact.
  • If the contact is only stored in a messenger, then edit it.
  • Behavior of editing the particular contact storage shouldn't be modified, only the edit for the whole merged contact.

There's also a similar request solving this problem differently, that may be done in the future: #22.

@Aga-C Aga-C added enhancement New feature or request and removed bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants