Maestro re-verification on iPhone 17 / iOS 26.4 / Xcode 26.4.1 proved the previous "canonical pattern replaces all workarounds" framing was wrong. The accessible={false} fix is necessary but not sufficient. Three independent issues all need their own fix: 1. Accessibility tree aggregation (accessible={false} on layout Views) 2. TouchableOpacity onPress not firing under Fabric+XCUITest (Pressable migration with JS-level disabled guard) 3. Flex containers intercepting synthetic taps even with accessible={false} (buttons rendered as siblings, not children, of flex:1 spacers) Plus the previously documented ToggleSwitch (UISwitch onValueChange bug) and testID props. Removing any one of #1, #2, or #3 breaks E2E silently — Maestro reports the tap as COMPLETED but the synthetic touch never reaches JS. The hierarchy dump confirms XCUITest finds the element correctly; the gesture is intercepted upstream of the JS layer. Restructured production-code-changes section to enumerate all three clearly, with diagnostic notes. Updated Future Possibility #7's CLAUDE.md content with all three rules + a diagnostic workflow agents can use when "Maestro tap COMPLETED but app didn't respond." Marked Unresolved Question #5 resolved. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Copied the RFC process from Rust with very slight modifications. #1

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions