Troubleshooting

Things break. When they do, this page is the first stop. It's a running list of the most common things that go wrong, in rough order of how often we see them, and exactly how to fix each one.

If your issue isn't here, jump to the bottom. There's a "still stuck" section with how to reach us.

The preview is blank on my phone

Several possible causes, roughly in order:

1. Expo Go isn't on the latest version. Update it from the App Store or Google Play.
2. Your phone and your preview are on different networks. Switch Appsanic to tunnel mode (Preview > Settings > Tunnel).
3. JavaScript error on first render. Shake your phone to bring up the dev menu, tap Debug to read the error. Usually an import or type error in recent code.
4. Bundler is stuck. In Appsanic > Preview > Restart server.
5. The QR code expired. Close Expo Go, scan again.

If none of that works, try a clean refresh:

1. Close Expo Go entirely.
2. In Appsanic, click Preview > Restart server.
3. Scan the new QR code.

"Native module X is not linked" or "Cannot find module react-native-xxx"

Translation: the agent added a library that needs special "native" code on the phone, but Expo Go doesn't include that specific library, so it can't run it.

Fix: ask the agent to build you a Dev Client (a custom preview app that includes the library):

"Build a Dev Client so I can test this library."

The build takes 10-20 minutes in the cloud. You install the Dev Client like Expo Go and use it as your preview from then on.

Log-in doesn't work

1. Check that you verified your email. If not, check spam; re-send from the log-in screen.
2. Check that your Supabase project is live. Sometimes Supabase pauses free-tier projects for inactivity. Unpause from the Supabase dashboard.
3. Reset your password from the log-in screen if you're unsure.
4. Log out of everything and log back in: clear cookies, restart Expo Go, try again.

If it's consistent across devices, check the Supabase dashboard > Logs > Auth for the specific error.

Stripe checkout doesn't charge me in test mode

You're probably using a live publishable key but a test secret key (or vice versa). They don't mix.

• Your Stripe keys live on the Stripe connector page (Dashboard > Connectors > Stripe). Saved secrets show as encrypted dots and never display again, so if you're not sure which mode you pasted, re-enter both keys from the same mode.
• Both should start with pk_test_ and sk_test_ respectively (for test mode), or both pk_live_ and sk_live_ (for production).
• Click Test connection on the connector page after changing keys.

Also check your webhook secret matches the mode you're in.

Stripe webhook events aren't hitting my backend

• Is the webhook URL correct in the Stripe dashboard? It should point at your app's backend webhook endpoint.
• Is the webhook secret correct? Re-save it on the Stripe connector page (Dashboard > Connectors > Stripe), then run a build so the change takes effect.
• Is Stripe showing failures in the Events log? Stripe > Developers > Events. Failed webhooks show the error, usually a mismatched signature or a 4xx from your app.

Send a test webhook from the Stripe dashboard (Developers > Webhooks > your endpoint > Send test webhook) to verify the pipe is clean before assuming your business logic is broken. Tip: with Account Access switched on for Stripe, the agent can create and wire the webhook for you - and every action it takes is listed in the Activity feed on that connector page.

Push notifications aren't arriving

