diff options
| author | James Lemieux <jplemieux@google.com> | 2014-01-30 12:00:03 -0800 |
|---|---|---|
| committer | James Lemieux <jplemieux@google.com> | 2014-03-07 16:38:48 -0800 |
| commit | 55d0725ebe4d12c7d1d02f5ee13840c1f200503d (patch) | |
| tree | 05270e4b7be130c0cfcb1a37e1ad23c843c6a525 /res/values-sw/strings.xml | |
| parent | 42c39c4026970508a536099085d5155196bbee42 (diff) | |
| download | android_packages_apps_UnifiedEmail-55d0725ebe4d12c7d1d02f5ee13840c1f200503d.tar.gz android_packages_apps_UnifiedEmail-55d0725ebe4d12c7d1d02f5ee13840c1f200503d.tar.bz2 android_packages_apps_UnifiedEmail-55d0725ebe4d12c7d1d02f5ee13840c1f200503d.zip | |
Keep on getting a couldn't sign-in notification
b/11551107
This is caused by ImapConnection.doLogin() only throwing
AuthenticationFailedExceptions and not other varieties of exceptions.
Our best guess based on the reported bug is that the IMAP server should
be returning "UNAVAILABLE" indicating the IMAP server is up and
responding but some resource it relies on (e.g. LDAP) is currently down.
We translate the "UNAVAILABLE" response code into a Server Error value
and display a message to the user and a Retry button.
While fixing this bug, I discovered that the ConversationListFooterView
that is displayed in response to a authentication failure contains a
button called "Sign In" that didn't actually do anything. I made it
navigate to the incoming account settings fragment where the user is
free to change the relevant account credentials.
Change-Id: I2c772ecab18f3e57059eceeae01de08f1fdab4c2
Diffstat (limited to 'res/values-sw/strings.xml')
0 files changed, 0 insertions, 0 deletions