[GH-ISSUE #538] Crash ("SMS Backup+ stopped working") when trying to backup #456

Closed
opened 2026-02-26 01:30:38 +03:00 by kerem · 6 comments
Owner

Originally created by @sputtene on GitHub (Feb 27, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/538

Hi,

Since Jan 12th SMS Backup+ crashes when I try to manually backup or when I restart my phone and the SMS Backup+ service gets started (which triggers an automatic backup, I assume).

I've cleared the cache and data through the Android manage apps menu, but it still crashes.

I'm using a regular IMAP server, not a GMail account for my backup. It worked for over 6 months with SMS Backup+, so I think that's not the problem.
I'm running SMS Backup+ 1.5.8, installed from F-Droid. My Android version is 4.2.2.

If I can help you with extra debugging logs or you need more information, I'd be happy to provide them to you.

Originally created by @sputtene on GitHub (Feb 27, 2015). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/538 Hi, Since Jan 12th SMS Backup+ crashes when I try to manually backup or when I restart my phone and the SMS Backup+ service gets started (which triggers an automatic backup, I assume). I've cleared the cache and data through the Android manage apps menu, but it still crashes. I'm using a regular IMAP server, not a GMail account for my backup. It worked for over 6 months with SMS Backup+, so I think that's not the problem. I'm running SMS Backup+ 1.5.8, installed from F-Droid. My Android version is 4.2.2. If I can help you with extra debugging logs or you need more information, I'd be happy to provide them to you.
kerem 2026-02-26 01:30:38 +03:00
  • closed this issue
  • added the
    v1.5.8
    label
Author
Owner

@jberkel commented on GitHub (Mar 3, 2015):

I think there was a broken version posted on f-droid for some time. Could you post the full stack trace?

<!-- gh-comment-id:76876429 --> @jberkel commented on GitHub (Mar 3, 2015): I think there was a broken version posted on f-droid for some time. Could you post the full stack trace?
Author
Owner

@sputtene commented on GitHub (Mar 3, 2015):

I've enabled Sync log and Extra debug information in the advanced settings, sms_backup_plus.log is created.
After I trigger the crash by pressing the Backup button in the main UI screen, the log file is 0 bytes.

Is there another way to get a stack trace?

<!-- gh-comment-id:76923223 --> @sputtene commented on GitHub (Mar 3, 2015): I've enabled `Sync log` and `Extra debug information` in the advanced settings, `sms_backup_plus.log` is created. After I trigger the crash by pressing the `Backup` button in the main UI screen, the log file is 0 bytes. Is there another way to get a stack trace?
Author
Owner

@jberkel commented on GitHub (Mar 3, 2015):

you need to run "adb logcat" from the console. for this you'll need to install the android sdk unfortunately, unless you have a rooted phone.
i would just try to reinstall 1.5.8 from f-droid, because there was a published version with a crash.
(#525 #523).
@krt16s, does auto-upgrade for the broken version work?

<!-- gh-comment-id:76931538 --> @jberkel commented on GitHub (Mar 3, 2015): you need to run "adb logcat" from the console. for this you'll need to install the android sdk unfortunately, unless you have a rooted phone. i would just try to reinstall 1.5.8 from f-droid, because there was a published version with a crash. (#525 #523). @krt16s, does auto-upgrade for the broken version work?
Author
Owner

@sputtene commented on GitHub (Mar 3, 2015):

adb logcat shows the same error and stacktrace as described in #525.

The f-droid status page for SMS Backup+ states that version 1.5.8 was released on 17 Jan, so it's more recent than the version I have installed.
I'll reinstall, test and report.

<!-- gh-comment-id:76934418 --> @sputtene commented on GitHub (Mar 3, 2015): `adb logcat` shows the same error and stacktrace as described in #525. The f-droid status page for SMS Backup+ states that version 1.5.8 was released on 17 Jan, so it's more recent than the version I have installed. I'll reinstall, test and report.
Author
Owner

@sputtene commented on GitHub (Mar 3, 2015):

Removing and reinstalling version 1.5.8 from f-droid fixed it.

Thanks!

<!-- gh-comment-id:76935178 --> @sputtene commented on GitHub (Mar 3, 2015): Removing and reinstalling version 1.5.8 from f-droid fixed it. Thanks!
Author
Owner

@ghost commented on GitHub (Mar 3, 2015):

Unfortunately not, since the versioncode is the same. We can force an updated VC on our side, but try to avoid it because upstream might use this VC as well someday. :/

<!-- gh-comment-id:76943893 --> @ghost commented on GitHub (Mar 3, 2015): Unfortunately not, since the versioncode is the same. We can force an updated VC on our side, but try to avoid it because upstream might use this VC as well someday. :/
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/sms-backup-plus-jberkel#456
No description provided.