Skip to content

Documentation · Test and release · 2 min read

Test your app, then get it ready

The browser preview, phone testing through Expo Go, and the release checks.

Run it in the browser

Preview, above the canvas, runs your real app. Tap through it, open the keyboard, follow its navigation. The console beneath it lists what the app prints, with the file and line that logged it, and an error shows a card that links to the exact line in Code. Ask Sanic AI about any error from that card.

Code keeps the same preview beside your files, rebuilding after each change.

On your phone

Test on phone opens the phone testing dialog. Start phone preview packages the project, compiles it for Android and iOS and shows a QR code; scan it in Expo Go on Android or with the camera on iPhone. Your phone and computer must share a network, and Expo Go must support the project's Expo SDK.

Applied changes are sent to the phone as you keep editing. Pause and resume the updates, send the latest version by hand, or stop the preview, from the same dialog. Devices & updates shows the phones that have connected.

Phone testing works in the local editor and is coming soon on the hosted site.

What a preview can and cannot prove

A clean web preview does not establish how a phone renders your app, and Expo Go cannot run features that need a native build: purchases, push notifications, error reporting and libraries with native code. Code reports native compatibility problems separately, so you learn about them before you are on a device.

  • Layout, touch targets and fonts on a real phone.
  • The keyboard, safe areas and both orientations your app supports.
  • Denied permissions and a lost network connection.

Get it ready for the stores

Open Settings in the rail for App settings. General holds the app's identity; iOS, Android, Icons & launch, Permissions, App links, Store listing and Publishing each have a section, and Search all settings finds any field. Release checks lists what the App Store and Google Play still need, including fields that only become required because of an answer you gave, and opens the right control for each.

Completing the checks prepares a release. Signing, store accounts and submission happen in the store consoles today; signed builds and submission from Appsanic are coming.

All guides