-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Signal crashes on restoring backup #13506
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
any news on this? I think this should not be closed, as there is apparently an issue with old backups, likely affecting other users as well. |
Hey I am also having this issue. I decided to give Signal one more try after a couple of years, and now restore won't work. |
Are y'all able to capture logs with adb logcat or some other tool to see what the crash is? The OP log link doesn't have any crash data in it. |
@cody-signal I have attached my logs here : crash_logs.zip
|
something that may help in debugging - |
Thanks for the additional information and the troubleshooting steps, we'll do our best to figure this out. |
Hi! I also have this issue when attempting to restore (valid/functioning) backups from 2021 and 2020 (Backup db version 105 and 44 respectively). The restore seems to go fine, then crashes at the last block. Restoring into an older version of Signal using an old APK appears to work fine, however I can't register/verify my number as it gives an "Unable to connect to service" toast, preventing me from getting in and updating it post-restore (attempts to do so cause crashes or it puts me back to the pre-restore welcome screen) Let me know if I can help provide additional info. I'd really like to restore these backups - my newer ones are all corrupted for some reason, despite semi-regular backing up over the last year or so. I wish Signal had a way to check backup integrity without wiping and restoring the app (or using another phone I suppose) -would have saved me some stress! Many thanks :) |
Hi! Since I recently started using the MacBook with M1 Chip and ARM64 architecture, I couldn't even use signal backup tool to verify which db Version my backup was using. What worked to restore the backup, however, was installing an old version of the android app. Before it always crashed, after loading the local backup file which was 4.2GB large and entering the Passphrase. I checked the date that my Signal Backup was created (in my case September 2024) What I want to check is, if updating the Android Signal app and then making a new backup in that version will make it restorable in newer versions of Signal too... Hope that helps. |
Bug description
Signal crashes on restoring a (valid) backup file. In particular when starting restoring from a file backup, messages seems to be processed and imported correctly. However afterwards, Signal crashes repeatedly on startup and cannot be started anymore, i.e. Android reports that the app is crashing repeatedly responding.
I've verified that the backup is intact with 3rd party tools (signal-backup-tools). I've also verified that the passphrase is correct; in particular I was able to extract all messages with signal-backup-tools (https://github.com/bepaald/signalbackup-tools) to text format and verified that all information is present. I've also tried to (re)write the backup using backup-tools in order to check that the backup file is not corrupted.
The database version as reported from signal-backup-tools: 136
Signal-Version: 7.2.4
The backup is from 2022; so I suspect that there is some issues when handling such "old" backups.
The backup contains personal information, but I am willing to help w.r.t. debugging this issue in any way I can
Steps to reproduce
Actual result: Signal crashes and can't be started anymore
Expected result: Should restore the backup and start as expected
Screenshots
unfortunately I have no screenshot
Device info
Device: Pixel 6a
Android version: 14
Signal version: 7.2.4
Link to debug log
signal-log-1712506609190.zip
attached to this report
The text was updated successfully, but these errors were encountered: