fix: document SwiftUI Text link tap limitation in test-xcode skill#400
Merged
fix: document SwiftUI Text link tap limitation in test-xcode skill#400
Conversation
Simulated taps via XcodeBuildMCP (and all iOS simulator automation tools) silently fail on SwiftUI Text views with inline AttributedString links due to a platform limitation — inline links are not exposed as separate accessibility elements. Added a known-limitation note in the testing step and a human-verification table entry so the agent prompts for manual taps instead of retrying silently. Closes #59.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Simulated taps via XcodeBuildMCP (and all other iOS simulator automation tools — idb, XCUITest, Appium) silently fail on SwiftUI
Textviews with inlineAttributedStringlinks. This is a fundamental platform limitation: inline links are not exposed as separate elements in the accessibility tree, so no automation tool can target them. Taps report success but have no effect.This adds a known-limitation note in Step 5 (Test Key Screens) and a human-verification table entry in Step 6 so the agent detects the silent failure pattern and prompts the user to tap manually. Also documents
xcrun simctl openurlas a fallback when the target URL is known.Closes #59
🤖 Generated with Claude Opus 4.6 (1M context, extended thinking) via Claude Code