> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openv2.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Fix common issues with preview, package installs, credits, collaboration, and builds.

## Preview not loading or showing a blank screen

**Symptoms:** The device preview frame is blank, stuck on a spinner, or showing a stale version of your app.

**Steps to fix:**

1. Click the **reload** button in the preview chrome to force a refresh.
2. Open the **terminal** panel and look for errors from `expo start` or a failed `npm install`.
3. If you recently added or changed dependencies, wait for the install to complete before reloading.
4. If the preview still does not load, ask the AI assistant to check for configuration errors in your `app.json` or `package.json`.

## Package install failing in the terminal

**Symptoms:** `npm install` or `npx expo install` exits with an error, or a package is missing after install.

**Steps to fix:**

1. Copy the **full error output** from the terminal.
2. Paste it into the AI chat and ask for a fix. The assistant can identify the cause and suggest a compatible package or an alternative install command.
3. Note that some packages requiring **native binary compilation** cannot install in the browser-based WebContainer environment. The AI can suggest a Expo-compatible alternative.
4. If the issue looks network-related, wait a moment and retry the install command.

## App looks different on device vs. browser preview

**Symptoms:** Styling, layout, or features behave differently when scanned with Expo Go or run on a physical device compared to the browser preview.

**Explanation:** The browser preview uses Expo's **web target** (React DOM). Your physical device runs true **React Native**, which uses native components and APIs. Some differences are expected — especially for camera, haptics, fonts, and navigation gestures.

**Steps to fix:**

1. For an accurate preview, use **Expo Go** by scanning the QR code from the preview panel.
2. For full native fidelity, create a **development build** — see [Test on your device](/test-on-device).
3. If a specific feature works in the browser but not on device, describe the behavior to the AI assistant; it can check for web-only code paths and fix them.

## Credits exhausted

**Symptoms:** A notice appears in the chat saying you are out of credits. New AI turns are blocked.

**Steps to fix:**

<Tabs>
  <Tab title="Free plan">
    Your daily credit allowance resets each day. Wait for the reset, or upgrade to a Pro or Ultra plan for a larger monthly pool — go to **Settings → Billing** or click **Upgrade** in the header.
  </Tab>

  <Tab title="Pro or Ultra plan">
    You have used your monthly credit allocation. Go to **Settings → Billing** to upgrade to a higher credit tier or switch to a plan with more credits.
  </Tab>
</Tabs>

See [Billing & plans](/billing-plans) for full details.

## Invite link not working

**Symptoms:** A collaborator opens the invite link and sees an error, is redirected to a wrong page, or is not added to the project.

**Steps to fix:**

1. Make sure the recipient **signs in** to Openv2 before or during the invite flow. Invite links require authentication — the recipient must complete sign-in with the invite URL intact.
2. Confirm the link has not expired or been revoked. Generate a new invite link from **Invite collaborators** in the project header if needed.
3. Ask the recipient to clear their browser cache for the Openv2 domain and try the link again.

See [Collaboration](/collaboration) for the full invite flow.

## Build failing

**Symptoms:** A mobile build (iOS or Android) errors out in the build flow.

**Common causes and fixes:**

* **Native dependency issues** — Some packages require native modules that must be configured in `app.json` or `eas.json`. Paste the build error into the AI chat for a diagnosis.
* **Missing capabilities or entitlements** — iOS features like push notifications and Sign in with Apple require entitlements configured in your Apple Developer account. See [App Store](/app-store) for setup guidance.
* **Build configuration** — If your project uses EAS Build, the AI assistant can review your build configuration and identify mismatches. Paste the full build log into chat and ask for a diagnosis.

## AI not applying changes

**Symptoms:** The AI responds but files are not updated, or the wrong file is edited.

**Steps to fix:**

1. Check that the **file path** in your prompt is correct. Reference the file by its exact path (e.g., `app/(tabs)/index.tsx`) so the AI targets the right file.
2. Provide a more specific prompt. Instead of "update the button", try "in `components/Button.tsx`, change the background color to blue and increase the font size to 16".
3. If the AI seems confused about the current state of a file, paste the relevant code block into the chat for context.
4. Check the **terminal** — if a previous command is still running, the AI may be waiting before applying file changes.

## Related pages

<CardGroup cols={2}>
  <Card title="FAQ" icon="circle-question" href="/faq">
    Quick answers to common questions about Openv2.
  </Card>

  <Card title="Billing & plans" icon="credit-card" href="/billing-plans">
    Manage credits and upgrade your plan.
  </Card>

  <Card title="Collaboration" icon="users" href="/collaboration">
    Fix invite and access issues for your team.
  </Card>

  <Card title="Test on your device" icon="mobile-screen" href="/test-on-device">
    Use Expo Go or a dev build for accurate device previews.
  </Card>
</CardGroup>