Troubleshooting & Performance
The builder feels slow
RapidNative bundles your app in a Web Worker in your browser. If that's slow, usually one of these is the cause:
- Too many screens open in the canvas. Close a few or use Zoom out.
- Browser. Chrome or Edge give the best performance today.
- Low-spec device with a very large project. Try on a laptop.
Preview or runtime fails to start
- Reload the page. The runtime re-bundles cleanly on refresh.
- Check your internet connection (initial package fetch needs network).
- Check the in-app console for errors and use Fix with AI on reported issues.
My database is empty
Every project comes with mock data populated by default. If you're seeing an empty state, your app likely dropped into "fresh user" mode. Sign out of the in-browser test user and sign back in, or reset mock data from the schema panel.
Auth, file upload, or real-time isn't working
These are provided by Vibecode DB's backend adapters. Make sure you haven't swapped to a Custom REST adapter without wiring up the endpoints. Default Supabase and SQLite adapters work out of the box.
Generation fails or returns errors
- Make your prompt more specific.
- Check that you haven't hit your monthly request limit. You can upgrade at rapidnative.com/pricing.
- Retry. If it keeps failing, email support@rapidnative.com with the project URL.
The exported project behaves differently
The in-browser runtime is a real React Native runtime, but minor differences can show up in exported Expo builds as upstream versions change. Run npx expo start locally and test on a real device to confirm. File any mismatch as a bug so we can track it.
Crash recovery
Your work auto-saves continuously. Reopen the project, and you'll resume exactly where you left off. Use Rollback if you need to jump back to an earlier version.
Browser compatibility
RapidNative works in all modern browsers. Chrome, Edge, Safari, and Firefox. Older browsers without Web Workers and WASM support are not supported.
Reporting bugs
Email support@rapidnative.com or use the Report a Bug page. Include the project URL and steps to reproduce. That's usually all we need.