Troubleshooting

Common setup and runtime failures with fixes aligned to current app behavior.

GitHub login fails with `provider is not enabled`

Enable GitHub in Supabase Authentication → Providers, then verify callback and redirect URLs.

Next step: See `docs/supabase-github-auth.md` in the repository.

Use a GitHub OAuth App for Supabase login. GitHub App credentials often fail for user-profile retrieval.

Next step: Replace provider credentials in Supabase and retry login.

Your stored GitHub token is missing/expired. Re-authenticate from dashboard connect flow.

Next step: Click “Re-authenticate with GitHub” on /dashboard/connect.

GitHub token likely lacks `workflow` scope; API may return 403/404 for workflow path writes.

Next step: Log out/in with required GitHub scopes and retry setup.

Site crawling is plan-gated (`site_crawler` feature); free users receive a 403 response.

Next step: Upgrade to Pro or Enterprise to use setup wizard crawling.

A repository crawl job is active. Dashboard resumes progress for the existing job.

Next step: Wait for completion or cancel from the crawl progress UI.

App requires authenticated session and crawler cannot pass login wall unauthenticated.

Next step: Generate Playwright storageState and paste it in the Auth Session step.

Your test did not call `occhio.startFlow()`, `occhio.captureStep()`, and `occhio.endFlow()` in execution path.

Next step: Add required capture calls and run test again.

Missing `Authorization: Bearer <OCCHIO_TOKEN>` header or token is revoked/invalid.

Next step: Generate a new token in dashboard settings and update CI secret.

Hosted PR review limit reached, or account plan has `0` hosted reviews.

Next step: Check billing plan and monthly usage; upgrade for more hosted reviews.

Need infrastructure-specific help (Vercel deploy, Supabase auth, GitHub App fields)? Use repository docs in docs/ alongside these in-app guides.