mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #456] Old sms not restoring #385
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#385
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 @melissamedina1 on GitHub (Jun 9, 2014).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/456
I've used the software for years. I recently got the Samsung s4 and tried to restore from my gmail account and it says its restoring 1884 messages however only one comes in stating that they are all duplicates. Has anyone had this issue and how do I fix?
@Quinnavere3 commented on GitHub (Jun 10, 2014):
I'm having the same issue. Been trying to read old posts to see if there's a fix but so far I've come up with nothing.
@junedalton commented on GitHub (Jul 16, 2014):
I a getting the same problem on my Galaxy Note 3. also many XOAuth login problems (seems to lock after a certain amount of time). any ideas? where do I send the log file?
specifically If I request 100 SMS to be restored I get 1 and 99 duplicates. Also I don't get anything in the message, just the telephone number. XOAuth authentication will work for the first time, then it will have a login authentication error on subsequent tries after the calculation period.
@melissamedina1 commented on GitHub (Jul 17, 2014):
I don't know... No one from that company has ever responded to me.
On Wed, Jul 16, 2014 at 4:33 AM, junedalton notifications@github.com
wrote:
Melissa Medina melissamedina1@gmail.com
@jberkel commented on GitHub (Dec 28, 2014):
fixed in 1.5.6
@chrisspar commented on GitHub (May 12, 2019):
Not fully restoring on 1 SMS contact. I followed all the FAQ, restoring and archiving details provided, but still can't restore it.