Troubleshooting

Find the symptom you see during setup, then check the configuration it depends on.

Cloning returns a 404 or permission error

Check that you have accepted the repository invitation and that your terminal uses the GitHub account with access. If you use SSH, add --ssh to the scaffold command.

The app closes at launch or reports a missing Supabase key

For local development, set EXPO_PUBLIC_SUPABASE_URL and EXPO_PUBLIC_SUPABASE_ANON_KEY in .env.local, then restart the development server and reload the app.

For a cloud build, check the environment selected by its eas.json profile. Local .env.local values are excluded from the upload. Add the values to the matching EAS environment and create a new build.

The confirmation email does not arrive

The app supports email confirmation. Check the email address, delivery configuration and redirect URLs in Authentication. A successful sign-up request does not prove the email was delivered.

Chat does not return a reply

Check function deployment and the OpenRouter secret. A missing key returns provider_not_configured; an invalid key or insufficient provider credit can fail after streaming starts. The app shows an error with a retry action.

Use a free model and an account with quota available. yarn skills:doctor can check secret metadata when your CLI is signed in and linked, but it does not send a model request.

To test the deployed function, run the bundled verifier with an existing test account that has confirmed its email:

node .claude/skills/setup/scripts/verify-ai.mjs --email "you@example.com" --password "your-test-account-password"

The script sends a real message and can consume provider credit and free quota. Look for the message that the model streamed a response. A quota refusal confirms that the function responded, but it does not test the provider. Without credentials, the script checks only reachability.

For a failure the script cannot explain, open the function’s logs in the Supabase Dashboard. See Chat error codes.

xcode-select: error: tool ‘xcodebuild’ requires Xcode

This error means the selected developer directory points at Command Line Tools instead of a full Xcode installation. Install and open Xcode , then select its developer directory. For the standard application path:

sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
xcodebuild -version

Use your actual Xcode path if it is installed elsewhere. See Apple’s command-line tools settings .

Expo cannot detect Xcode

Open Xcode once to complete installation, accept its license and install the simulator runtime. Check the selected developer directory with xcode-select --print-path. If it points to Command Line Tools, use the command in the section above.

No products or offerings are available from RevenueCat

Check the store products, RevenueCat offering and the key for the platform you are testing. The failure can have several causes, including store agreements or mismatched product identifiers. Follow Payment troubleshooting for the checks and the expected sandbox setup.