KasWare signing problems
The wallet popup doesn't appear, the signature fails, or the request seems to hang during signing.
KasWare popup doesn't appear at all
- Confirm the KasWare extension is installed and unlocked.
- Confirm you're actually connected (see Connect KasWare) — a disconnected wallet won't produce a popup.
- If the dashboard shows DO NOT SIGN instead of a normal signing action, this is expected behavior, not a bug in the popup: PolicyVault's own pre-sign verification found a mismatch and deliberately does not offer a signature action at all. See Local intent verification.
The signature is rejected as invalid
PolicyVault verifies every consensus-visible field of a signed transaction is byte-identical to what was actually built, before accepting a signature — only the input signature scripts themselves are expected to differ. A rejection here usually means either the wallet altered something it shouldn't have (rare, and would itself be a reportable issue — see Responsible disclosure), or a stale/expired request was signed after the vault's live state moved on. See Transaction pending for the latter.
An approval signature (not a spend signature) fails
Approver signatures use a specific signing mode — signing a named input of the frozen transaction with the correct signature-hash type. A wallet producing an ordinary "sign this message" signature instead of this exact form is not usable as covenant approval and will be refused; see What KasWare signs for exactly what's required.
Account or network changed mid-signature
If you switch accounts or networks in KasWare while a request is in-flight, PolicyVault discards that in-progress request rather than risk reinterpreting a signature under a changed identity. Rebuild the request after switching back to the correct account/network. See Wrong wallet connected and Wrong network.
KasWare reports an unsupported operation
PolicyVault checks a connected signer's declared capabilities before offering an action that signer can't actually perform, and fails closed (SIGNING_UNSUPPORTED) rather than sending a request a provider can't handle. If this happens for an operation you'd expect KasWare to support, confirm you're running a current version of the extension.
See also: What wallets and signers do, Error codes.