iOS 27: What's New and What Breaks for App Testing

What Is New in iOS 27?

Most iOS 27 new features are aimed at iPhone users, but several change what a UI test sees on screen or how an app behaves underneath it. The table maps each change in Apple's release notes to the test it affects.

Apple's iOS 27 page also says app launches are up to 30% faster, measured by Apple on an iPhone 11 Pro Max running iOS 26.6 against prerelease iOS 27. Re-measure launch-time budgets on iOS 27 devices, older models included, before you compare a new build against numbers recorded on iOS 26.

iOS 27 Supported Devices and Release Timeline

iOS 27 runs on every iPhone that ran iOS 26: iPhone 11 and later, plus iPhone SE (2nd generation and later), per Apple's iOS 27 page. Apple Intelligence features need an iPhone 16 model or later, iPhone 15 Pro, or iPhone 15 Pro Max, so AI-dependent flows need their own device list.

The releases so far, from Apple's security releases page, release notes and developer releases feed:

Apple's iPhone Duo announcement sets availability from Friday, October 23, 2026, with pre-orders from October 16, and describes iOS 27 as tailored for iPhone Duo.

The Xcode 27.1 release notes list SDKs for iOS 27.1 and iPadOS 27, plus known issues in the iPhone Duo Simulator runtime, such as StandBy being unavailable. If you support the foldable, add it to the matrix as its own iOS 27.1 row.

In October 2026, the TestMu AI real device list for app automation showed iOS 27 on these models, next to the other iOS versions that belong in the same matrix:

Device inventory changes as devices are updated, so filter the live device list by OS version before you pin a model in CI.

Keep iOS 26 in the matrix while users upgrade: Apple's security releases page still lists iOS 26 updates, including iOS 26.7.1. The iOS version fragmentation guide covers how to weight older versions in a test plan.

What Breaks When You Build With the iOS 27 SDK?

Most of these changes apply when you build with the iOS 27 SDK in Xcode 27, not when an existing build runs on an iOS 27 device. A suite can pass on iOS 27 devices today and fail right after the toolchain upgrade, so run it once on the Xcode 27 build before you change anything else.

Apple's Adopting Liquid Glass guide names UIDesignRequiresCompatibility as the key that keeps an app looking as it did under previous SDKs while it ships with the latest ones, which made it the Liquid Glass opt-out.

Apple's UIDesignRequiresCompatibility documentation states that the system ignores the key when you build for iOS 27 or later, so the compatibility mode that displayed an app as it looked under previous SDKs no longer applies to those builds.

Treat the first iOS 27 SDK build as a visual change to every screen and re-baseline screenshots before you review diffs.

Apple's upcoming requirements page lists no iOS 27 SDK deadline yet. Since April 28, 2026, uploads must be built with Xcode 26 and the iOS 26 SDK, and since September 9, 2026, apps must target iOS 13 or later.

Xcode 27 Changes for UI Testing

Xcode 27 includes Swift 6.4 and the iOS 27 SDK, installs and runs only on Apple silicon Macs, and needs macOS Tahoe 26.6 or later. It supports on-device debugging on iOS 17 and later.

Keep a second runner on an older Xcode for any iOS 15 or 16 devices still in your matrix, and move the rest of the CI fleet to Apple silicon before you switch builds to Xcode 27.

• Device Hub - simulators and physical devices open in Device Hub, which can also pair iPhones and iPads running iOS 27 over the network without a cable. During parallel testing, simulators may not show in Device Hub while they run tests.
• Crash severity in test plans - a test plan can treat a crash of the app under test during UI testing as off, a warning, a failure (the default) or a fatal failure.
• XCUIVoiceOverService - a new XCTest API drives VoiceOver from UI tests and checks focus, spoken output and navigation. Pair it with manual iOS VoiceOver checks on a real device.
• Launch tests per configuration - a new launch test template opts into runsForEachTargetApplicationUIConfiguration, so one test runs across every orientation, localization and appearance the app supports.
• Cross-framework assertions - an XCTest assertion called inside a Swift Testing test, or the reverse, raises a runtime warning when it fails, controlled by a new test plan setting.
• Agents in Xcode - coding agents can boot simulators, install and launch apps, synthesize touch events and capture screenshots to check UI behavior.

