mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
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#458
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 @eriji on GitHub (Mar 9, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/539
Original issue #524 from Pseudomous:
Hello, this was working great but suddenly got the XOAuth error. IMAP is enabled. While I do have 2-step verification enabled, the program worked fine with it before. Please help. Have deleted and reinstalled but same error... many thanks.
i have a oneplus one phone.
I have a Samsung Galaxy S4
I'm having the same problem as pseudomous above. I have 2-step verification, SMS Backup+ worked until Dec 14, then stopped working. Have not been able to get this working since.
Get "XOAuth authorization error. Please make sure you enabled IMAP in your Gmail account settings"
IMAP is and has been enabled.
Here is the Log:
03-08 20:08 Backup requested (manual)
03-08 20:08 Starting backup (MANUAL)
03-08 20:08 Backing up (916 SMS, 0 MMS, 163 call log)
03-08 20:08 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://XOAUTH2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=0, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true, typesToBackup=[SMS, MMS, CALLLOG, WHATSAPP]}
03-08 20:08 need to perform xoauth2 token refresh
03-08 20:08 error refreshing token: com.zegoggles.smssync.auth.TokenRefreshException: android.accounts.AuthenticatorException: User intervention required. Notification has been pushed., cause=android.accounts.AuthenticatorException: User intervention required. Notification has been pushed.
03-08 20:08 Authentication error: Command: sensitive; response: #2# [NO, [ALERT], Invalid credentials (Failure)](exception: com.fsck.k9.mail.store.XOAuth2AuthenticationFailedException: Command: sensitive; response: #2# [NO, [ALERT], Invalid credentials %28Failure%29])
03-08 20:08 BackupState{currentSyncedItems=0, itemsToSync=0, backupType=MANUAL, exception=com.fsck.k9.mail.store.XOAuth2AuthenticationFailedException: Command: sensitive; response: #2# [NO, [ALERT], Invalid credentials (Failure)], state =ERROR}
03-08 20:08 Backup finished
03-08 20:10 Backup requested (manual)
03-08 20:10 Starting backup (MANUAL)
03-08 20:10 Backing up (916 SMS, 0 MMS, 163 call log)
03-08 20:10 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://XOAUTH2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=0, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true, typesToBackup=[SMS, MMS, CALLLOG, WHATSAPP]}
03-08 20:10 need to perform xoauth2 token refresh
03-08 20:10 error refreshing token: com.zegoggles.smssync.auth.TokenRefreshException: android.accounts.AuthenticatorException: User intervention required. Notification has been pushed., cause=android.accounts.AuthenticatorException: User intervention required. Notification has been pushed.
03-08 20:10 Authentication error: Command: sensitive; response: #2# [NO, [ALERT], Invalid credentials (Failure)](exception: com.fsck.k9.mail.store.XOAuth2AuthenticationFailedException: Command: sensitive; response: #2# [NO, [ALERT], Invalid credentials %28Failure%29])
03-08 20:10 BackupState{currentSyncedItems=0, itemsToSync=0, backupType=MANUAL, exception=com.fsck.k9.mail.store.XOAuth2AuthenticationFailedException: Command: sensitive; response: #2# [NO, [ALERT], Invalid credentials (Failure)], state =ERROR}
03-08 20:10 Backup finished
@eriji commented on GitHub (Mar 9, 2015):
I did try a disconnect and reconnect. The reconnect failed with a similar error.
@jberkel commented on GitHub (Mar 9, 2015):
thanks for the detailed report. the log says
User intervention required. Notification has been pushed.Looks like some manual user intervention is required to refresh the token.@jberkel commented on GitHub (Mar 9, 2015):
did you get a system notification when the error happened? it should be a password prompt or similar.
@eriji commented on GitHub (Mar 9, 2015):
No, I was waiting for something, and looked for it, but there was no
indication anywhere that login was waiting.
Other programs using authorization might forward you to the browser to
"finish" logging in, some use the one-time tokens (which require password
entry), and most of them now just have a screen come up that says what
information is being shared, permissions, etc, and to accept.
--eric powell
eric powell
po box 129, orangeburg, sc 29116-0129
803-997-0707 - fax 877-885-8830
epowell@pobox.com
On Mon, Mar 9, 2015 at 8:33 AM, Jan Berkel notifications@github.com wrote:
@jberkel commented on GitHub (Mar 9, 2015):
Ok, that's weird. Android should handle this case (as it says in the log: Notification has been pushed.) I'll see if I can reproduce it.
@eriji commented on GitHub (Mar 10, 2015):
Jan,
Something was bugging me about having seen something about Google and
XOAuth changing recently, and when I got some time I searched for it and
found some tweets by searching for "Google Authentication API". They
indicated that there was a problem with an error similar to what I was
experiencing that caused odd authentication problems over a variety of apps.
After reading that, I tried the SMS Backup+ authentication again, and it
worked fine now. It appears it was a Google problem and temporary.
I'm sorry that you were chasing a problem that turned out to be Google's
problem. Thanks for responding to my inquiry so quickly.
Everything seems to work fine now.
Cheers,
--eric powell
On Mon, Mar 9, 2015 at 10:18 AM Jan Berkel notifications@github.com wrote:
@eriji commented on GitHub (Mar 10, 2015):
Something was bugging me about having seen something about Google and XOAuth changing recently, and when I got some time I searched for it and found some tweets by searching for "Google Authentication API". They indicated that there was a problem with an error similar to what I was experiencing that caused odd authentication problems over a variety of apps.
After reading that, I tried the SMS Backup+ authentication again, and it worked fine now. It appears it was a Google problem and temporary.
@jberkel commented on GitHub (Mar 10, 2015):
cool, thanks for the research!
@danyeungw commented on GitHub (May 28, 2015):
After you searched for "Google Authentication API", what did you do to make it work? I got the same issue. Thanks.