1. Are you testing on a real device? Pushes don't fire in the simulator/emulator.
2. Did the user grant permission? Check Settings > [Your app] > Notifications on the device.
3. Do you have an Expo push token stored? Check your push_tokens table (or wherever the agent stored it). The token should start with ExponentPushToken[.
4. Are the iOS push credentials uploaded to Expo? Expo dashboard > Credentials > iOS.
5. Are the Android FCM credentials uploaded? Expo dashboard > Credentials > Android. The google-services.json must be current.
6. Sending pushes from your own server? That goes through the Expo Push connector (your Expo access token) and the small relay the agent set up - check that the relay is deployed and the connector's Test connection passes. Receiving pushes needs no connector at all.

If all of that checks out, send a test push from Expo's push tool with the token. That isolates whether the problem is delivery or your send-from-server logic.

The build stopped and asked me to connect a service

That's by design. When the agent needs a service that isn't connected yet - say, Stripe for a checkout screen - it stops, says why in one sentence, and shows a connect card in the chat.

1. Click Connect on the card. The connectors modal opens at that provider, right there on the build page - you don't lose your place.
2. Connect the service (one-click OAuth where available, or paste your keys).
3. The card detects the connection on its own and the build resumes automatically. If it hasn't noticed after a few seconds, click "I'm done - check now" on the card.

One thing that won't work: pasting the key into the chat. The agent refuses keys in chat and points you to the dashboard - chat history is not a safe place for secrets. See In-Chat Connect Cards for the full flow.

My export to GitHub fails

• Is Appsanic authorized for your GitHub account? Open the GitHub panel in the builder - if you're not connected, it shows a Connect GitHub button. You can also check GitHub > Settings > Applications > Authorized OAuth Apps.
• Do you have permission to create repos in the target org? If you chose an org, your GitHub role must allow creating repos.
• Is the repo name already taken? Pick a different name; GitHub rejects duplicates.

For orgs with strict audit rules, your org admin may need to approve Appsanic as an OAuth app before you can export there.

The App Store rejected my app

Most first rejections come from one of five reasons (see Publishing to the App Store):

1. Crashes on launch → test on a real iPhone before resubmitting.
2. Design spam (looks like a template) → add real content.
3. Privacy policy URL missing or broken.
4. Missing Sign in with Apple when you offer another third-party login.
5. Permissions requested without explanation in Info.plist.

Apple's rejection email cites the specific guideline. Fix that exact thing, reply via Resolution Center, resubmit.

Expo Go says "Something went wrong" with no detail

1. Shake your phone, tap Debug for the stack trace.
2. If the stack trace mentions Unable to resolve module, a dependency wasn't installed. In Appsanic, click Preview > Restart.
3. If the error is in a specific file, the agent can usually fix it quickly with: "The preview is crashing with [error]. Fix it."

My screen shows no data, but I can see the data in Supabase

You've probably hit the privacy rules the agent set up. They're doing their job, but a little too aggressively.

The rules say "users only see their own data," and they only know who the user is if the user is signed in at the moment of the query.

Check, in order:

1. Is the user actually signed in at the moment the screen loads? Try signing out and back in.
2. The data you're trying to show. Is it tagged with the signed-in user's ID? In the Supabase dashboard, click the table and check the user_id column.
3. If you added rows manually in the Supabase dashboard, did you remember to set their user_id? The agent does this automatically; manual rows often miss it.

If you're stuck, mention it to the agent and paste the error or the empty screen. It'll usually spot the issue in one round.

The agent keeps making the same mistake

Patterns that help:

1. Restate the constraint explicitly. Sometimes the agent has forgotten an earlier rule. Repeat it in the current prompt.
2. Start a new conversation. Old context can accumulate contradictions. Summarize where you are and what you want, fresh.
3. Switch models. Fast sometimes misses things Pro catches. And vice versa when a prompt is tightly scoped.
4. Ask for a plan. Make the agent surface its assumptions before writing.

My credits burned faster than I expected

Most common causes:

1. Using Pro for Fast work. Use Fast on small tweaks. See Fast vs Pro.
2. Very long conversations. The agent re-reads context on each turn; past turns add up. Start fresh conversations when you switch topics.
3. Ambiguous prompts. Three rounds of clarification cost three times the credits of one good prompt. See Writing Prompts.
4. Dev Client builds. Each is free in credits but takes time. Don't trigger extra ones unnecessarily.

If you think your usage isn't right, email contact@appsanic.com with a rough timeline. We look at the breakdown and sort it out.

Still stuck

Email contact@appsanic.com with:

• What you expected to happen.
• What actually happened.
• Any error messages (screenshot or paste).
• Your project URL in Appsanic.

We respond within 1 business day. For security issues, mention "security" in your subject line so we route it quickly.

Next

Read the FAQ for common conceptual questions, or loop back to the Introduction.