Swift Package Manager can now repeat tests until a condition is met, which helps reproduce a flaky package test from the command line after the toolchain upgrade:

swift test --maximum-repetitions 50 --repeat-until fail

Appium and XCUITest on iOS 27

Appium tracked Xcode 27 and iOS 27 support in issue 22368, which lists the XCUITest driver and WebDriverAgent changes made for it and was closed on September 20, 2026. These items from that issue change how a working iOS suite behaves:

• No Simulator.app - Xcode 27 opens simulators in Device Hub, so older XCUITest driver versions fail when they try to open the Simulator window. Update the driver, or set appium:isHeadless as a workaround.
• WebDriverAgent builds - building WebDriverAgent with Xcode 27 needed a higher iOS deployment target. The maintainers note that iOS 27 also works with a WebDriverAgent built by Xcode 26.
• Lock commands - locking the device might not work on iOS 27 before XCUITest driver 11.17.5.
• System UI order - the order of system UI elements changed in iOS 27, so flows that pick a system alert or permission button by position need updating. Locate those elements by accessibility ID or label instead.
• Keyboard on real devices - a WebDriverAgent keyboard issue reports that the keyboard dismisses and reappears during automated text input on real iOS 27 devices. The maintainers traced it to XCTest and closed it as not planned.

Text entry in a web context takes a different path. A Safari search on a real iPhone 18 Pro with iOS 27.0 typed its query intact, and the session capabilities show the stack it ran on:

{
  "automationName": "XCUITest",
  "browserName": "Safari",
  "deviceName": "iPhone 18 Pro",
  "platformName": "ios",
  "platformVersion": "27.0",
  "realDevice": true
}

For native app suites, the getting started with XCUITest docs cover running XCUITest on real devices. If you are also planning the next driver upgrade, what's new in Appium 4 covers the changes in Appium's next major version.

Safari 27 Changes for Web Testers

Read navigator.userAgent in Safari on a real iPhone 18 Pro with iOS 27.0 and the OS token reports 18_7, while the Version token reports 27.0:

Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/27.0 Mobile/15E148 Safari/604.1

In WebKit bug 298260, WebKit engineers explain that Safari's OS version is frozen on purpose, that all Apple platforms will report 18_7, and that the Safari version is a good analog for the OS version on iOS.

• Read the Version/27.0 token when a test needs the Safari major version, and use feature detection for behavior checks.
• Update analytics, device detection and UA-based routing tests that parse "iPhone OS", since they will bucket iOS 27 traffic as iOS 18.
• Check expected strings against the current iOS user agents list instead of hardcoding an OS version.

According to WebKit, the Safari 27.0 feature count rose from 58 to 80 after the first beta in June, and WebKit added 60% more fixes after announcing 525 at WWDC, reaching a total of 844.

These Safari 27 changes alter what automated web tests see:

• Full-page screenshots - WebDriver full-page screenshots were clipped to the viewport before this release, so full-page baselines captured on Safari 26 will not match new captures.
• Subpixel inline layout - inline layout now places elements with subpixel precision, and CSS Zoom was rebuilt, so text and inline elements can shift by a fraction of a pixel in visual diffs.
• Scroll anchoring - content no longer jumps when something loads above it, which changes assertions on scroll position after lazy content arrives.
• Digital Credentials - new WebDriver commands simulate wallet payloads, wait indefinitely for a credential response, and simulate a user rejecting the request.
• Safari MCP - on a Mac, safaridriver --mcp lets coding agents read the DOM, network requests, screenshots and console output once "Allow remote automation and external agents" is checked in Safari's Developer settings.
• Customizable select - appearance: base-select restyles the select element and its picker, an opt-in change that resets dropdown screenshots on pages that adopt it.

