mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #965] Permission is required: Access SMS Messages #764
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#764
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 @boxorandyos on GitHub (Jul 10, 2019).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/965
Originally assigned to: @jberkel on GitHub.
I have my Google Pixel XL running version QPP5.190530.014 and I just received a security update. After installing the update I got a notification that says Permission problem: the following permission is required: Access SMS Messages.
I have allowed this app all permissions.
It has always worked before this latest update.
I always keep everything updated.
I am running the very latest version of SMS Backup+ that it shows available in the play store version 1.5.11.
Android version 10, all updates installed.
Stock Google Messaging app.
-randall
@partounian commented on GitHub (Jul 18, 2019):
Confirmed issue also affects Q DP5 for the Pixel 2 XL.
@krknopp commented on GitHub (Jul 18, 2019):
And Pixel 3 on Android Q DP5.
@jaxidian commented on GitHub (Jul 19, 2019):
In case it's useful info, I'm seeing the same behavior with TiBu (an older APK) on both a Pixel 3 and Pixel 3 XL. Worked fine on DP2 on both phones but not on DP3.
@kurahaupo commented on GitHub (Oct 3, 2019):
Does it keep asking, or was that a one-off?
Google adjusts the Android permissions system from time to time, and newly created permissions are not automatically granted to any app, even if the user previously said "grant all".
@boxorandyos commented on GitHub (Oct 3, 2019):
In my case the messages always displayed.
Again speaking in my case I have checked a few times to make sure that all permissions are granted. So even if any new ones came along I would see that.
@kurahaupo commented on GitHub (Nov 9, 2019):
This is possibly a duplicate of #958.
There was a change to some permission handling in Android Q which required a patch to the app.
Please try the new beta version (1.6.0-BETA1).
@boxorandyos commented on GitHub (Nov 9, 2019):
Different error message received at a separate time than #958 but unknown if it was the same root cause.
I can confirm that I just tried this for the first time since 1.6.0-BETA1 and this issue is now resolved and the app is working again.