Common issues
Quick fixes for the most reported OpenV2 problems — 404 errors, preview failures, chat, and publishing.
Start here when something breaks. Pick the area that matches your symptom, or scan the 404 section below if you see Not Found anywhere.
Browse by topic
- Preview & workbench — blank preview, bundler errors, device QR
- Chat & generation — chat stuck, credits, bad AI output
- V2 Cloud & backend — auth, database, uploads, API errors
- Account & publishing — login, billing, deploy, native builds
404 Not Found — where it happens
Documentation page shows 404
| Cause | Fix |
|---|---|
| URL missing the page slug | Open a page from the sidebar, e.g. /docs/troubleshooting/overview — not /docs/troubleshooting alone |
| Wrong language prefix | Romanian pages live under /docs/ro/...; English under /docs/... |
| Page just added | Hard-refresh the browser or restart the local dev server so new docs are picked up |
Use Search in the docs header to jump to the right article.
App preview shows “Unmatched Route” or 404 screen
Your generated Expo app is missing a route file for the screen you opened.
- Note the path shown in the preview error (e.g.
/settings). - Ask the chat: “Add the missing screen for
/settingsand wire navigation to it.” - Or add
app/settings.tsx(or the matching route) in the Code editor.
See Preview & workbench.
Published web app or demo URL returns 404
- Confirm the project preview builds without errors in the workbench.
- Run Web deploy again from the publish flow — old URLs may point to a removed build.
- Check Visibility & live demo — private projects on Free may not serve a public demo.
See Account & publishing.
V2 Cloud or API request returns 404
| Cause | Fix |
|---|---|
| Wrong collection or bucket name | Use col('logical_name') helpers — ask the AI to sync names with the schema |
| Hook or server function path typo | Check Logs and fix the route in chat |
| Record deleted or wrong ID | Verify the ID in your query matches an existing row |
See V2 Cloud & backend.
Still need help?
Email support@openv2.dev with:
- Project name
- What you clicked or typed (full URL if 404)
- Screenshot of preview logs or the error message