A plain pixel diff flags those fractional text shifts across a whole site. TestMu AI's visual AI testing uses Smart Ignore to filter rendering noise such as sub-pixel font variation and anti-aliasing, so a Safari 27 re-baseline surfaces real layout changes instead of one-pixel noise on every screenshot.

How to Test Your App on iOS 27 With TestMu AI

TestMu AI's real device cloud runs iOS 27 on physical iPhones and iPads, so launch behavior, Face ID and keyboard input come from the real OS rather than a simulator. These steps run a first check:

• Pick the devices - filter the device list by iOS 27, and pair at least one iOS 27 model with the same model on iOS 26, such as iPhone 17 on both.
• Set the capabilities - set platformName to ios, platformVersion to 27 and isRealMobile to true. Without isRealMobile, the session runs on a simulator.
• Connect - point the driver at https://mobile-hub.lambdatest.com/wd/hub with your username and access key.
• Run and review - upload the .ipa built with Xcode 27 or install it from TestFlight, run the suite, and review the video, device logs and network logs of each session.

This Node.js script runs a Safari search on a real iPhone 18 Pro with iOS 27 using selenium-webdriver, then prints the page title and the user agent:

const { Builder, By, until } = require('selenium-webdriver');

const capabilities = {
  browserName: 'Safari',
  'LT:Options': {
    platformName: 'ios',
    deviceName: 'iPhone 18 Pro',
    platformVersion: '27',
    isRealMobile: true,
    build: 'iOS 27 Release Check',
    name: 'Safari search on iOS 27',
    w3c: true,
  },
};

const hub = 'https://' + process.env.LT_USERNAME + ':' + process.env.LT_ACCESS_KEY +
  '@mobile-hub.lambdatest.com/wd/hub';

(async () => {
  const driver = await new Builder().usingServer(hub).withCapabilities(capabilities).build();
  try {
    await driver.get('https://ecommerce-playground.lambdatest.io/');

    // The mobile layout renders two search inputs; type into the visible one
    const boxes = await driver.findElements(By.css('input[name="search"]'));
    let search;
    for (const box of boxes) {
      if (await box.isDisplayed()) { search = box; break; }
    }
    await search.sendKeys('iPhone');
    await driver.executeScript('arguments[0].form.submit()', search);

    await driver.wait(until.elementLocated(By.css('.product-layout')), 30000);
    console.log('Title:', await driver.getTitle());
    console.log('UA:', await driver.executeScript('return navigator.userAgent'));
    await driver.executeScript('lambda-status=passed');
  } catch (err) {
    await driver.executeScript('lambda-status=failed');
    throw err;
  } finally {
    await driver.quit();
  }
})();

The session passes on iOS 27.0, prints "Search - iPhone" as the title, and returns the frozen 18_7 user agent shown in the Safari section. The final screen shows the results under Safari's floating toolbar:

• Face ID failure paths - iOS 27.0.1 fixed iPhone 18 Pro and Pro Max restarts when Face ID fails to authenticate. Real devices simulate successful and failed Face ID matches, so biometric login fallbacks can run on the model that had the bug.
• Coverage beyond iOS 27 - the same account reaches 10,000+ real Android and iOS devices, with network profiles from 2G to 5G and offline, and geolocation from 170+ countries.
• iPhone 18 Pro - the test on iPhone 18 page covers real iPhone 18 Pro and Pro Max devices plus their iOS 27 simulators for earlier checks.

Getting Started With iOS 27 Testing

Rebuild the app with Xcode 27 on an Apple silicon runner, then run the full suite once on an iOS 27 device and an iOS 26 device before you change anything else. Fix the scene life cycle and launch screen first, then re-baseline screenshots for Liquid Glass and update any test that picks system alerts by position.

When the Xcode 27 build passes, run it through app automation on TestMu AI, following the app testing on real devices docs, across the iOS 27 and iOS 26 devices your users actually carry.