-
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
[FEATURE] Export by a date range #82
Comments
Hi. Today I tested the changes you made in the dev branch and I thought they were amazing. However, there was an exception error, regarding the timezone_offset parameter that you try to assign a value to in the dataModel Message. I have a little knowledge of Python and, from what I've seen, your code tries to assign a value to an attribute that doesn't exist, thus generating the exception. When I commented out the line that made this assignment, the application worked without problems. The exception occurs on line 346 of the android_handler.py file. I hope, in some way, to be contributing to the project. |
Can you post the stack traceback and the command you used? |
I used the following command in question
The traceback was this
The exception persists even if I pass a value for time-offset using the argument "--time-offset -3" |
Could you please check the |
Hey! I redid the tests, because I realized that I was having a conflict between the dev version and the main version on my machine. By redoing the tests correctly, I was successful. There was no error now. |
I will leave this open until next release. |
Is your feature request related to a problem? Please describe.
I want to create a repository on Google Drive with my conversations, creating a folder for each year, however, the tool does not allow me to extract the conversations for a date range.
Describe the solution you'd like
An option to inform the interval for extracting messages would be very welcome.
Additional context
An example would be the command:
wtsexporter -d --between 2022-01-01 00:00 - 2023-01-01 00:00
The text was updated successfully, but these errors were encountered: