You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My problem, on a One Plus running Android 9, is that if I have a contact ("John") that was created through the phone, I then create (ContactsService.addContact) a contact through the app with the exact same name ("John"), which results in a combined contact between these two. This is not so much of an issue and is probably just how the phone works. The issue is when I want to delete (ContactsService.deleteContact) the app-created contact through the app, it also deletes the old phone-created contact.
@danijelzolic1 thanks for the comment and question. Unfortunately, as you pointed out, it's related to the phone. There are hacks to differentiating contacts created with your app.
Yes, every device is different but, at least on Android, this is because of fetching the "CONTACT_ID" instead of "RAW_CONTACT_ID".
I did a local change in the library to use RAW_CONTACT_ID and now it only deletes the app-created contact.
Just wanted to put this here if other people stumble on this issue.
Hi,
First of all, great plugin. Makes life easy.
My problem, on a One Plus running Android 9, is that if I have a contact ("John") that was created through the phone, I then create (ContactsService.addContact) a contact through the app with the exact same name ("John"), which results in a combined contact between these two. This is not so much of an issue and is probably just how the phone works. The issue is when I want to delete (ContactsService.deleteContact) the app-created contact through the app, it also deletes the old phone-created contact.
Not sure if the case is the on iOS.
So my question is, is there any solution to this?
I assume this is related to:
http://android-contact-id-vs-raw-contact-id.blogspot.com/
The text was updated successfully, but these errors were encountered: