Skip to content

Docs

Troubleshooting

The first things to check, and what to do when macOS refuses to open the app.

Common issues

  • The overlay never appears — confirm a provider is connected in Settings; without one, Veyra has nothing to answer with.
  • Answers are slow or absent — check your provider connection and that the meeting audio is actually reaching Veyra.
  • Nothing gets answered at all — check Sensitivity; Quiet only responds to clear, direct questions.
  • A briefing seems empty — confirm it was built before the meeting started; Veyra reads sources once, at build time.

Veyra is built to a two-second budget: end of speech to first readable word. If answers consistently arrive well outside that, something upstream — your network, or your provider — is the likely cause, not Veyra itself.

Opening an unsigned build

macOS Gatekeeper blocks software from outside the App Store or an identified developer by default. An unsigned or unnotarised build of Veyra triggers this the first time you open it.

  1. 1Try to open Veyra normally once — macOS will refuse and show a warning.
  2. 2Open System Settings → Privacy & Security.
  3. 3Find the message about Veyra being blocked, and choose Open Anyway.
  4. 4Confirm in the dialog that appears. This is only required once per install.

Intel Macs are not supported. Gatekeeper's warning is unrelated to platform support — it appears on supported machines too, whenever a build is not notarised.