Killing test runner does not end the automation state

[muvaf]

trafficstars

Describe the bug

When I run ios runwda, if I send SIGTERM with Ctrl+C, I see Killing test runner with pid 387 but the phone is still in automation state, eg overlay that says Automation Running is still in place. When I run the same test in Xcode and click on stop button, it does end the Automation Running state as well.

To Reproduce Steps to reproduce the behavior: Run a long-running test, like with the following call:

ios runwda \
  --bundleid="com.somebundle" \
  --testrunnerbundleid="com.somebundle.tests.xctrunner" \
  --xctestconfig=somebundle.xctest

Then send SIGTERM to that command via Ctrl+C. You'll see that it gracefully exits but the phone is still in Automation Running state.

Expected behavior

The phone is back in normal state after shutdown of the test.

Screenshots

Desktop (please complete the following information):

• OS: macOS 15.1.1
• Browser: None
• go-ios version: v1.0.165

Smartphone (please complete the following information):

• Device: iPhone 14
• OS: 17.6.1
• Browser stock safari

Additional context

I run ios tunnel start in a separate tab and all tabs have ENABLE_GO_IOS_AGENT=yes