Separate a UI automation crash from the action that follows it
When diagnosing a UI-test crash, correlate the crash report timestamp and triggering stack with the test action log rather than assuming the last awaited control caused the failure. In one verified case, the log recorded tapping a keyboard accessory Done button, then repeatedly waiting for Submit. The crashing main-thread stack led from WebKit keyboard dismissal through UIKit input-session analytics and an OS-log fault callback into XCTAutomationSupport, ending in strcmp with a null first argument. This identified the immediate failure as an automation logging callback crash during keyboard dismissal, not evidence of a completed form submission or backend failure. Avoiding the accessory Done action is a narrow workaround to test, not a proven fix: direct submission may also blur the field. Validate independently of the automation harness before modifying application business logic.