Mixing
AbstractAccountAuthenticator allow only 1 account
I have implemented AbstractAccountAuthenticator as a requirement to use SyncAdapter hower my application is supporting only 1 account at a time.
When the user is trying to add another account via settings - Settings crash with an error that it stopped working.
I have seen some application e.g. LinkedIn, Facebook they somehow handle it differently a toast message is shown to the user with a statement that only 1 account is supported. How can I achieve this functionality?
This is my authenticator
class ApplicationAuthenticator(private val context: Context) : AbstractAccountAuthenticator(context) {
// Editing properties is not supported
@Throws(UnsupportedOperationException::class)
override fun editProperties(response: AccountAuthenticatorResponse,
accountType: String): Bundle? {
throw UnsupportedOperationException()
}
// Don't add additional accounts
override fun addAccount(response: AccountAuthenticatorResponse, accountType: String,
authTokenType: String, features: Array<String>,
options: Bundle): Bundle? {
return bundleOf(AccountManager.KEY_INTENT to null)
}
// Ignore attempts to confirm credentials
@Throws(NetworkErrorException::class)
override fun confirmCredentials(response: AccountAuthenticatorResponse, account: Account,
options: Bundle): Bundle? {
return null
}
// Getting an authentication token is not supported
@Throws(NetworkErrorException::class, UnsupportedOperationException::class)
override fun getAuthToken(response: AccountAuthenticatorResponse, account: Account,
authTokenType: String, loginOptions: Bundle): Bundle? {
throw UnsupportedOperationException()
}
// Getting a label for the auth token is not supported
override fun getAuthTokenLabel(authTokenType: String): String {
return context.resources.getString(R.string.application_name)
}
// Updating user credentials is not supported
override fun updateCredentials(response: AccountAuthenticatorResponse, account: Account,
authTokenType: String, loginOptions: Bundle): Bundle? {
return null
}
// Checking features for the account is not supported
@Throws(NetworkErrorException::class)
override fun hasFeatures(response: AccountAuthenticatorResponse, account: Account,
features: Array<String>): Bundle {
return bundleOf(KEY_BOOLEAN_RESULT to false)
}
}
android android-syncadapter android-authenticator
asked Nov 19 '18 at 12:40
antanas_sepikas
1,73921740
add a comment |
I have implemented AbstractAccountAuthenticator as a requirement to use SyncAdapter hower my application is supporting only 1 account at a time.
When the user is trying to add another account via settings - Settings crash with an error that it stopped working.
I have seen some application e.g. LinkedIn, Facebook they somehow handle it differently a toast message is shown to the user with a statement that only 1 account is supported. How can I achieve this functionality?
This is my authenticator
class ApplicationAuthenticator(private val context: Context) : AbstractAccountAuthenticator(context) {
// Editing properties is not supported
@Throws(UnsupportedOperationException::class)
override fun editProperties(response: AccountAuthenticatorResponse,
accountType: String): Bundle? {
throw UnsupportedOperationException()
}
// Don't add additional accounts
override fun addAccount(response: AccountAuthenticatorResponse, accountType: String,
authTokenType: String, features: Array<String>,
options: Bundle): Bundle? {
return bundleOf(AccountManager.KEY_INTENT to null)
}
// Ignore attempts to confirm credentials
@Throws(NetworkErrorException::class)
override fun confirmCredentials(response: AccountAuthenticatorResponse, account: Account,
options: Bundle): Bundle? {
return null
}
// Getting an authentication token is not supported
@Throws(NetworkErrorException::class, UnsupportedOperationException::class)
override fun getAuthToken(response: AccountAuthenticatorResponse, account: Account,
authTokenType: String, loginOptions: Bundle): Bundle? {
throw UnsupportedOperationException()
}
// Getting a label for the auth token is not supported
override fun getAuthTokenLabel(authTokenType: String): String {
return context.resources.getString(R.string.application_name)
}
// Updating user credentials is not supported
override fun updateCredentials(response: AccountAuthenticatorResponse, account: Account,
authTokenType: String, loginOptions: Bundle): Bundle? {
return null
}
// Checking features for the account is not supported
@Throws(NetworkErrorException::class)
override fun hasFeatures(response: AccountAuthenticatorResponse, account: Account,
features: Array<String>): Bundle {
return bundleOf(KEY_BOOLEAN_RESULT to false)
}
}
android android-syncadapter android-authenticator
asked Nov 19 '18 at 12:40
antanas_sepikas
1,73921740
add a comment |
I have implemented AbstractAccountAuthenticator as a requirement to use SyncAdapter hower my application is supporting only 1 account at a time.
When the user is trying to add another account via settings - Settings crash with an error that it stopped working.
I have seen some application e.g. LinkedIn, Facebook they somehow handle it differently a toast message is shown to the user with a statement that only 1 account is supported. How can I achieve this functionality?
This is my authenticator
class ApplicationAuthenticator(private val context: Context) : AbstractAccountAuthenticator(context) {
// Editing properties is not supported
@Throws(UnsupportedOperationException::class)
override fun editProperties(response: AccountAuthenticatorResponse,
accountType: String): Bundle? {
throw UnsupportedOperationException()
}
// Don't add additional accounts
override fun addAccount(response: AccountAuthenticatorResponse, accountType: String,
authTokenType: String, features: Array<String>,
options: Bundle): Bundle? {
return bundleOf(AccountManager.KEY_INTENT to null)
}
// Ignore attempts to confirm credentials
@Throws(NetworkErrorException::class)
override fun confirmCredentials(response: AccountAuthenticatorResponse, account: Account,
options: Bundle): Bundle? {
return null
}
// Getting an authentication token is not supported
@Throws(NetworkErrorException::class, UnsupportedOperationException::class)
override fun getAuthToken(response: AccountAuthenticatorResponse, account: Account,
authTokenType: String, loginOptions: Bundle): Bundle? {
throw UnsupportedOperationException()
}
// Getting a label for the auth token is not supported
override fun getAuthTokenLabel(authTokenType: String): String {
return context.resources.getString(R.string.application_name)
}
// Updating user credentials is not supported
override fun updateCredentials(response: AccountAuthenticatorResponse, account: Account,
authTokenType: String, loginOptions: Bundle): Bundle? {
return null
}
// Checking features for the account is not supported
@Throws(NetworkErrorException::class)
override fun hasFeatures(response: AccountAuthenticatorResponse, account: Account,
features: Array<String>): Bundle {
return bundleOf(KEY_BOOLEAN_RESULT to false)
}
}
android android-syncadapter android-authenticator
asked Nov 19 '18 at 12:40
antanas_sepikas
1,73921740
I have implemented AbstractAccountAuthenticator as a requirement to use SyncAdapter hower my application is supporting only 1 account at a time.
When the user is trying to add another account via settings - Settings crash with an error that it stopped working.
I have seen some application e.g. LinkedIn, Facebook they somehow handle it differently a toast message is shown to the user with a statement that only 1 account is supported. How can I achieve this functionality?
This is my authenticator
class ApplicationAuthenticator(private val context: Context) : AbstractAccountAuthenticator(context) {
// Editing properties is not supported
@Throws(UnsupportedOperationException::class)
override fun editProperties(response: AccountAuthenticatorResponse,
accountType: String): Bundle? {
throw UnsupportedOperationException()
}
// Don't add additional accounts
override fun addAccount(response: AccountAuthenticatorResponse, accountType: String,
authTokenType: String, features: Array<String>,
options: Bundle): Bundle? {
return bundleOf(AccountManager.KEY_INTENT to null)
}
// Ignore attempts to confirm credentials
@Throws(NetworkErrorException::class)
override fun confirmCredentials(response: AccountAuthenticatorResponse, account: Account,
options: Bundle): Bundle? {
return null
}
// Getting an authentication token is not supported
@Throws(NetworkErrorException::class, UnsupportedOperationException::class)
override fun getAuthToken(response: AccountAuthenticatorResponse, account: Account,
authTokenType: String, loginOptions: Bundle): Bundle? {
throw UnsupportedOperationException()
}
// Getting a label for the auth token is not supported
override fun getAuthTokenLabel(authTokenType: String): String {
return context.resources.getString(R.string.application_name)
}
// Updating user credentials is not supported
override fun updateCredentials(response: AccountAuthenticatorResponse, account: Account,
authTokenType: String, loginOptions: Bundle): Bundle? {
return null
}
// Checking features for the account is not supported
@Throws(NetworkErrorException::class)
override fun hasFeatures(response: AccountAuthenticatorResponse, account: Account,
features: Array<String>): Bundle {
return bundleOf(KEY_BOOLEAN_RESULT to false)
}
}
android android-syncadapter android-authenticator
android android-syncadapter android-authenticator
asked Nov 19 '18 at 12:40
antanas_sepikas
1,73921740
asked Nov 19 '18 at 12:40
antanas_sepikas
1,73921740
asked Nov 19 '18 at 12:40
antanas_sepikas
1,73921740
asked Nov 19 '18 at 12:40
antanas_sepikas
1,73921740
asked Nov 19 '18 at 12:40
antanas_sepikas
1,73921740
1,73921740
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
When the user clicks the "Add Account" button, Android just calls the addAccount method of your ApplicationAuthenticator. In return it expects either the account to be created, an Intent which launches the account setup or an error.
If you don't allow multiple accounts you have multiple options here:
- Return an error with code ERROR_CODE_UNSUPPORTED_OPERATION. Although I've not tried that yet.
Return your existing account as the result. At this point you can also show a
Toast.
To Return the existing account just let
addAccountreturn aBundlewith the following keys and their respective values:
AccountManager.KEY_ACCOUNT_NAME and AccountManager.KEY_ACCOUNT_TYPE of the account that was added, or
Return an Activity
Intentwhich doesn't create an account but explains to the user that this is an unsupported/unnecessary operation. It's not a requirement that the Activity actually adds an account.
This gives the best user experience IMO.
answered Nov 29 '18 at 5:41
Marten
3,0041822
But how do I return the existing account as a result, do I need to implement AccountAuthenticatorActivity or can I just simple return that results directly from Authenticator?
– antanas_sepikas
Nov 29 '18 at 6:23
I've updated the answer. Also make sure to removeKEY_INTENTfrom your bundle if you return the account instead.
– Marten
Nov 29 '18 at 9:27
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374867%2fabstractaccountauthenticator-allow-only-1-account%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When the user clicks the "Add Account" button, Android just calls the addAccount method of your ApplicationAuthenticator. In return it expects either the account to be created, an Intent which launches the account setup or an error.
If you don't allow multiple accounts you have multiple options here:
- Return an error with code ERROR_CODE_UNSUPPORTED_OPERATION. Although I've not tried that yet.
Return your existing account as the result. At this point you can also show a
Toast.
To Return the existing account just let
addAccountreturn aBundlewith the following keys and their respective values:
AccountManager.KEY_ACCOUNT_NAME and AccountManager.KEY_ACCOUNT_TYPE of the account that was added, or
Return an Activity
Intentwhich doesn't create an account but explains to the user that this is an unsupported/unnecessary operation. It's not a requirement that the Activity actually adds an account.
This gives the best user experience IMO.
answered Nov 29 '18 at 5:41
Marten
3,0041822
But how do I return the existing account as a result, do I need to implement AccountAuthenticatorActivity or can I just simple return that results directly from Authenticator?
– antanas_sepikas
Nov 29 '18 at 6:23
I've updated the answer. Also make sure to removeKEY_INTENTfrom your bundle if you return the account instead.
– Marten
Nov 29 '18 at 9:27
add a comment |
When the user clicks the "Add Account" button, Android just calls the addAccount method of your ApplicationAuthenticator. In return it expects either the account to be created, an Intent which launches the account setup or an error.
If you don't allow multiple accounts you have multiple options here:
- Return an error with code ERROR_CODE_UNSUPPORTED_OPERATION. Although I've not tried that yet.
Return your existing account as the result. At this point you can also show a
Toast.
To Return the existing account just let
addAccountreturn aBundlewith the following keys and their respective values:
AccountManager.KEY_ACCOUNT_NAME and AccountManager.KEY_ACCOUNT_TYPE of the account that was added, or
Return an Activity
Intentwhich doesn't create an account but explains to the user that this is an unsupported/unnecessary operation. It's not a requirement that the Activity actually adds an account.
This gives the best user experience IMO.
answered Nov 29 '18 at 5:41
Marten
3,0041822
But how do I return the existing account as a result, do I need to implement AccountAuthenticatorActivity or can I just simple return that results directly from Authenticator?
– antanas_sepikas
Nov 29 '18 at 6:23
I've updated the answer. Also make sure to removeKEY_INTENTfrom your bundle if you return the account instead.
– Marten
Nov 29 '18 at 9:27
add a comment |
When the user clicks the "Add Account" button, Android just calls the addAccount method of your ApplicationAuthenticator. In return it expects either the account to be created, an Intent which launches the account setup or an error.
If you don't allow multiple accounts you have multiple options here:
- Return an error with code ERROR_CODE_UNSUPPORTED_OPERATION. Although I've not tried that yet.
Return your existing account as the result. At this point you can also show a
Toast.
To Return the existing account just let
addAccountreturn aBundlewith the following keys and their respective values:
AccountManager.KEY_ACCOUNT_NAME and AccountManager.KEY_ACCOUNT_TYPE of the account that was added, or
Return an Activity
Intentwhich doesn't create an account but explains to the user that this is an unsupported/unnecessary operation. It's not a requirement that the Activity actually adds an account.
This gives the best user experience IMO.
answered Nov 29 '18 at 5:41
Marten
3,0041822
When the user clicks the "Add Account" button, Android just calls the addAccount method of your ApplicationAuthenticator. In return it expects either the account to be created, an Intent which launches the account setup or an error.
If you don't allow multiple accounts you have multiple options here:
- Return an error with code ERROR_CODE_UNSUPPORTED_OPERATION. Although I've not tried that yet.
Return your existing account as the result. At this point you can also show a
Toast.
To Return the existing account just let
addAccountreturn aBundlewith the following keys and their respective values:
AccountManager.KEY_ACCOUNT_NAME and AccountManager.KEY_ACCOUNT_TYPE of the account that was added, or
Return an Activity
Intentwhich doesn't create an account but explains to the user that this is an unsupported/unnecessary operation. It's not a requirement that the Activity actually adds an account.
This gives the best user experience IMO.
answered Nov 29 '18 at 5:41
Marten
3,0041822
edited Nov 29 '18 at 9:26
answered Nov 29 '18 at 5:41
Marten
3,0041822
answered Nov 29 '18 at 5:41
Marten
3,0041822
answered Nov 29 '18 at 5:41
Marten
3,0041822
3,0041822
But how do I return the existing account as a result, do I need to implement AccountAuthenticatorActivity or can I just simple return that results directly from Authenticator?
– antanas_sepikas
Nov 29 '18 at 6:23
I've updated the answer. Also make sure to removeKEY_INTENTfrom your bundle if you return the account instead.
– Marten
Nov 29 '18 at 9:27
add a comment |
But how do I return the existing account as a result, do I need to implement AccountAuthenticatorActivity or can I just simple return that results directly from Authenticator?
– antanas_sepikas
Nov 29 '18 at 6:23
I've updated the answer. Also make sure to removeKEY_INTENTfrom your bundle if you return the account instead.
– Marten
Nov 29 '18 at 9:27
But how do I return the existing account as a result, do I need to implement AccountAuthenticatorActivity or can I just simple return that results directly from Authenticator?
– antanas_sepikas
Nov 29 '18 at 6:23
But how do I return the existing account as a result, do I need to implement AccountAuthenticatorActivity or can I just simple return that results directly from Authenticator?
– antanas_sepikas
Nov 29 '18 at 6:23
I've updated the answer. Also make sure to remove
KEY_INTENT from your bundle if you return the account instead.– Marten
Nov 29 '18 at 9:27
I've updated the answer. Also make sure to remove
KEY_INTENT from your bundle if you return the account instead.– Marten
Nov 29 '18 at 9:27
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374867%2fabstractaccountauthenticator-allow-only-1-account%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
