Refactor how xctestrun files are parsed (#553)

By introducing new methods and introducing a new metadata object to extract the version, the parsing becomes easier to read and extend in the future.

Allow ResponseWithReturnValueInPayload to be passed into dtxConnectio…

…n.Dispatch (#552)

Change noisy log line level from 'Info' to 'Debug' (#549)

Reset ax settings (#546)

Authored-by: fish-sauce <[email protected]>

Add missing proxydispatcher cases + fix productModuleName for iOS <17 (…

…#547)

The method switch in proxydispatcher::Dispatch was missing a few cases, which led to missing XCUITest results when using go-ios on iOS <17 devices.

Additionally, the productModuleName field in the XCTestConfiguration appeared to be wrong (also for iOS <17 devices), leading to the same issue of missing test results. It has been changed to match the iOS 17 config, which seems to work better for the test cases I've tried.

Tunnel mode selection feature for agent mode. (#544)

With this change ENABLE_GO_IOS_AGENT can be set to "user" or "kernel" to start selective mode tunnel.

Co-authored-by: dmissmann <[email protected]>

---------

Co-authored-by: Serhat Toktamisoglu <[email protected]>
Co-authored-by: dmissmann <[email protected]>

Set keepaliveidle time more aggressive against connection drops (#540)

Keepaliveidle time should be set more aggresive than the gVisor's 2 hours default idle time. Many NAT and firewalls drop the idle connections more aggressively (30-60 secs apparently).

Keepaliveinterval option doesn't take affect as the keep alive probe doesn't start before the idle time reaches. It is 2 hours by default and before it reaches NAT/Firewall close the connection unlike kernel mode TUN device,

With this change the idle time will be more aggressive and according to several tests this fix connection drops. Long running test more than 24 hours achieved with this fix.

Add Support for Parsing .xctestrun file and use it to start xctest (#525

)

This pull request introduces enhancements to the go-ios tool by adding the ability to parse .xctestrun files, enabling seamless execution of XCTest. The key updates include:

Key updates include:

1. Parsing .xctestrun File:

A new parseFile method has been implemented to extract test configuration details from the .xctestrun file.
The parsed data includes all details needed to execute an xctest like TestHostBundleIdentifier, TestBundlePath, OnlyTestIdentifiers, SkipTestIdentifiers, IsUITestBundle, CommandLineArguments, EnvironmentVariables, and TestingEnvironmentVariables of the xctestrun file.
Added a validation step to ensure the FormatVersion of the .xctestrun file is supported. Currently, only FormatVersion 1 is accepted, with clear error messages for unsupported versions.
2. Enhanced CLI Command:

Introduced a new ios runxctest command in the CLI with updated explanations for better usability.
Allows users to specify xctestrun file path and output preferences.
3. Improved Test Coverage:

Added test cases to validate parsing of .xctestrun file.
Ensured robust assertions for critical fields like TestHostBundleIdentifier and TestBundlePath.
These updates simplify and enhance the process of running XCTest by directly utilizing .xctestrun files, reducing manual setup and ensuring better adaptability to diverse testing scenarios.

throw an error if userpsace tunnel is used for ios <17.4 (#534)

postinstall: add arm64 as valid arch (#530)

Signed-off-by: Muvaffak Onus <[email protected]>