Revyl Xcode 27.1 builds
You can now build your iOS app with Xcode 27.1 in the cloud.
Pick the ios-macos-26-xcode-27.1 toolchain image for an iOS cloud build. It has the iOS 27.1 SDK and simulator runtimes 27.1, 27.0, 26.5, 26.2 and 18.5, including iPhone Duo. Xcode 27.0 stays the default, so nothing changes until you pin the new image in your build config or with --image. See toolchain images.
Pixel Tablet and Figma in Proof of Changes
You can now test tablet layouts on Android, and Proof of Changes can check a change against its Figma design.
This release also adds revyl device set-fold-state, so you can fold or unfold a running iPhone Duo from the CLI or MCP.
Start Android sessions and tests on Pixel Tablet with Android 14. Pick it like any other device. The screen has no phone camera cutout, the viewer keeps the tablet’s orientation as it rotates, and clearing text after a rotation targets the right field.
Link a Figma frame in your pull request description, and the proof agent reads it. It captures the same screen on the device, compares the two, and names the visible differences your change made. This uses your organization’s Figma team connection: an owner or admin adds a token under Integrations → Figma. Read about Proof of Changes.
Capy and Devin in Experiments
You can now turn on Capy and Devin yourself and hand work from Revyl to your own coding agents.
This release also doubles the credits in the Free plan for new organizations, and web tests now run inside workflows next to iOS and Android.
An owner or admin turns on Capy or Devin in Settings → Experiments, then connects your own key under Integrations. Send an Atlas screen or a test report to an agent to fix or investigate. Capy can also prove your pull requests. Agent usage bills your Capy or Devin account. Set up Capy.
Web testing and a faster test agent
Your team can now turn on web testing and a faster test agent yourselves, from Settings → Experiments. You can also test foldable layouts on iPhone Duo.
This release also opens GitLab to every organization.
Web testing is now open to every organization. An owner or admin turns on Web apps in Settings → Experiments; it isn’t on by default. The confirmation shows the rate before you opt in. Turning it off hides Web but keeps your apps and builds, and sessions already running finish.
Owners and admins can move their organization’s runs onto a faster test agent from Settings → Experiments. It covers every run, CI included. Runs already in progress keep the agent they started with.
Run sessions and tests on iPhone Duo with iOS 27.1. Add a fold state step to fold or unfold the device from YAML, the test editor, or the quick actions in a live session. Live views and reports follow whichever panel is active. Duo works everywhere except Atlas.
Connect GitLab.com or a self-managed GitLab instance with an automation token, then build merge requests and post Proof of Changes on them. An owner or admin connects it with revyl gitlab connect. Set up GitLab.
Git branch detection
Uploads and runs now follow your Git branch, so a build lands where your code lives.
This release also sets a new app’s default branch from its first upload, reuses matching native builds across branches for Expo and React Native apps with fingerprinting on, and opens Atlas on All branches when a link names no branch.
Upload without picking a branch, and the build goes to your current Git branch. Automatic runs try that branch first, then fall back to your app’s default branch. Explicit branches, exact builds, and saved choices still win. Prefer the default branch? Turn off Automatic Git branch detection in App settings → Build branches.
Atlas Chat and build branches
You can now ask Atlas about your app and get answers tied to the exact screens. Builds also get branches, and the web app works on your phone.
This release also adds app icons and an App settings page, breadcrumbs on nested pages, and build caches in your home folder.
Ask a question from the bar on your Atlas map. It reads your screens, builds, tests, and reports, and links its answer to the exact captures. Use it to find issues, explore flows, or compare two builds. Findings open as a canvas you can share.
Atlas Chat is rolling out now. If you don’t see it yet, ask us to turn it on for your team.
Open Build branches in your app’s settings to create branches and set each one’s default build. When you start a run, pick a branch, then Automatic, Latest build, or an exact build. From the CLI, pass --branch.
Every screen in the web app now fits a phone. Lists stack into cards, dialogs open as bottom sheets, and controls are sized for touch.
Filter an Atlas map by device model and OS from the Device & runtime panel in the scope control. The filter stays in the URL, so you can share it. Run again on an exploration report now fills in the previous run’s settings.
Dragging a large .app folder into an upload no longer drops files. Remote builds that need Git credentials fail right away instead of waiting until they time out. Findings show again on reports linked to an exploration. Signing in again takes you back to the link you opened. The CLI no longer creates a duplicate run when a response is lost.
A Builds page and signed store builds
Every build in your organization now lives in one place. Remote builds can also sign your app and upload it to App Store Connect or Google Play.
This release also adds app-scoped navigation, a queue for runs at your device limit, a simpler first run, revyl feedback, private share links from the CLI, and iOS 27.0.
Open Builds in the sidebar to see every build, live ones first. Open one to see each step with its own logs. If a build fails, copy the Agent handoff.
Remote builds can now sign a release build with your own certificate or keystore, then upload it to App Store Connect or Google Play. Your build commands don’t change. The Signed Store Builds guide covers both platforms.
Pick an app in the top bar and the product scopes to it. Its Overview shows sessions, builds, proof runs, and device time.
When every device is busy, new runs wait in a queue instead of failing. Interactive sessions go first. The capacity indicator on the Sessions page shows what’s running and what’s waiting.
A failed quarantined test no longer fails its workflow. Tests stay running when a step fails partway through. Validations pass on the screenshot check, with video as a fallback. Explorations that hit a dead end finish as completed. CLI errors show the real cause instead of “test not found”.
Proof of Changes verdicts and cloud builds
Proof of Changes now tells you how ready a pull request is, not just pass or fail. revyl build also runs in the cloud by default.
This release also adds push notifications on iOS cloud devices, comments and Cursor in the Atlas canvas, a Builds tab in Live Monitor, and proxy support in the CLI.
Every proof now ends as Ready, Ready with polish, Ready with issues, Failed, or Inconclusive. Each write-up scores its confidence from 1/5 to 5/5 and links real problems to their Atlas threads. Find every run under Cloud Agents → Proof of Changes. Read about Proof of Changes.
revyl build now builds on Revyl’s cloud runners instead of your machine. Add --local to keep building locally. Cloud builds use compute credits, and a failed one never falls back to a local build. Set up remote builds.
revyl device push sends a notification to your app in a live iOS session. You don’t need a push token, a signed build, or the push entitlement. Your app still has to allow notifications.
Android live views no longer get stuck on “Waiting for device screen”. iOS text entry no longer reports success on an empty field. Slow iOS launches no longer time out, and a crash on launch now shows in the report. Proof of Changes no longer sticks on “Waiting for CI build” after an upload to a draft pull request.
GitHub automation for every workspace
GitHub automation is out of early access. Install the Revyl GitHub App, and any workspace gets pull request previews and repository config. Atlas comments also get mentions and an Inbox.
This release also adds preview links that always open the latest build, a Current map view in Atlas, session IDs for device commands in the CLI, and video downloads from reports.
Install the Revyl GitHub App on a repository, then add it from the GitHub integration settings. Pull requests use the Revyl config from their own commit, so a config change gets checked in the same pull request. Push a valid config to your default branch, and the project is created for you. Read the GitHub docs.
@mention a teammate in an Atlas comment. Mentions, replies, and status changes land in your Inbox. Comments can carry files, and threads can be marked Blocker, Issue, or Polish.
Each app now has one preview link that always opens its latest build. Copy it from the app’s menu on the Apps page, and share one link instead of a new one for every upload.
Device video shows up as soon as the stream is ready. iOS sessions no longer fail to start when a notification covers the app. Dates like “today” in test steps use the device’s time zone. Remote builds can pull private GitHub dependencies. An Android emulator crash a few seconds after launch is fixed. Viewers can no longer run or delete workflow runs.
Live device embeds and Atlas comments
You can now put a live cloud device running your app on any web page. Your team can also comment right on Atlas screens.
This release also adds Explore from the CLI, compiler caching for remote builds, ordered iOS launch arguments, and screenshot exports from reports.
Open a build, choose Configure > Public embed, and paste the snippet into your site or docs. Visitors click Start live demo and use your app on a cloud device, right on the page. Attach launch variables to open it signed in to a demo account. Read the embed guide.
Turn on Annotate and pin a comment to any spot on a screen. Reply and resolve from the Comments rail, and see who else is in the map while you work. Coding agents can read and resolve threads from the CLI.
revyl explore run starts Explore from your terminal or CI and shows progress until the Atlas map is ready. Explore from the CLI.
Clearing a field on Android now checks that it’s empty. Android deep links keep every query parameter. Flutter apps that use Impeller no longer crash on Android. The build page no longer freezes in Safari. Some iOS sessions no longer drop touch input. Closing a pull request preview tab releases the device.
Faster Expo builds and evidence in pull requests
Expo builds now skip the native rebuild when only your JavaScript changed. Proof comments on pull requests show screenshots inline, with no sign-in needed.
This release also adds secret launch variables.
Revyl fingerprints the native side of your Expo app. If a matching build already exists, Revyl repacks it with your new JavaScript instead of rebuilding iOS or Android. It’s on by default. Read about fingerprinting.
Proof comments now show screenshots and GIFs right in the comment, with a link to a shared report. Reviewers don’t need a Revyl account to see them.
Mark a launch variable as secret, and it’s encrypted and write-only. Reports keep it masked and show everything else.
Drag screenshots out of a live device
Take a screenshot on a live device and drag it straight into another app. Atlas onboarding now maps your app from one card.
This release also opens Cloud Agent Conversations to every organization and keeps device controls close in narrow windows.
Click the camera button in the live device toolbar. A preview shows up in the corner. Drag it into any app, and it lands as a PNG.
Answer one optional question about logging in, and Atlas starts mapping your app without leaving the setup timeline.
Under 1024 pixels wide, a session switches to a simulator-only view. Share, Shake, and Rotate stay right beside the device.
01 Open a cloud device and try what we just shipped.