Troubleshooting
Common problems and where to look next.
App will not open or crashes on launch
- Quit Avera completely and reopen.
- On macOS, check that you installed from a trusted DMG build.
- If you use beta builds, ensure the database migrated:
avera status --check-migrations.
Writer or Teams missing
You need Google sign-in and an active Avera Pro subscription. Confirm Account → Billing. Writer stays hidden or gated without Pro.
Import or Quick Add blocked
Free-tier paper or note limits show a dialog. Upgrade or remove unused items from Trash.
Library search missing papers
Large imports may need time to index. Power users: avera search rebuild-index. Verify the paper is not in Trash or filtered by a collection sidebar selection.
PDF will not open
Re-attach the PDF from the File column. If the file moved on disk, upload again. Use Retry in the viewer after fixing the attachment.
Connector will not connect
See Connector troubleshooting: app running, connector enabled, native host ID, optional HTTP dev fallback.
CLI changes not visible in the app
You may have used --no-notify. Switch views or reload. Confirm avera --json status shows appRunning: true when you expect live refresh.
Note conflict or external update banner
Another session or the CLI changed the note. Reload remote content or copy your edits elsewhere before reloading.
Screening counts look wrong
Refresh the PRISMA tab after decisions. Use manual overrides for counts outside the tool. Check Conflicts and Maybe queues for unresolved papers.
AI chat errors
Verify API key, provider status, and network. Clear chat and retry. Keys are stored locally — re-enter if you rotated keys at the provider.
Still stuck?
Gather app version, OS, signed-in state, and subscription status before contacting support. Internal QA checklists in the app repository cover edge cases for testers but are not required for normal use.