Skip to main content

Development Troubleshooting

This guide covers common issues you might encounter during FindU development and how to resolve them.

Setup Issues

Repository Clone Failures

Problem: Can’t clone repositories
Solution:
  1. Ensure you have GitHub organization access
  2. Use HTTPS clone if SSH isn’t set up
  3. Check with team lead for repository access

Missing Environment Files

Problem: No .env file in repository Solution: Create from example or get from team

Component-Specific Issues

Web App

”Cannot find module” errors

Solution: Install dependencies

Port already in use

Solution: Kill the process or use different port

iOS App

”No such module ‘Supabase’”

Solution: Install CocoaPods dependencies

Missing Secrets.xcconfig

Solution: Copy example and add credentials

Database Issues

Connection refused

Problem: Can’t connect to Supabase Solution: Check your credentials
  1. Verify .env has correct Supabase URL and keys
  2. Test connection in Supabase dashboard
  3. Check if using dev or prod credentials
  4. Ensure no typos in environment variables

Permission denied errors

Problem: RLS policies blocking access Solution:
  1. Check if using correct user role (anon vs service)
  2. Verify RLS policies in Supabase dashboard
  3. Use service role key for admin operations

Python/ML Environment

Module import errors

Solution: Create and activate virtual environment

Environment Configuration

Missing credentials errors

Problem: .env.local has placeholder values Solution: Get real credentials from team lead
  • Required: Supabase project ID, URL, and anon key
  • Optional: Service keys, OAuth credentials

Wrong environment credentials

Problem: Using wrong Supabase instance Solution: Update your .env files
  1. Get correct credentials from team lead
  2. Update .env in each repository
  3. Restart your development servers
  4. Verify by checking data in Supabase dashboard

Git & GitHub Issues

Permission denied (publickey)

Problem: SSH key not configured Solution: Use HTTPS or setup SSH

Pre-commit hook failures

Problem: Code doesn’t pass linting Solution: Fix issues or skip temporarily

Performance Issues

Slow dependency installation

Solution: Use faster registry

High memory usage

Solution: Limit concurrent processes

Getting Help

Check Documentation

  1. Repository CLAUDE.md files
  2. Internal docs
  3. Component-specific READMEs

Ask the Team

  1. Search Slack history in #dev
  2. Post specific error messages
  3. Include steps to reproduce

Debug Commands

Common Fixes Checklist

When something’s not working, try these in order:
  1. ✓ Is Docker running?
  2. ✓ Are you in the right directory?
  3. ✓ Did you run npm install?
  4. ✓ Is .env.local configured?
  5. ✓ Did you pull latest changes?
  6. ✓ Did you restart the service?
  7. ✓ Check Slack for known issues
Most issues are solved by one of: installing dependencies, starting Docker, or configuring environment variables.