mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 08:55:54 +03:00
[GH-ISSUE #710] Restore IO Error #598
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#598
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 @ragnardannes66 on GitHub (Jan 29, 2017).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/710
Successfully backed everything up, did a factory reset stock marshmallow (Dec 2016)
App will still backup any new messages I get/send, but if I try to restore it just says calculating and then goes to an IO Error
My first thought was that I have too many messages. I went into restore settings and set it to just 100 messages and still having the same issue.
@tmfa commented on GitHub (Feb 19, 2017):
I am having the same issue. I can back up all SMS and MMS. When I try to restore, I get an I/O error. Changing the number of texts to restore makes no difference.
@taps007 commented on GitHub (Feb 28, 2017):
Yes I have exactly the same issue on my Pixel (7.1.1)
@parker5635 commented on GitHub (May 30, 2017):
675
@LittleTimmyHartwell commented on GitHub (Dec 10, 2017):
Same problem. LG TP450, Android 7
@jberkel commented on GitHub (Dec 19, 2017):
Duplicate of #675