Skip to content
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

Open
Ilya-Ezhik opened this issue Mar 7, 2024 · 23 comments
Open

🐞 [BUG] Error restoring a SMS backup copy #70

Ilya-Ezhik opened this issue Mar 7, 2024 · 23 comments
Labels
bug Something isn't working help wanted Extra attention is needed important

Comments

@Ilya-Ezhik
Copy link

When trying to restore an SMS from a backup, an error occurs when reading the copy file.

Steps to reproduce the behavior:

  1. Go to "Menu --> Backup"
  2. Click on "Restore"
  3. Select the copy file
  4. Click "OK"

The dialog box will contain a description of the error "it is impossible to read the backup file"

  • Device: Samsung Galaxy A22 5G (as well as all other devices)
  • OS: Android 13, One UI Core 5.1 (and other Android OS
  • App Version 4.0.7 (latest)

Screenshot_20240307_022132

@Ilya-Ezhik Ilya-Ezhik added the bug Something isn't working label Mar 7, 2024
@octoshrimpy
Copy link
Owner

Looking now.

@Ilya-Ezhik
Copy link
Author

Looking now.

Thanks! There is also a problem with group SMS sending, but for this probably need to open a new topic?

@octoshrimpy
Copy link
Owner

re is also a problem with group SMS sending, but for this probably need to open a new topic?

yes please.

@octoshrimpy
Copy link
Owner

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?

@Ilya-Ezhik
Copy link
Author

it never writes a backup.

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)

@Ilya-Ezhik
Copy link
Author

Idid this work with QKSMS?

Yes, in that application, a backup is created and successfully restored! Without problems!

@octoshrimpy
Copy link
Owner

it never writes a backup.

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)

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.

@Ilya-Ezhik
Copy link
Author

and you can open the json with another file viewer/editor without problem?

Yes! I open it on phone using the MT Manager app without any problems! :)

Screenshot_20240308_002309_MT Manager

@edent
Copy link

edent commented Mar 18, 2024

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:

{
	"messageCount": 765,
	"messages": [
		{
			"address": "+447700900123",
			"body": "I need to order a cake for my friend's birthday in a few days.♡",
			"date": 1703340489087,
			"dateSent": 0,
			"locked": false,
			"protocol": 0,
			"read": true,
			"status": -1,
			"subId": 3,
			"type": 1
		},

Although it starts with a few "blank" entries like:

		{
			"address": "",
			"body": "",
			"date": 1511875195000,
			"dateSent": 1511875195000,
			"locked": false,
			"protocol": 0,
			"read": true,
			"status": -1,
			"subId": -1,
			"type": 2
		},
		{
			"address": "+4407700900321,
			"body": "",
			"date": 1511875284000,
			"dateSent": 1511875284000,
			"locked": false,
			"protocol": 0,
			"read": true,
			"status": -1,
			"subId": -1,
			"type": 1
		},

(Phone numbers replaced with fakes by me)

@esan0
Copy link

esan0 commented Mar 20, 2024

Same issue.

@octoshrimpy
Copy link
Owner

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.

@octoshrimpy octoshrimpy added help wanted Extra attention is needed important and removed waiting for reply labels Mar 20, 2024
@octoshrimpy octoshrimpy changed the title [BUG] Error restoring a SMS backup copy 🐞 [BUG] Error restoring a SMS backup copy Mar 31, 2024
@octoshrimpy octoshrimpy pinned this issue Mar 31, 2024
@engelhro
Copy link

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!

@SanskritFritz
Copy link

Just a heads-up, a workaround: QKSMS is able to restore the backups made with QUIK.

@engelhro
Copy link

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.

@b-risk
Copy link

b-risk commented Jun 2, 2024

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"

@antistress
Copy link

Same bug here with latest version from F-Droid (4.0.7) on my new Galaxy S10e with lineage-20.0-20240608-nightly
And same workaround : I had to use QKSMS to import the backup file and then QUIK to synchronise itself with QKSMS

@Saarsk
Copy link

Saarsk commented Jun 21, 2024

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.

@MoralCode
Copy link

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.

@rafnov
Copy link

rafnov commented Oct 23, 2024

Same on me.
Successfuly created backup .json (quite small - 1,17 MB) on Realme 7 Pro, uploaded to Google drive, then downloaded od Realme GT Neo 2 and tried to restore: unable to read a file. 😟
Any chances for soon fix? It's been some time since Quik was updated...

@wrenix
Copy link

wrenix commented Oct 25, 2024

I use https://github.com/tmo1/sms-ie for this Problem now

@rafnov
Copy link

rafnov commented Oct 25, 2024

Ok, it worked perfectly for me too, but that doesn't fix anything in Quik.

@Renarde-dev
Copy link

Renarde-dev commented Nov 11, 2024

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 :
If you want to use my script it's available on my forgejo instance : https://forgejo.la-taniere-solidaire.gay/Renarde/SMS_Import_script

[Edit : I forgot to make the script public ><]

@dex2000
Copy link

dex2000 commented Nov 12, 2024

FYI: it was broken in 4.06 too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed important
Projects
Status: Ready
Development

No branches or pull requests