Getting Started & Support

Your guide to configuring and troubleshooting the FeatherSense AI application.

Can't Log In?

If you're seeing an "api-key-not-valid" error, it's likely that the client-side keys below are not configured correctly in your deployment environment. For a complete diagnosis, please visit the full Connection Tests page.

Loading client configuration...

Server-Side Secrets (`apphosting.yaml`)

For your deployed application to function, you must create these secrets in Google Cloud Secret Manager and reference them in your `apphosting.yaml` file.

secrets:
  - secret: GOOGLE_APPLICATION_CREDENTIALS
  - secret: NEXT_PUBLIC_GEMINI_API_KEY
    availableToFrontend: true
  - secret: NEXT_PUBLIC_FIREBASE_API_KEY
    availableToFrontend: true
  - secret: NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN
    availableToFrontend: true
  - secret: NEXT_PUBLIC_FIREBASE_PROJECT_ID
    availableToFrontend: true
  - secret: NEXT_PUBLIC_FIREBASE_STORAGE_BUCKET
    availableToFrontend: true
  - secret: NEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID
    availableToFrontend: true
  - secret: NEXT_PUBLIC_FIREBASE_APP_ID
    availableToFrontend: true
  - secret: NEXT_PUBLIC_RECAPTCHA_SITE_KEY
    availableToFrontend: true

Local Development (`.env.development`)

To run the app locally, create a file named `.env.development` in the project root and add the following variables.

# .env.development

# Google AI Studio API Key
NEXT_PUBLIC_GEMINI_API_KEY="..."

# Firebase Client SDK Configuration
NEXT_PUBLIC_FIREBASE_API_KEY="..."
NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN="..."
NEXT_PUBLIC_FIREBASE_PROJECT_ID="..."
NEXT_PUBLIC_FIREBASE_STORAGE_BUCKET="..."
NEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID="..."
NEXT_PUBLIC_FIREBASE_APP_ID="..."

# Google reCAPTCHA v3 Site Key (for Firebase App Check)
NEXT_PUBLIC_RECAPTCHA_SITE_KEY="..."

# Firebase Admin SDK Service Account (must be a single line)
GOOGLE_APPLICATION_CREDENTIALS='{ "type": "service_account", ... }'

Back to Login