Skip to main content

Auth Emails Or Google Login Are Not Working

Check these first:
  • NEXT_PUBLIC_SUPABASE_URL
  • NEXT_PUBLIC_SUPABASE_ANON_KEY
  • NEXT_SUPABASE_SERVICE_KEY
  • Supabase Auth URL configuration
In Supabase, make sure:
  • Site URL is set correctly
  • /auth/confirm is included in your redirect URLs
  • Google OAuth is enabled if you expect Google sign-in to work
This is almost always a redirect mismatch. Check:
  • NEXT_PUBLIC_APP_URL
  • Supabase Site URL
  • Supabase Redirect URLs
The repo expects the auth confirmation flow to go through:
  • /auth/confirm
If that route is missing from your allowed redirects, sign-in can partially work but never finish correctly.

A Model Does Not Show Up In The UI

Usually one of these is true:
  • the provider API key is missing
  • the model is not exposed in lib/ai/models.ts
  • the app does not use that provider path
  • the model supports fewer capabilities than you expected
Example:
  • a model may support text but not browsing
  • a model may support text but not vision

PDF Chat Is Not Working

PDF chat depends on more than one thing:
  • storage must be configured
  • OpenAI embeddings must be available
  • the document must actually be uploaded and indexed
  • the document must be attached to the chat flow
If you can upload a PDF but do not get useful citations, the usual causes are:
  • embeddings were never created
  • retrieval found no strong matches
  • OpenAI is missing so the vector step cannot run
Read:

Image, Video, Voice, Or Vision Uploads Fail

Check the storage variables:
STORAGE_REGION
STORAGE_ACCESS_KEY
STORAGE_SECRET_KEY
STORAGE_ENDPOINT
STORAGE_BUCKET
STORAGE_PUBLIC_URL
Many app flows depend on file storage. If storage is not configured correctly, the apps may load but uploads and saved outputs will fail.

Payments Do Not Record Purchases

Usually one of these is wrong:
  • NEXT_PUBLIC_PAYMENT_PROVIDER
  • provider webhook secret
  • webhook URL
  • hosted checkout URLs
  • product/variant mapping
Also make sure your provider is sending webhooks to:
  • /api/payments/[provider]
If checkout works but purchases are missing from the app, the webhook path or secret is usually the culprit.

Analytics Is Not Firing

Check:
  • NEXT_PUBLIC_ANALYTICS_PROVIDER
  • provider-specific analytics env vars
  • whether you restarted the dev server after changing env
If you use multiple analytics providers, the syntax matters. The repo expects a comma-separated value like:
NEXT_PUBLIC_ANALYTICS_PROVIDER=posthog,datafast

Voice Studio Loads But Some Generation Modes Fail

Voice Studio has several separate API paths:
  • voices
  • text-to-speech
  • speech-to-speech
  • music
  • sound effects
If one mode works and another fails, do not assume the whole app is broken. Check the specific mode, payload, and ElevenLabs access for that feature.

The App Runs But Looks Outdated Or Mismatched

This is usually a branding/content issue, not a runtime issue. Check:
  • config.ts
  • landing page copy
  • pricing sections
  • app descriptions
  • docs content
Because this repo includes both product and marketing surfaces, outdated copy in one place can make the whole repo feel inconsistent.

Mintlify Docs Preview Looks Wrong

Check:
  • Mintlify is pointed at the anotherwrapper-premium repo
  • the docs root is docs/public
  • the nav in docs/public/mint.json matches the files that exist

Good Debugging Order

When something is broken, check in this order:
  1. env vars
  2. provider credentials
  3. redirect URLs or webhook URLs
  4. storage config
  5. whether the feature depends on a second provider you forgot about
That order usually saves time.