Sep30ConflictException

Exception thrown when the recovery server returns HTTP 409 Conflict.

Indicates that the request conflicts with the current state of the recovery server. This typically occurs when:

• An account is already registered and a new registration is attempted

• A signer is already registered for the account

Recovery actions:

• Use the update endpoint instead of register if the account already exists

• Retrieve the current account details to understand the existing state

Example - Handle conflict:

try {
    val account = sep30Service.registerAccount(address, identities, signers)
} catch (e: Sep30ConflictException) {
    println("Account already registered: ${e.message}")
    // Update the existing registration instead
}

See also:

• Sep30Exception base class

• SEP-0030 Specification

Parameters