UI测试疑问：accessibilityIdentifier可被检测但录制器识别失败，跨iPhone版本异常

I’ve run into this exact issue a few times—here’s what’s going on and how to fix it:

The core problem is that the UI Test Recorder often generates code based on the exact view hierarchy structure of the device you’re recording on. Different iPhone models (especially ones with big screen size differences like iPhone 5 vs 7) can have subtle variations in how the system renders view layers, which makes the recorded code break on other devices. Even worse, the recorder sometimes ignores existing accessibility identifiers in favor of traversing the view tree—this is a well-known limitation of the tool.

Here are the actionable fixes I recommend:

1. Ditch Recorded Hierarchy Code—Use Accessibility Identifiers Directly #

This is the most reliable solution by far. Instead of relying on the recorder’s fragile layer-based code, explicitly target elements using the accessibility identifiers you’ve already set. For example:

// If your static text has the identifier "targetText"
let targetText = app.staticTexts["targetText"]

// If it's inside a collection view cell with its own identifier
let targetCell = app.collectionViews.cells.element(matching: .cell, identifier: "productCell")
let cellLabel = targetCell.staticTexts["productNameLabel"]

This code will work consistently across all devices, as long as your identifiers stay intact.

2. Double-Check Your Accessibility Setup #

Even though you can see the identifier in Accessibility Inspector, it’s worth verifying these details:

• Ensure the identifier is assigned directly to the element you want to test, not a parent container or superview
• Confirm the element’s isAccessibilityElement property is set to true (most standard UIKit controls like UILabel/UIButton have this enabled by default, but custom views might need manual setup)
• Recheck Accessibility Inspector: Select the target element and confirm the "Identifier" field matches exactly what you’ve set (no typos or extra spaces)

3. Refactor Recorded Code to Be Device-Agnostic #

If you need to use recorded code as a starting point, rewrite it to avoid hardcoded boundBy indices (these are the main culprits for cross-device failures). For example:

Instead of this fragile iPhone 7 recorded code:

app.children(matching: .window).element(boundBy: 0).children(matching: .other).element(boundBy: 1).scrollViews.children(matching: .other).element.children(matching: .collectionView).element.children(matching: .cell).element(boundBy: 0).children(matching: .other).element(boundBy: 0)

Simplify it to target key elements directly:

app.collectionViews.cells.element(boundBy: 0).staticTexts["TEXT"]

Or better yet, add an identifier to the cell and use that:

app.collectionViews.cells.element(matching: .cell, identifier: "firstProductCell").staticTexts["TEXT"]

4. Rule Out Version Compatibility Issues #

Older devices like the iPhone 5 might be running an older iOS version, which can have subtle differences in accessibility behavior compared to newer models like the iPhone 7. Make sure your Xcode version is compatible with all the iOS versions you’re testing—using a matching Xcode/iOS version pair can eliminate unexpected hierarchy discrepancies.

内容的提问来源于stack exchange，提问作者Carlos Miguel Colanta