ChallengeRequestException

Exception thrown when requesting a challenge transaction from the server fails.

This can occur for several reasons:

• Network connectivity issues

• Server returns HTTP error (400, 401, 403, 500, etc.)

• Invalid response format from server

• Missing required response fields

• Configuration errors (missing WEB_AUTH_ENDPOINT, invalid stellar.toml)

HTTP status codes and their meanings:

• 400 Bad Request: Invalid account ID or parameters

• 401 Unauthorized: Server authentication required

• 403 Forbidden: Account not allowed to authenticate

• 404 Not Found: WebAuth endpoint not available

• 500+ Server Error: Server-side issues

Example - Handle challenge request errors:

try {
    val challenge = webAuth.getChallenge(accountId)
} catch (e: ChallengeRequestException) {
    when (e.statusCode) {
        400 -> println("Invalid account ID: ${e.errorMessage}")
        403 -> println("Account not allowed: ${e.errorMessage}")
        else -> println("Server error: ${e.message}")
    }
}

Example - Network errors (statusCode = 0):

try {
    val challenge = webAuth.getChallenge(accountId)
} catch (e: ChallengeRequestException) {
    if (e.statusCode == 0) {
        println("Network error: ${e.errorMessage}")
        // Retry logic
    }
}

Parameters