-
Notifications
You must be signed in to change notification settings - Fork 66
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
Crash when content id is not found #61
Comments
Hi. Could you post the value of |
Sorry for overtaking this issue, but I have just tried and face the same bug. The The issue seems to be also affecting the To fix the issue temporary, I have currently added the c.execute("""SELECT COALESCE(ZFROMJID, ZTOJID) as _id,
ZWAMESSAGE.Z_PK,
ZISFROMME,
ZMESSAGEDATE,
ZTEXT,
ZMESSAGETYPE,
ZWAGROUPMEMBER.ZMEMBERJID,
ZMETADATA,
ZSTANZAID
FROM ZWAMESSAGE
LEFT JOIN ZWAGROUPMEMBER
ON ZWAMESSAGE.ZGROUPMEMBER = ZWAGROUPMEMBER.Z_PK
LEFT JOIN ZWAMEDIAITEM
ON ZWAMESSAGE.Z_PK = ZWAMEDIAITEM.ZMESSAGE
WHERE _id is NOT NULL;""") Media query c.execute("""SELECT COALESCE(ZWAMESSAGE.ZFROMJID, ZWAMESSAGE.ZTOJID) as _id,
ZMESSAGE,
ZMEDIALOCALPATH,
ZMEDIAURL,
ZVCARDSTRING,
ZMEDIAKEY,
ZTITLE
FROM ZWAMEDIAITEM
INNER JOIN ZWAMESSAGE
ON ZWAMEDIAITEM.ZMESSAGE = ZWAMESSAGE.Z_PK
WHERE ZMEDIALOCALPATH IS NOT NULL AND _id is NOT NULL
ORDER BY _id ASC""") However, I could not verify if it causes any corruption due to my message history being insanely huge (venv) sunnylo@SunnyLos-Laptop % ./venv/bin/wtsexporter -i -b ~/Library/Application\ Support/MobileSync/Backup/asdf
WhatsApp directory already exists, skipping WhatsApp file extraction.
Processing contacts...(548)
Processing messages...(245452/245452)
Processing media...(128019/128019)
Processing vCards...(51/51)
Generating chats...(564/564)
Copying media directory...
Everything is done! Hope it will be fixed soon, thanks for the great library, love it |
Hi @LoSunny. Thanks for your workaround. Since |
This fix also changed how to determine if the message belongs to a group or PM.
Yep it "works" sunnylo@SunnyLos-Laptop WhatsApp-Chat-Exporter % wtsexporter -i -o result2 -b ~/Library/Application\ Support/MobileSync/Backup/asdf
WhatsApp directory already exists, skipping WhatsApp file extraction.
Processing contacts...(548)
Processing messages...(245452/245452)
Processing media...(128019/128019)
Processing vCards...(51/51)
Generating chats...(548/548)
Copying media directory...
Everything is done! However, it seems to have generated less chats than before, from 564 to 548? I have ran a
On the other hand, the $ diff -r result result2
161c195
< <p>Not supported WhatsApp internal message</p>
---
> <p>The group name changed to asdf</p> |
I believe 548 is the correct number. AFAIK, each message should be mapped to the table
Well😄That's unintended. |
After I double check with the messages, it indeed exists in other group chat, so yeah it should be correct now. hou yea 🤩 |
For example:Assuming the user Before the fix:
After the fix:
|
okie. learn a lot of new stuff tdy. |
If it is related to #64, could you provide some more details & screenshots to that issue? Also, as I mentioned in another issue, I don't currently have access to the latest iOS WhatsApp, so its difficult for me to reproduce the problem and debug that. |
I will leave this open until next release. |
When you have Whatsapp and migrate to Whatsapp business or the opposite, some records will lose its ids and python doesn't like it here.
The text was updated successfully, but these errors were encountered: