[Documentation](https://fluxnative.app/docs) / Build your app

# Checks

When a type or native check fails, read the diagnostic and fix it in chat or Code; the revision stays so you can repair it.

![The Status tab: open items, the app's three journeys marked Built, and the last checks, beside the preview](https://fluxnative.app/guide-media/checks.b6874f5e.webp)

Status shows open items, the journeys and what the last checks found.

## When a check fails

1. Read the diagnostic: it names the file and the problem.
2. Ask the assistant to continue from the error, or fix the file in **Code**.
3. Send the follow-up. The next revision replaces the failing one.

## Native build failures

The Build panel keeps the reason with the build and says who fixes it. **Fix with AI** starts a chat turn for a code problem, **Retry build** runs it again, and **Show log** reads the log, without secrets.

## Good to know

- Diagnostics stay with the project, not only in one chat message.
- A failed check or a stopped turn never reverts the source. See [Revisions and undo](https://fluxnative.app/docs/revisions).
- A failed native build is not charged.

## Related

[Fix a failed build](https://fluxnative.app/docs/build-failures) · [Troubleshooting](https://fluxnative.app/docs/troubleshooting)

Previous: [App name and icon](https://fluxnative.app/docs/app-icon) · Next: [Export the project](https://fluxnative.app/docs/export)

---

When a type or native check fails, read the diagnostic and fix it in chat or Code; the revision stays so you can repair it.

Page: https://fluxnative.app/docs/checks