-
Notifications
You must be signed in to change notification settings - Fork 31
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
🐞 [BUG] Error restoring a SMS backup copy #70
Comments
Looking now. |
Thanks! There is also a problem with group SMS sending, but for this probably need to open a new topic? |
yes please. |
looks like this may be because quik never asked for access to files, only media. it never writes a backup. I'm assuming it's the same problem when importing a backup. did this work with QKSMS? |
When creating a backup, it creates a JSON file in the selected folder on the phone with all SMS (headers from the phone number and SMS text)! And then he can't read it (described above) |
Yes, in that application, a backup is created and successfully restored! Without problems! |
and you can open the json with another file viewer/editor without problem? I wonder if I have remnants of some debug build from testing directly from android studio that is interfering. mine isn't storing the file at all, which is even worse. |
I'm having the same issue. Both phones are use V4.0.7. I have manually copied across the JSON file. When I try to open it in the app I get the error "Couldn't read backup file". I can create a backup into a specific folder. But if I try to read that newly created backup on the same phone, I get that error. The JSON file is valid and look like:
Although it starts with a few "blank" entries like:
(Phone numbers replaced with fakes by me) |
Same issue. |
looking into it. I have some large life changes coming up in the next couple months so I cannot guarantee a fix soon, but am trying to find the issue. |
Any news on this issue? I'm affected as well. Switched from one phone to a new one today, and now I can't import my backup and all its messages. Would be really nice if this could be fixed 👍. Thanks a lot for a short update! |
Just a heads-up, a workaround: QKSMS is able to restore the backups made with QUIK. |
Yeah, I've seen that afterwards and it indeed helped to solve my issue! 😀 The problem existing in QUIK but not already in QKSMS should hopefully help the developer to more easily identify and fix the problem. Would still be nice to see a working restore functionality also in the "revived" app which is QUIK. |
Hi, I'm having a similar issue too, I made a backup with this revived app on my phone and I transferred it to my computer, after wiping my phone (so no making a new backup) and installing GrapheneOS and restoring from the file in settings it gives an error where it says "couldn't read" |
Same bug here with latest version from F-Droid (4.0.7) on my new Galaxy S10e with lineage-20.0-20240608-nightly |
Here was my workaround:I used the app "SMS Import / Export" available from F-Droid. You might want to check the Readme. There were no issues for me, but if you have group messages etc. there might be issues. All I did was tap "import" and it appeared in QUIK. I see there's an option in QUIK to re-synch with the native SMS database. |
This seemed to work for me, and also seemed to import MMS, which I suspect the built in importer doesn't do. |
Same on me. |
I use https://github.com/tmo1/sms-ie for this Problem now |
Ok, it worked perfectly for me too, but that doesn't fix anything in Quik. |
I could wait for a release and SMS-IE didn't work for me so I wrote a quick script to convert backups to Fossify Messages and used it to import my messages : [Edit : I forgot to make the script public ><] |
FYI: it was broken in 4.06 too |
When trying to restore an SMS from a backup, an error occurs when reading the copy file.
Steps to reproduce the behavior:
The dialog box will contain a description of the error "it is impossible to read the backup file"
The text was updated successfully, but these errors were encountered: