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
Environment:
iOS 18.2.1
WhatsApp 2.24.25.89
Unencrypted iTunes backup to Windows 11 24H2
Python 3.13.1
Same behavior for main and dev branches as of 1/18/25
The generated chat histories have multiple "Not supported WhatsApp internal Message" entries.
I could find the following events for which they are generated, but there could be others:
Call log entries (missed calls, successful calls) in the chat itself. A separate Call History is generated successfully.
End-to-end encryption messages (which might be intentional based on other issues)
Messages about changes in security codes (which might be intentional based on other issues)
Message about someone leaving a WhatsApp group
In addition, when someone is added to a group, or a group member changes their phone number, the message in the chat history states:
"The group name changed to [email protected]" (with 12223334444 being the phone number added or changed to)
Steps to reproduce the behavior:
Just run the program in the environment specified.
Thank you for this great tool!
The text was updated successfully, but these errors were encountered:
Environment:
iOS 18.2.1
WhatsApp 2.24.25.89
Unencrypted iTunes backup to Windows 11 24H2
Python 3.13.1
Same behavior for main and dev branches as of 1/18/25
The generated chat histories have multiple "Not supported WhatsApp internal Message" entries.
I could find the following events for which they are generated, but there could be others:
In addition, when someone is added to a group, or a group member changes their phone number, the message in the chat history states:
"The group name changed to [email protected]" (with 12223334444 being the phone number added or changed to)
Steps to reproduce the behavior:
Just run the program in the environment specified.
Thank you for this great tool!
The text was updated successfully, but these errors were encountered: