Skip to content

Latest commit

 

History

History
184 lines (129 loc) · 5.32 KB

insert-groups.md

File metadata and controls

184 lines (129 loc) · 5.32 KB

Insert groups

This library provides the GroupsInsert API that allows you to create/insert groups associated to an Account or no account.

An instance of the GroupsInsert API is obtained by,

val insert = Contacts(context).groups().insert()

A basic insert

To create/insert a new group for an Account,

val insertResult = Contacts(context)
    .groups()
    .insert()
    .group(
        title = "Besties",
        account = Account("[email protected]", "com.google")
    )
    .commit()

If you need to insert multiple groups,

val newGroup1 = NewGroup("Goodies", Account("[email protected]", "com.google"))
val newGroup2 = NewGroup("Baddies", Account("[email protected]", "com.google"))

val insertResult = Contacts(context)
    .groups()
    .insert()
    .groups(newGroup1, newGroup2)
    .commit()

Groups and Accounts

A set of groups exist for each Account. The "null" account (representing the local/device-only account) may also have a set of groups.

ℹ️ Prior to version 0.3.0, this API did not allow insertion of groups with null accounts.

The get accounts permission is required here because this API retrieves all available accounts, if any, and does the following;

  • if the account specified is found in the list of accounts returned by the system, then the account is used
  • if the account specified is not found in the list of accounts returned by the system, then the insertion fails for that group
  • if a null is specified, then the group will be inserted without association to an account

ℹ️ For more info on the relationship of Groups and Accounts, read Query groups.

Groups and duplicate titles

The Contacts Provider allows multiple groups with the same title (case-sensitive comparison) belonging to the same nullable account to exist. In older versions of Android, the AOSP Contacts app allows the creation of new groups with existing titles. In newer versions, duplicate titles are not allowed. Therefore, this library does not allow for duplicate titles.

Executing the insert

To execute the insert,

.commit()

Handling the insert result

The commit function returns a Result.

To check if all inserts succeeded,

val allInsertsSuccessful = insertResult.isSuccessful

To check if a particular insert succeeded,

val firstInsertSuccessful = insertResult.isSuccessful(newGroup1)

To get the Group IDs of all the newly created Groups,

val allGroupIds = insertResult.groupIds

To get the Group ID of a particular Group,

val secondGroupId = insertResult.groupId(newGroup2)

Once you have the Group IDs, you can retrieve the newly created Groups via the GroupsQuery API,

val groups = contactsApi
    .groups()
    .query()
    .where { Id `in` allGroupIds }
    .find()

ℹ️ For more info, read Query groups.

Alternatively, you may use the extensions provided in GroupsInsertResult. To get all newly created Groups,

val groups = insertResult.groups(contactsApi)

To get a particular group,

val group = insertResult.group(contactsApi, newGroup1)

Handling insert failure

The insert may fail for a particular group for various reasons,

insertResult.failureReason(newGroup1)?.let {
    when (it) {
        TITLE_ALREADY_EXIST -> promptUserToPickDifferentTitle()
        INVALID_ACCOUNT -> promptUserToPickDifferentAccount()
        UNKNOWN -> showGenericErrorMessage()
    }   
}

Cancelling the insert

To cancel an insert amid execution,

.commit { returnTrueIfInsertShouldBeCancelled() }

The commit function optionally takes in a function that, if it returns true, will cancel insert processing as soon as possible. The function is called numerous times during insert processing to check if processing should stop or continue. This gives you the option to cancel the insert.

For example, to automatically cancel the insert inside a Kotlin coroutine when the coroutine is cancelled,

launch {
    withContext(coroutineContext) {
        val insertResult = insert.commit { !isActive }
    }
}

Performing the insert and result processing asynchronously

Inserts are executed when the commit function is invoked. The work is done in the same thread as the call-site. This may result in a choppy UI.

To perform the work in a different thread, use the Kotlin coroutine extensions provided in the async module. For more info, read Execute work outside of the UI thread using coroutines.

You may, of course, use other multi-threading libraries or just do it yourself =)

ℹ️ Extensions for Kotlin Flow and RxJava are also in the project roadmap.

Performing the insert with permission

Inserts require the android.permission.WRITE_CONTACTS and android.permission.GET_ACCOUNTS permissions. If not granted, the insert will do nothing and return a failed result.

To perform the insert with permission, use the extensions provided in the permissions module. For more info, read Permissions handling using coroutines.

You may, of course, use other permission handling libraries or just do it yourself =)