-
Notifications
You must be signed in to change notification settings - Fork 5
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
Log name(Cached_name) Mismatch or wrong #10
Comments
Hi, |
Thank you for your comment. I am using name value from the log and I’m getting wrong name. |
What kind of wrong name do you get ? Another one from your contact list ? |
Yes another name from contact as mentioned when it starts from 63... I have gone through the possibilities like checking if I saved the number on both the contacts. I even deleted the contact and tried. Later it took another name say "Name A" was showing before after deleting the contact is showing "Name B". I tried with different phone numbers starts with 6... All shows the same type of issues. |
Hi @umaraliyar, we fixed the cached number in our last 1.3.2 version. Does it solve your problem ? |
Did your problem get resolved? I noticed that if I dial (a random unsaved) number out, it always shows a random contact name (cached_name) with it incorrectly. I keep having this issue on whichever device I test on. I'm just using the example code... Is it just me? Any ideas? FYI: If I delete the contact that is incorrectly shown against the number I dialed, it'll just give another random contact name as the (cached_name) name against the dialed number. >_< |
Hi,
Thanks for the plugin & maintenance. Im using Cordova & Javascript to retrieve log information after passing request permission. I am getting wrong "name" for the right numbers from data return. Esp., number starts with 63... others are ok with proper name. As native Android suggest, should I go search in contact to get the right name? if so im not finding a document to search with this plugin. Guide me.
The text was updated successfully, but these errors were encountered: