Common Issues

Purpose: Quick fixes for setup and runtime errors. Audience: Developer, Support Prerequisites: Local env configured; access to Supabase and Stripe dashboards.

For AI-specific issues, see AI Troubleshooting Guide.

Environment problems

• Missing env vars: Ensure .env contains VITE_SUPABASE_URL, VITE_SUPABASE_PUBLISHABLE_KEY, VITE_STRIPE_PUBLISHABLE_KEY.
• Wrong project ref: Replace placeholders with your project, never commit secrets.

Supabase

• 401/403 from PostgREST: Check RLS; verify user session exists (see src/contexts/AuthContext.tsx:45-53).
• Functions 404 in dev: Run Supabase local or update proxy. See vite.config.ts:12-17.
• Realtime not firing: Check channel table filters in useGlobalRealtimeNotifications.ts:31-55, 65-74.
• Blur policy:
  • Field visible but should be blurred: verify blurred_fields row for field_key; check listing_view_secure projection; confirm subscription status (active) and expiry.
  • Admin/Owner still blurred: ensure bypass via can_view_field; confirm user role/ownership and refresh cache.
  • Admin toggle no effect: check admin_toggle_blurred_field (admin only) and updated_at; invalidate ['blurred-fields'] cache in UI.

Stripe

• Webhook signature errors: Verify endpoint secret in Edge Function env. See supabase/functions/stripe-webhook/index.ts:5-12.
• Test cards: Use 4242 4242 4242 4242 (any future expiry, any CVC, any zip).
• Payout failing: Confirm Connect account KYC; handled in webhook mapping.

CORS / Proxy

• In dev, calls to /functions/v1/* should proxy to Supabase local (127.0.0.1:54321). See vite.config.ts:12-17.

Build/Preview

• White screen after deploy: Ensure SPA fallback to index.html is enabled.

Listing Visibility Issues

• Listing approved but not visible on /explore:
  • Check if seller is verified: SELECT seller_verification_status FROM profiles WHERE id = 'seller-uuid'
  • If seller not verified, listing only visible to owner/admin
  • Solution: Verify seller first, then approve listing
• Admin approval not updating verification_status:
  • Ensure using updated approval logic in AdminListings.tsx
  • Check seller verification status before approval
  • Verify RLS policy requires both status='active' AND verification_status='approved'
• Listing visible to owner but not public:
  • Check verification_status in listings table
  • Must be 'approved' or 'verified' for public visibility
  • Update manually if needed: UPDATE listings SET verification_status='approved' WHERE id='listing-uuid'

Next steps

• See docs/operations/deployment.md for hosting configs.
• See docs/setup/environment.md for env examples.
• See docs/features/listings.md for complete approval flow documentation.