mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #1058] SMS Backup + is not Automatically backing up. Settings appear correct and manual works #844
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#844
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 @FanOfNoMan on GitHub (Apr 4, 2021).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1058
Before you report your issue, please consider perusing the FAQ and searching the issues page to see if it has already been reported.
Expected behaviour
(edited) Backups should occur automatically
Actual behaviour
(edited) SMS Backup + is not automatically backing up.
Steps to reproduce the behaviour
(edited) Settings appear correct and manual works
Device details
@JenBcute commented on GitHub (May 25, 2021):
Is this not automatically backing up anymore only because I have Android 11?
Is there any work around to fix this?
@kurahaupo commented on GitHub (Jun 11, 2021):
Likely duplicate of #954
@kurahaupo commented on GitHub (Jul 8, 2021):
Thanks everyone for the feedback.
Using the new Oreo JobScheduler API is on the roadmap.
I'm marking this as a duplicate of #758 just so we can track one issue and keep all the feedback in one place.