-
Notifications
You must be signed in to change notification settings - Fork 141
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
Add LOOKUP_KEY #93
Comments
Nice! Thanks for the suggestion. Will look into it shortly. |
Hi @joachim-quis , it is OK if I submit a PR with this parameter added, or you prefer to do it yourself? |
Hello, any updates on this? |
Hi, is there any update on this? what would be the iOS equivalent of this? |
I think on iOS the contact ID is the same even between devices. |
Hi @svprdga - it would be amazing if you could submit a PR actually! I'm happy to review/approve it :) |
Any update on this? I am developing an app for my work and I am struggling to relate contacts added using this plugin with the contacts on our remote database. I am currently using a map in a database to map the contact ID i get after adding the contact using the plugin to the IDs in our remote system but we regularly have problems with contacts being orphaned due to the id changing locally. I am going to have to do a bandaid fix by storing the remote ID in a group or note or something but this feature would be a godsend. |
It would be nice to add the LOOKUP_KEY parameter for each contact.
This identifier seems to be the only way to identify contacts between devices, since the regular ID might change in contact synchronizations and between devices.
This threads explains how to obtain it: https://stackoverflow.com/questions/58118556/get-cross-device-unique-id-for-android-phone-contacts
The text was updated successfully, but these errors were encountered: