-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Inadvertently creating duplicate birthday events when importing birthdays from contacts #206
Comments
Where do you store your contacts? Do you modify contacts in any way between imports? Also, please provide your specific device model. |
I've now retested the app and indeed, no duplicates appear. My bad, I should've tested it more thoroughly. Should I cancel this bug report? The only bug now, if we can classify it as that, is after removing the birthday from a contact (in this case, the contact I modified for the test) it is not automatically removed from the calendar, even after tapping again on I have the stock contacts app on a Pixel 8. |
There's already a similar issue: #194, so we are aware that this synchronization needs a refinement. |
Similar problem with teracube and iode-os. |
Checklist
Affected app version
1.0.3
Affected Android/Custom ROM version
Android 14
Affected device model
All
How did you install the app?
GitHub releases
Steps to reproduce the bug
Expected behavior
The event for the birtdays would be added only once, and the duplicates would not be added or would be merged. So, if one taps n times the import button at any n moments, there should still be only one event of each birthday for every contact.
Actual behavior
For every contact there are n events created (with n taps on the import button), and there is not a way, or a button, or a setting to automatically merge all birthdays for all contacts for every year in the calendar.
Screenshots/Screen recordings
No response
Additional information
The only way to solve this is to delete the birthdays event tab completely and re-import all the birthdays, which is slightly inconvenient. It would be nice if there was a simple check to prevent this behaviour from happening.
Also, I haven't tried with anniversaries or other types of events, but I suspect the behaviour might be the same.
The text was updated successfully, but these errors were encountered: