You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
kotlin-sdk: Signing failures surface as Generic errors — no typed pre-broadcast signal #4052
Dashpay.sendContactRequest failed with Generic: SDK error: Protocol error: Generic Error: no private key stored for <pubkeyHex>.
Signing happens strictly pre-submission, so integrators need a typed error (e.g. SigningFailed) to safely classify "definitively not broadcast" for fallback/retry logic.
Currently message-matching "no private key stored". Live-verified.
Context: found during the Android wallet dashj→Kotlin-SDK migration (dashpay/dash-wallet#1507); live-verified items were reproduced on testnet (Galaxy S22).
Fixed by #4183 and #4321. A missing signing key is now the typed native error ErrorSigningKeyUnavailable (31), mapped to DashSdkError.PlatformWallet.SigningKeyUnavailable, so callers get a pre-broadcast signal instead of Generic. Closing.
Activity
feat(kotlin-sdk): typed SigningKeyUnavailable error for missing signi…
HashEngineering commentedon Nov 9, 2026
Fixed by #4183 and #4321. A missing signing key is now the typed native error
ErrorSigningKeyUnavailable(31), mapped toDashSdkError.PlatformWallet.SigningKeyUnavailable, so callers get a pre-broadcast signal instead of Generic. Closing.