starred/sms-backup-plus-jberkel

Fork 0

mirror of https://github.com/jberkel/sms-backup-plus.git synced 2026-04-25 17:05:59 +03:00

[GH-ISSUE #909] Completely Broken for Months. #711

New issue

Open

opened 2026-02-26 01:31:25 +03:00 by kerem · 11 comments

kerem commented

2026-02-26 01:31:25 +03:00

Owner

Originally created by @KyleSanderson on GitHub (Jul 13, 2018).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/909

Before you report your issue, please consider perusing the https://github.com/jberkel/sms-backup-plus#faq and searching the issues page to see if it has already been reported.

Expected behaviour

Messages would be backed up.

Actual behaviour

Nothing is backed up.

Steps to reproduce the behaviour

Press the backup button.

Please specify the following:

Android version
8
Phone model / brand
Pixel
SMS Backup+ version installed
Latest
Messaging app
Latest

Originally created by @KyleSanderson on GitHub (Jul 13, 2018). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/909 Before you report your issue, please consider perusing the [https://github.com/jberkel/sms-backup-plus#faq](FAQ) and searching the issues page to see if it has already been reported. ### Expected behaviour Messages would be backed up. ### Actual behaviour Nothing is backed up. ### Steps to reproduce the behaviour Press the backup button. ### Please specify the following: * Android version 8 * Phone model / brand Pixel * SMS Backup+ version installed Latest * Messaging app Latest

kerem added the

labels

2026-02-26 01:31:25 +03:00

kerem commented

2026-02-26 01:31:25 +03:00

Author

Owner

@jcrben commented on GitHub (Jul 14, 2018):

Thanks for the report! I cannot reproduce this with my setup using Pulse SMS (https://messenger.klinkerapps.com/) on an LGv20 running Android 7.0.

I probably can't help debug this, but note the FAQ https://github.com/jberkel/sms-backup-plus#faq-backup-automatic-backup:

When reporting a bug related to auto backup it is essential to attach a sync log file. See the relevant FAQ for more information on how to do this.

Without more information, we will close this eventually.

However, even with more information, we cannot guarantee a fix. Any help you can provide in debugging is appreciated.

@jcrben commented on GitHub (Jul 14, 2018): Thanks for the report! I cannot reproduce this with my setup using Pulse SMS (https://messenger.klinkerapps.com/) on an LGv20 running Android 7.0. I probably can't help debug this, but note the FAQ https://github.com/jberkel/sms-backup-plus#faq-backup-automatic-backup: > When reporting a bug related to auto backup it is essential to attach a sync log file. See the relevant FAQ for more information on how to do this. Without more information, we will close this eventually. However, even with more information, we cannot guarantee a fix. Any help you can provide in debugging is appreciated.

kerem commented

2026-02-26 01:31:26 +03:00

Author

Owner

@KyleSanderson commented on GitHub (Jul 15, 2018):

I've reverted back to 1.5.10 and it works perfectly... Backup and Restore does not work at all on Oreo with the sub-release that's pinned as stable.

https://i.imgur.com/sLz1fjz.png None of the objects are actually backed up that are mentioned in the log.

@KyleSanderson commented on GitHub (Jul 15, 2018): I've reverted back to 1.5.10 and it works perfectly... Backup and Restore does not work at all on Oreo with the sub-release that's pinned as stable. https://i.imgur.com/sLz1fjz.png None of the objects are actually backed up that are mentioned in the log.

kerem commented

2026-02-26 01:31:26 +03:00

Author

Owner

@jberkel commented on GitHub (Jul 16, 2018):

Weird. My guess would be a permission problem, but it should show up in the log. Can you manually verify that SMS Backup+ has been granted permission to read SMS? Somewhere in the Android preferences. (on a second thought; this makes no sense – it probably wouldn't be able to get the message counts if the permissions were missing)

@jberkel commented on GitHub (Jul 16, 2018): Weird. My guess would be a permission problem, but it should show up in the log. Can you manually verify that SMS Backup+ has been granted permission to read SMS? Somewhere in the Android preferences. (on a second thought; this makes no sense – it probably wouldn't be able to get the message counts if the permissions were missing)

kerem commented

2026-02-26 01:31:26 +03:00

Author

Owner

@KyleSanderson commented on GitHub (Jul 16, 2018):

SMS Backup+ has full permissions. I just backed up 30k messages on 1.5.10, there seems to be a breaking point where it will only handle 5k messages (I've been using this since I had my Galaxy Nexus; so it's my favourite app and is blocking me from actually flipping to Apple) but doing them in the 7 chunks got me there. Auto Backup looks like it works on the old version; the new version just wouldn't do anything at all.

@KyleSanderson commented on GitHub (Jul 16, 2018): SMS Backup+ has full permissions. I just backed up 30k messages on 1.5.10, there seems to be a breaking point where it will only handle 5k messages (I've been using this since I had my Galaxy Nexus; so it's my favourite app and is blocking me from actually flipping to Apple) but doing them in the 7 chunks got me there. Auto Backup looks like it works on the old version; the new version just wouldn't do anything at all.

kerem commented

2026-02-26 01:31:26 +03:00

Author

Owner

@KyleSanderson commented on GitHub (Jul 22, 2018):

Any update on this? Play Store keeps trying to update me to the completely busted version.

@KyleSanderson commented on GitHub (Jul 22, 2018): Any update on this? Play Store keeps trying to update me to the completely busted version.

kerem commented

2026-02-26 01:31:26 +03:00

Author

Owner

@jberkel commented on GitHub (Jul 24, 2018):

@KyleSanderson I need more information to be able to debug this. The logs you posted didn't show any error messages, which is strange. Does it return immediately when you press backup?

@jberkel commented on GitHub (Jul 24, 2018): @KyleSanderson I need more information to be able to debug this. The logs you posted didn't show any error messages, which is strange. Does it return immediately when you press backup?

kerem commented

2026-02-26 01:31:26 +03:00

Author

Owner

@KyleSanderson commented on GitHub (Jul 24, 2018):

Pretty much unfortunately, the counter rapidly dwindles.

@KyleSanderson commented on GitHub (Jul 24, 2018): Pretty much unfortunately, the counter rapidly dwindles.

kerem commented

2026-02-26 01:31:26 +03:00

Author

Owner

@KyleSanderson commented on GitHub (Sep 10, 2018):

Confirming this is still completely broken on Android Pie. Any chance at getting the play store version reverted to two years ago when this worked?

@KyleSanderson commented on GitHub (Sep 10, 2018): Confirming this is still completely broken on Android Pie. Any chance at getting the play store version reverted to two years ago when this worked?

kerem commented

2026-02-26 01:31:26 +03:00

Author

Owner

@KyleSanderson commented on GitHub (Jan 8, 2019):

@jberkel my old Pixel literally melted... new handset shows massive GUI issues with this app and nothing else. There's likely nothing wrong with the core but the GUI library that this was re-written to use.

@KyleSanderson commented on GitHub (Jan 8, 2019): @jberkel my old Pixel literally melted... new handset shows massive GUI issues with this app and nothing else. There's likely nothing wrong with the core but the GUI library that this was re-written to use.

kerem commented

2026-02-26 01:31:26 +03:00

Author

Owner

@galstaf commented on GitHub (Feb 6, 2019):

1.5.1.1 is dead for me too. Just noticed no SMS backups since June of 2018 after the update. Tried XOAuth and manual configuration and the error comes back as "IMAP not enabled" on the gmail side. But it is.

With manual configuration it just says invalid username and password, but I have confirmed all is correct.

Are you still working on this project, @jberkel ?

@galstaf commented on GitHub (Feb 6, 2019): 1.5.1.1 is dead for me too. Just noticed no SMS backups since June of 2018 after the update. Tried XOAuth and manual configuration and the error comes back as "IMAP not enabled" on the gmail side. But it is. With manual configuration it just says invalid username and password, but I have confirmed all is correct. Are you still working on this project, @jberkel ?

kerem commented

2026-02-26 01:31:26 +03:00

Author

Owner

@kurahaupo commented on GitHub (Apr 27, 2020):

@galstaf there is a trickle of progress - a 1.6β release is available on Play Store, but if that doesn't fix it then we're going to need volunteers who can install off-market apps in their phones, as it's impossible to solve this kind of problem without being able to instrument the devices where it's occurring.

(The project has a few contributors besides @jberkel, so it's not dead, but the rest of us don't have a signing key to add releases to Play Store or FDroid.)

@kurahaupo commented on GitHub (Apr 27, 2020): @galstaf there is a trickle of progress - a 1.6β release is available on Play Store, but if that doesn't fix it then we're going to need volunteers who can install off-market apps in their phones, as it's impossible to solve this kind of problem without being able to instrument the devices where it's occurring. (The project has a few contributors besides @jberkel, so it's not dead, but the rest of us don't have a signing key to add releases to Play Store or FDroid.)