-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Contact Details Not Resolving, Phone Number Only #62
Comments
This software interacts with the iMessage database only; contacts are not stored inside of it. This tool only targets features that are directly related to the iMessage tables. |
@DevMan01 not really a direct solution but you can try making this a script to run through all your conversations with numbers and possibly have success with this? https://apple.stackexchange.com/questions/72652/contacts-app-command-line-interface |
Such an ability would make this tool so much more useful to me—I get that this software itself will only access the iMessage database, but if someone were to write a script using the tool @paulasyn mentioned it would be awesome. (A pity I don't have the skills to do it myself!) |
I know this is was late, but I cobbled this script up and it's worked for me... no guarantees, but if it helps anybody:
|
Thanks for this awesome tool, @ReagentX! On the outside chance it's useful to someone... I have a personal Python script for wrangling contact information, and I just added a feature to update the imessage-exporter files with contact info pulled from a collection of vCard files. It's in this repo, added in this commit. I don't expect it to be directly usable by anyone, but it points a possible direction to go for other tools. |
When I run:
imessage-exporter -f html -o /Users/...
The tool successully exports and builds the export, with one exception - All of HTML files, and chat mentions are titled or addressed using individuals phone numbers, and not their contact name in the MacOS Contacts.
Is this a bug? User error? Or a feature that needs to be developed?
The text was updated successfully, but these errors were encountered: