Yttrium Kotlin 0.10.58

Release version 0.10.58

Branch: main

⚠️ Breaking change — ComplianceFailed error removed

The pay module no longer special-cases sanctioned wallets. The ComplianceFailed
error has been removed from all pay exception types. Sanctioned-wallet /
compliance responses now surface through the generic error path instead.

Removed cases (Kotlin):

• GetPaymentOptionsException.ComplianceFailed
• ConfirmPaymentException.ComplianceFailed
• PayJsonException.ComplianceFailed

A sanctioned wallet that previously threw ComplianceFailed now throws a generic
error (e.g. Http). No compliance-specific handling remains in the SDK.

Migration

Remove any catch or when branch that references ComplianceFailed and rely on
your generic error handling instead:

// Before
try {
    pay.confirmPayment(/* ... */)
} catch (e: GetPaymentOptionsException.ComplianceFailed) {
    showComplianceBlocked(e.message)
} catch (e: GetPaymentOptionsException) {
    showGenericError(e.message)
}

// After — drop the ComplianceFailed catch; it now flows into the generic handler
try {
    pay.confirmPayment(/* ... */)
} catch (e: GetPaymentOptionsException) {
    showGenericError(e.message)
}

You only need changes if your code explicitly references ComplianceFailed
(a catch on that type, or an is ...ComplianceFailed -> branch in a when).
Code that catches only the base exception needs no changes.

The equivalent removal shipped for Swift in Yttrium 0.10.57 and for JS/WASM in
Yttrium WASM Pay 0.10.57.

Maven Artifacts

After this release, the following artifacts are available via JitPack:

repositories {
    maven { url 'https://jitpack.io' }
}

dependencies {
    // Base library
    implementation 'com.github.reown-com:yttrium:0.10.58'

    // Utils (multi-chain support)
    implementation 'com.github.reown-com.yttrium:yttrium-utils:0.10.58'

    // WCPay (payment flows)
    implementation 'com.github.reown-com.yttrium:yttrium-wcpay:0.10.58'
}