Home/ Questions/Q 6733259
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T10:44:51+00:00

In an Android app I’m working on, I’m using the AccountManager to store the

  • 0

In an Android app I’m working on, I’m using the AccountManager to store the user’s account info and also sync a couple of sources (I have two services that respond to the android.content.SyncAdapter intent action).

However, I am not syncing contacts. In spite of this, if I go in the contacts app and choose to add a contact, I get a popup asking me under which account should the contact be created. The account created by my app is listed there as well. I have tried putting android:supportsUploading="false" on my <sync-adapter>s, doesn’t work.

The only solution I currently see is to create an empty, invisible contact sync service that has android:supportsUploading="false", but that seems like the biggest and most useless hack ever.

Help?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It appears to me that you have to specify both android:supportsUploading="false" AND your content authority must be android:contentAuthority="com.android.contacts" (ContactsContract.AUTHORITY).

    See com.android.contacts.model.Sources.queryAccounts(), which fills in the .readOnly flag, and com.android.contacts.model.Sources.getAccounts(), which is used by com.android.contacts.util.AccountSelectionUtil.getSelectAccountDialog() to populate the contacts dialog.

    What’s not clear to me is whether this has additional (potentially undesirable) side effects — particularly given that you’re specifying a contentAuthority that is conceptually the opposite of what you want.

    -Tim

    • 0