mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #562] dismiss "Could Not Connect" notification at next scheduled backup #475
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#475
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 @Lx on GitHub (Jun 5, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/562
During times of no data signal, scheduled backups will necessarily fail and a notification to the effect of "could not connect" will appear.
I often see this notification many successful backups later, and I start diagnosing connectivity issues before realising that there's no issue to diagnose at this time.
Coding the notification to be removed when the next scheduled backup commences would prevent the notification from being displayed when there's no actual problem.
@jberkel commented on GitHub (Jun 12, 2015):
can you try with 1.5.9-BETA6 ? https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.9-BETA6
@Lx commented on GitHub (Jun 12, 2015):
Thanks. I've installed it and I'll let you know if I have any issues, although the intermittent nature of my underlying network means it might take a while.
@Lx commented on GitHub (Jul 10, 2015):
Seems to be working well. I've had a few intermittent network dropouts, and the notification hasn't persisted past network restoration.