Troubleshooting
Diagnose BaseBuddy setup, sign-in, mapping, save, upload, and deployment issues.
Start with diagnostics:
shpnpm setup:check
pnpm basebuddy doctorMissing Setup
If the app redirects to onboarding, create app data from /onboarding or the CLI. Onboarding should show the database env screen, the owner account screen, and then the setup checks screen.
Sign-In Fails
Confirm the local user exists in app data, the email is correct, and the app can read app data. Reset the owner password from the CLI if needed.
Content Does Not Load
Check BASEBUDDY_CONTENT_DATABASE_URL in env, then confirm the saved mapping points at existing tables and columns.
Saves Fail
BaseBuddy saves dirty mapped fields only. Unsupported storage shapes should stay read-only or unsupported until you adjust the mapping.
Uploads Fail
Check the mapped storage provider. Supabase Storage and S3-compatible storage still need valid bucket permissions and CORS settings.