mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #1026] Beginning July 8, 2020, SMS Backup+ will no longer have access to your Gmail data #817
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#817
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 @jmorgannz on GitHub (Jun 30, 2020).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1026
I removed the issue template as this relates to a google policy issue and it's effect on SMS Backup+, not a sequence of events leading to a reproducible bug.
Today I received this email:
@bferrell commented on GitHub (Jul 2, 2020):
I got the same message. I've found this to be enormously useful. Please don't allow it to die
@al-right commented on GitHub (Jul 4, 2020):
I got a similar message too.
Too bad Google did not write what the problems were as to qualify and pass the verification process or where to find the specific details about the problems they identified.
@kurahaupo commented on GitHub (Jul 8, 2020):
@al-right actually Google have said: the short version of the reason that SMS Backup+ has not been granted access to the Gmail "sensitive scope" is that it is not an app whose primary purpose is to be a user-focused email client.
That's a somewhat intractable problem to overcome.
The fact that it never sends email actually counts against it.
@kurahaupo commented on GitHub (Jul 8, 2020):
@jmorgannz @bferrell @al-right I'm guessing you're on G-suite accounts, so you've had an extra year. Welcome to the rest of the world. :-(
We have a fair work-around, though it involves the user enabling 3rd-party IMAP access to their Gmail account, which is not ideal.
Further details on issue #959.
@jmorgannz commented on GitHub (Jul 8, 2020):
@kurahaupo I'm not on G-suite. Regular consumer gmail here.
@al-right commented on GitHub (Jul 8, 2020):
@kurahaupo I'm not on G-suite either. Also regular consumer gmail here. I did #973 back when Google kicked my instance of SMS Backup+ from accessing my account in August 2019 and it has worked ever since without having to re-authenticate. I will try to re-authenticate when they finally kick me this time and see if the Firefox trick still works. But I guess eventually I have to surrender to another method unless SMS Backup+ could get a simple send email/check email functionality... Beggars belief - I know ;)
@al-right commented on GitHub (Jul 19, 2020):
I can confirm today that trying to connect using https://github.com/jberkel/sms-backup-plus/issues/973#issuecomment-521420655 using XOAuth2 does no longer work. Firefox tells that login with google is temporarily deactivated for this app (SMS Backup +). The exact wording in English I do not have (because it is written in Danish, my first language.)
Too bad, but that is how things are. :)