mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #184] XOAuth logon error #157
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#157
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 @hhallman on GitHub (Oct 4, 2011).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/184
I'm using google apps and the application has been working until recently.
(Last successful backup was on 25th of september.)
Error output is "Authentication error: null" in the log. No settings have been changed in neither gmail nor the application. IMAP is enabled.
@hhallman commented on GitHub (Oct 10, 2011):
Could work around the problem by switching from xoauth to plain text authentication
@jamgregory commented on GitHub (Jan 22, 2012):
I've just started seeing this issue. If I "Force Close" the app, the next sync will seem to go through without a problem. However, after a few more syncs, this issue will appear again.
@nx01 commented on GitHub (Mar 10, 2012):
I have just started getting this message too. I have been using the app since the beginning of February. Tried 'Force Close' and that did not resolve the problem. Changing to plain text authorization did not work either..
@FindingOlivier commented on GitHub (Mar 18, 2012):
Same here.
@jberkel commented on GitHub (Mar 18, 2012):
cannot reproduce - have you tried disconnecting and reconnecting your account?
@nx01 commented on GitHub (Mar 18, 2012):
I have use the instruction on how to revoke SMS Backup+ access. I
uninstalled the app and then re-installed with the same result. I had
uninstalled a
week ago. It had worked for about a month and 1/2 before the error. I
just installed again an now it seems to be working again.
On 3/18/2012 9:19 AM, Jan Berkel wrote:
@FindingOlivier commented on GitHub (Mar 18, 2012):
Test 1 :
also tested :
@brucekelley commented on GitHub (Apr 17, 2012):
I'm having this issue with my new Galaxy Nexus with ICS, as well. The XOAuth in SMS Backup+ was working fine on my old Droid, so it isn't an issue with the Google account. IMAP is turned on and working. Any tests you'd like me to try to narrow this down?
@zrajm commented on GitHub (Jun 5, 2013):
This problem showed up for me when making a restore of some 9000+ text messages (though in all honesty the phone was also new). My first thought is that this might be some google spam (or overload) prevention-thingy. (Since I assume that SMS Backup+ does one IMAP access for each text message, and doing 9000+ transfers an one time might seem excessive to Google…)
Are other people seeing this problem with lower volumes of text messages?
EDIT: Found Fix Gmail IMAP Invalid Credentials or Web Login Requires (Failure) Error which seems to support my above theory.
EDIT2: Another (newer article, with more tips on the same thing): Cannot Get Mail Gmail IMAP Not Responding Error on iPhone, iPad or Mac.
The problem seem to have gone away, for me, by switching to plain text authentication. (by setting username [=gmail address] & password in the SMS Backup+ menu "Advanced settings -> IMAP server settings"
@Ulopes commented on GitHub (Feb 19, 2016):
Uninstall and reinstall SMS Backup+ solved the problem.
@sf395 commented on GitHub (Oct 17, 2016):
Seems strange but uninstalling and reinstallinmg SMS Backup+ solved the problem too.