-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
KeyError: 'conversationId' when exporting #162
Comments
Thanks for reporting. If anyone can investigate what is going on here that would be great. It'll likely be a little while before I get the time to properly look into this. |
@carderne - see #144 (comment) and the following comments from me. This issue seems to confirm that it is due to a change in Signal (updated a few days ago). I'll submit a pull request for this error shortly. |
Also getting this error now. Looking forward to a new release with the PR merged! |
After updating to version 3.4.1, the error has disappeared (everything runs fine to the end) BUT there are missing data. |
@coppolab - can you provide some details:
I have not delved into if recent messages are missing before this or not... but will try to cut out some time later this week to dig into it. |
@yarko thanks for your additional effort, here is the requested info:
|
Desktop (please complete the following information):
Describe the bug
Last week sigexport was working for me. This week I get this error:
I'm upgraded to the latest version (v3.2.2).
Maybe Signal changed something?
The text was updated successfully, but these errors were encountered: