mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #538] Crash ("SMS Backup+ stopped working") when trying to backup #456
Labels
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#456
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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?
@sputtene commented on GitHub (Mar 3, 2015):
I've enabled
Sync logandExtra debug informationin the advanced settings,sms_backup_plus.logis created.After I trigger the crash by pressing the
Backupbutton in the main UI screen, the log file is 0 bytes.Is there another way to get a stack trace?
@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?
@sputtene commented on GitHub (Mar 3, 2015):
adb logcatshows 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.
@sputtene commented on GitHub (Mar 3, 2015):
Removing and reinstalling version 1.5.8 from f-droid fixed it.
Thanks!
@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. :/