-
-
Notifications
You must be signed in to change notification settings - Fork 260
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
Serious bug = Data loss: deleting contact actually removes all entries withe the same name #872
Comments
|
@tibbi I have just tested it here: the problem happens either if I delete the contact while it is selected in the list or viewing the contact details, but not when editing the contact that will be deleted (edit first, then delete). By the way, there is also a bug that once the keyboard shown while editing an item, the top bar with the icons is moved upwards and gets somewhat hidden, it's required to hide the keyboard (or "go back" ) first in order to be able to save. |
right, so that isnt a bug. Edit screen deletes just the specific contact instance, but View screen or the list view deletes them all |
@tibbi I am sorry, but this is not the expected behavior nor what the vast majority of other similar apps do: if a contact is selected (or active in the details view) and delete is used then only the selected (or active) item us supposed to be removed. There is no info anywhere that all items with the same name will be removed. Just to be clear, not even the option to merge contacts was enabled, so deleting all items with the same name is not the expected behavior at all. |
Hello! I think this issue should be re-open.
In fact, if you want to move a large amount of contact from
One solution can be:
Thank you for this app, I think this can be a great upgrade :) |
Yes, this causes data loss and should be changed. There's no info anywhere that deleting the contact being viewed will also delete every other contact with the same name. |
the fact that the contact will be deleted from all contact sources is written directly at the confirmation dialog. |
In french it is only written "Are you sure to delete the contact?" |
thats when you delete from the Edit screen, only 1 single contact is deleted. Multiple ones are deleted only at the View Details screen |
@tibbi Sorry, but you still didn't get it... You do not have many contacts with the same first name, people you do not ask their last name, etc? For instance, I have three contacts named Tibor, with different phone numbers and addresses, they have the same name but they are different contacts. If I remove one of them from the contacts list, all of them are deleted, causing data loss. There is no info anywhere warning that this will happen! Of course, there is a warning that deleting a contact will remove it from the list, but there no info anywhere that all three contacts with the same named (Tibor) will be deleted from the app! Any user is expecting that only the contact being displayed will be deleted, but this action deletes all contacts with the same name as the one being deleted. |
I tested all the delete cases, and I have the same result (duplicated contacts from different accounts are all deleted) and the same french warning message |
Also, every other existing Contacts app (as well as any other app with items shown on a list that can be selected and deleted) only deletes the item that is being displayed. There is no reason at all to silently delete all items with th same name. This is not expected and not user friendly. |
I'm agree with the idea that deleting all contacts with a related name isn't what I expect a contacts app to do (any app actually). When I want to delete an entry, I want only this entry to be deleted, not other entries that the application think are related. Deleting "related" entries is kind of evil actually :/ |
Hello!
Once again, thank you for providing the apps for free, the private contacts lists is a great idea. I wanna report a serious bug regarding contact management in Contacts 6.21.0 Pro. How to reproduce the problem:
This is a serious problem, I hope this can be fixed soon.
Regards
The text was updated successfully, but these errors were encountered: