mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-26 09:25:55 +03:00
[GH-ISSUE #6] Disable auto-backup during restore #6
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#6
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 @florx on GitHub (May 20, 2010).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/6
Hi,
When SMS are restored, the program then backs up when it has just restored, this creates duplicates in GMail!
Jake.
@jberkel commented on GitHub (May 21, 2010):
you mean it automatically triggers a back up after a restore?
@florx commented on GitHub (May 21, 2010):
No, during restore. I had 2711 items and it started backing up what had just restored. I've now got duplicates of all sms in GMail
@jberkel commented on GitHub (May 21, 2010):
do you have automatic back up enabled?
@florx commented on GitHub (May 22, 2010):
When I started the restore it was on, however I turned it off while it was still restoring.
When I turned it back after the restore it continued to backup all of the sms on the phone (which at that point was just the restored ones)
@jberkel commented on GitHub (Jul 11, 2010):
I added a guard against this case. a new version should be released soon, with some other fixes.
@florx commented on GitHub (Jul 13, 2010):
Great! Thanks :)