Local Testing Fixes

Local Testing Fixes

This document explains what was fixed to enable local testing of the Supabase connection feature.

Issues Fixed

1. API Not Starting - Missing ENCRYPTION_KEY

Problem: API was crashing on startup because it couldn't find ENCRYPTION_KEY.

Fix:

  • Updated dotenv configuration to load .env.local from project root
  • Added better error handling for missing environment variables

Action Required:

  • Ensure .env.local exists in project root with ENCRYPTION_KEY set
  • Generate key: openssl rand -base64 32

2. Connections Form Not Working

Problem: The form had a TODO comment and wasn't actually making API calls.

Fix:

  • Created API client utility (apps/web/src/lib/api.ts)
  • Implemented full API integration in connections page
  • Added form state management
  • Added loading states and error handling
  • Added user ID management (default user for development)

3. Missing User ID Management

Problem: API requires userId but there was no way to get/create one.

Fix:

  • Created default user endpoint (/api/users/default)
  • Added user utility to get/create default user
  • Updated frontend to fetch user ID on mount
  • Updated all API calls to use the fetched user ID

How to Test

Step 1: Verify Environment

  1. Check .env.local exists:

    cat .env.local | grep ENCRYPTION_KEY

  2. If missing or using placeholder, generate and set:

    openssl rand -base64 32
# Copy output and add to .env.local

Step 2: Ensure Database is Set Up

  1. Check database exists:

    psql -l | grep unifiedcron

  2. Run migrations if needed:

    cd packages/database
pnpm build
node dist/migrate.js

Step 3: Start Servers

  1. Start development servers:

    pnpm dev

  2. Verify both are running:

Step 4: Test Supabase Connection

  1. Set up Supabase (if not done):

    • Run SQL from docs/supabase-setup.sql in Supabase SQL Editor
    • Get Project URL and Anonymous Key from Supabase dashboard

  2. Test in UnifiedCron:

  3. What should happen:

    • Form shows "Connecting..." while submitting
    • Modal closes on success
    • Connection appears in the list
    • Error message shows if something fails

Step 5: Verify Connection Works

  1. Check connection appears in the connections list
  2. Test connection using the Test button
  3. Refresh jobs to discover cron jobs from Supabase

Debugging

If Form Still Doesn't Work

  1. Check browser console:

    • Open Developer Tools (F12)
    • Look for JavaScript errors
    • Check Network tab for failed requests

  2. Check API is running:

    curl http://localhost:3001/health

  3. Check API logs:

    • Look at terminal where pnpm dev is running
    • Check for error messages

  4. Test API directly:

    # Get default user ID
curl http://localhost:3001/api/users/default
 
# Should return: {"success":true,"userId":"...",...}

Common Error Messages

"Failed to connect to API"

  • API is not running
  • Check port 3001 is accessible
  • Restart API server

"User ID not available"

  • API endpoint /api/users/default failed
  • Check API logs for errors
  • Verify database connection

"Failed to create connection"

  • Check API logs for detailed error
  • Verify Supabase credentials are correct
  • Check database is accessible

Connection created but test fails

  • Supabase views might not be set up
  • Run SQL from docs/supabase-setup.sql
  • Verify Project URL and Anon Key

Files Changed

  • apps/web/src/lib/api.ts - New API client
  • apps/web/src/app/connections/page.tsx - Full API integration
  • apps/api/src/routes/users.ts - Default user endpoint
  • apps/api/src/utils/user.ts - User utility functions
  • apps/api/src/index.ts - Better env loading
  • packages/database/src/migrate.ts - Always create default user

Next Steps

After successful connection:

  • Test job discovery (Refresh Jobs)
  • View jobs in dashboard
  • Test connection refresh
  • Try deleting and re-adding connections
DevelopmentTroubleshooting