Troubleshooting Basics
Start with the shortest failure path first.
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 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 you are unsure where the issue is
Go back through:
Scope note
This page stays intentionally short until the SDK path has real recurring failure cases to document.