mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-26 09:25:55 +03:00
[GH-ISSUE #409] When only restoring call log SMS Backup+ still requests SMS write rights #342
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#342
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 @RoadXY on GitHub (Dec 9, 2013).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/409
I always first restore 200 SMS messages, after that I restore 200 call log entries.
Even though I deselect the option to restore SMS messages, SMS backup+ still pops up a message for write request in the SMS database.
@jberkel commented on GitHub (Dec 9, 2013):
is this for the current beta?
@RoadXY commented on GitHub (Dec 9, 2013):
Yes, it is.