Skip to Content
SDKTroubleshooting Basics

Troubleshooting Basics

Check the basics

  • Is the Beav3r API key valid?
  • Is the project configured for the intended test flow?
  • Is one signer paired and active?
  • Can the device receive push notifications?
  • Is the caller pointing at the correct Beav3r server?

If offchain works but onchain authorization fails

This usually means flow prerequisites are mixed:

  • Offchain guard / guardAndWait can succeed with policy allow or approval routing.
  • Onchain authorizeOnchainAction additionally requires onchain signer registration for the actor (account, keyId) in the signer registry.

Checks:

  • verify signer registry has the expected signer for that actor account and key id
  • verify project and API key are the same ones used during onchain actor provisioning
  • verify actor account and executor match the provisioned record

If the signer does not receive a notification

Check:

  • the signer is paired
  • the signer is the active device
  • the request reached the correct Beav3r project

If the request does not resolve back to the caller

Check:

  • the caller is using the right API key
  • the action was accepted by Beav3r
  • the integration or app callback path is configured correctly

If status is denied

denied is a policy/evaluation result, not a signer rejection.

Check:

  • API key scopes
  • project policy conditions (amount, chain, recipient, action type)
  • whether the project is configured for auto-allow, signer approval, or deny for that request shape

If the issue source is unclear

Go back through:

SDK API ReferenceOverview