mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #1024] Error: System shows future date in backup #818
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#818
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 @android987987 on GitHub (Jun 25, 2020).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1024
Originally assigned to: @kurahaupo on GitHub.
Recent messages not backing up because last backup date shows July 7, 2020 which is in the future (today is June 25, 2020)
@kurahaupo commented on GitHub (Jun 26, 2020):
Any chance your cellular provider messed up the clock on your device?
@android987987 commented on GitHub (Jun 26, 2020):
Hi Martin,
I don't think the carrier is the problem. I haven't had any other issues.
I uninstalled and reinstalled the app.
Same problem persists today. I attached a screenshot I just took. The app
updated the mms & call log today. The sms date is still incorrect.
Thanks for replying!
On Fri, Jun 26, 2020, 6:52 AM Martin Kealey notifications@github.com
wrote:
@kurahaupo commented on GitHub (Jun 28, 2020):
I'm considering the case where the clock in your phone is wrong for a brief period, during which a backup occurs. Unless you're looking at the phone at the time you probably wouldn't notice anything. And yes, phone carriers do screw up their clocks quite often.
Then to avoid overloading the IMAP server, SMS Backup+ does not make another backup until a minimum time after the previous backup - which happens to be 2 weeks in the future.
Restarting or even reinstalling the app won't help so long as that "lasted backed up" time is still recorded.
The problem will resolve itself in 9 days' time, but I will see if I can track down where the last-backed-up date is stored.
@kurahaupo commented on GitHub (Jul 10, 2020):
@android987987 can you confirm that backups have returned to normal operation as the "future" date has now passed?
(I will continue to investigate in case anyone else encounters this problem.)
@android987987 commented on GitHub (Jul 10, 2020):
Yes they have. Thank you!
On Thu, Jul 9, 2020, 7:34 PM Martin Kealey notifications@github.com wrote:
@haroldong8 commented on GitHub (May 8, 2022):
I have a similar problem. I received an SMS dated for the year 2221, so SMS Backup is stuck until that time. Unlike the first poster, I can't wait this out! Can someone help suggest a resolution?
@kurahaupo commented on GitHub (May 9, 2022):
@haroldong8 Some possibilities include:
Fortunately
SMS Backup+doesn't store messages on your phone, just its settings and its next-time-to-run timestamp, so clearing the app data isn't the end of the world. Just make sure you've written down the settings including the app password first - or you could generate a new app password and revoke the old one.Reminder: Google's IMAP server is
imap.gmail.com, notimap.google.com.