-
Notifications
You must be signed in to change notification settings - Fork 39
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
call_history file malformed #1
Comments
Is it a recent encrypted backup, created from iOS13 by iTunes on Windows? Is the decryption password definitely correct (i.e. try an invalid password just to check you do see an error)? How did you verify the SQLite file was malformed? You could also try these projects, which are also copies of the underlying Google library: |
# For some reason, certain files seem to have a "Size" attribute # that does not match up to the true byte length of the file, # leading to actual data being truncated incorrectly. # Instead, use the latest version of the Google code that implements # removal of RFC 1423 CBC padding correctly, and ignore reported # file size. # This is likely the cause of #1.
@ArifJezir; I think I have reproduced this issue and fixed it. If you try using the latest version from GitHub, do you still have the same issue? |
I believe this is now fixed. Please re-open with more details if not. |
Thanks it's working !!!!! |
Thanks it's working!!!!!
…On Tue 17 Mar, 2020, 4:36 PM James Sharkey, ***@***.***> wrote:
I believe this is now fixed. Please re-open with more details if not.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AILYMS6C6VV6ODZ6B7GNFRTRH5KVDANCNFSM4KGRYH3Q>
.
|
call_history.sqlite -> file was not open sqlite db
The text was updated successfully, but these errors were encountered: