Test the app on your phone before release work drifts.
Ubriot Console is the mobile companion for cloud builds. Open artifacts, inspect logs, scan dashboard QR codes, read AI diagnosis, check release readiness, and confirm store actions from a real device instead of losing time in a simulator loop.
Build #418
Sorelia, iOS production, TestFlight ready
STATUS
ready
ARTIFACTS
2
CHECKS
pass
AI diagnosis
Last Android failure points to a missing production keystore. Upload the release credential before queueing Google Play.
phone handoff
Scan from the build row, open /preview/open on mobile, then jump into Ubriot Console with ubriot://build/418.
What it handles
A tighter test loop for React Native and Expo teams.
Scan a dashboard QR
Every build can show a phone handoff QR that opens /preview/open and then launches the native app.
Open deep links
Launch ubriot://build and ubriot://artifact links from dashboard buttons, shared links, or a phone browser.
Install artifacts
Open APK or AAB artifacts from Android, and use signed iOS release paths such as TestFlight for iPhone review.
Read the failure
See recent logs and AI diagnosis without opening the dashboard on a laptop.
Check release readiness
Review signing, store, and platform readiness before a production handoff.
Test device registration
Register the phone as a test device for apps that use Ubriot Notify.
Confirm from the device
Cancel running builds or queue store submissions only after a native confirmation prompt.
Boundary
It is not a magic runtime for arbitrary native code.
Preview works with real Ubriot builds, OTA-compatible React Native updates, and artifacts produced through the release pipeline. Custom native modules still need a compatible development build, a signed build, or a store review path. The point is to remove friction from real-device testing, not hide the native boundary.
phone workflow