FriendChise Docs
Troubleshooting
Fixes for the problems contributors hit most often
Most local problems trace back to .env.local, the local database, or a stale Prisma client. Start here before opening an issue.
App won't start / build fails
- Re-check
.env.localagainst Environment Variables —DATABASE_URL,AUTH_SECRET, andAUTH_URLare required for a basic boot. - Run
pnpm prisma generateif types look stale after pulling schema changes. - Run
pnpm installagain if a dependency is missing after a pull.
Database
- Port
5432already in use: stop the other Postgres service, or map the Docker container to a different host port and updateDATABASE_URLto match. - Schema drift / migration errors: re-run
pnpm prisma migrate dev. See Migrations and Seeding. - Seed looks stale or wrong:
pnpm seedis destructive for the currentSEED_NAMESPACEbecause it clears that namespace before reseeding. Use a disposable namespace for routine reseeds, and usepnpm seed:cleanwhen you only want to remove your own namespaced data.
Auth / sign-in
- Session loops or immediately signs out: usually a missing/incorrect
AUTH_SECRETorAUTH_URL, or anAUTH_SECRETthat doesn't match between environments (this also affects the mobile app — see Mobile Authentication). - OAuth sign-in fails locally: OAuth is optional in development — leave
AUTH_GOOGLE_ID/AUTH_GOOGLE_SECRETblank and use the seeded dev-user picker on the sign-in page instead.
Demo sessions
- Demo button returns an error / 429: the demo pool has a concurrency cap (see Task System and Operations); wait for an existing demo session to expire and retry.
- Mobile demo/dev sign-in link doesn't work: dev and demo credential flows are only registered when
NODE_ENV === "development"— they will not work against a production build.
Uploads / images
- Uploads fail or images don't render:
NEXT_PUBLIC_SUPABASE_URLandSUPABASE_SECRET_KEYare required for any upload/logo/task-image flow — see Environment Variables and Image Handling.
Still stuck
- Run the Smoke Test to isolate whether the issue is setup-wide or feature-specific.
- Open an issue with what you tried from this page.
TODO
- Add known Sentry/Upstash Redis local-dev quirks once they come up often enough to document.
