We are experiencing issues during extended automated test executions on iOS devices.
During long-duration test runs that involve a high volume of interactions with the device under test, the socket connection is unexpectedly terminated. When this occurs, the automation session is disrupted and the test run fails.
We would like to better understand the root cause of this behavior and determine whether it is related to the automation framework, the underlying iOS platform, or another system-level constraint.
We have the following questions:
Are there any iOS security mechanisms or system protections that may be triggered after a high number of automated interactions, resulting in the termination of an active socket connection?
Does iOS impose any runtime limitations, session timeouts, resource restrictions, or inactivity thresholds that could impact long-running automation sessions?
Are there any known conditions under which iOS may terminate or reset socket connections during extended periods of intensive device interaction?
Any guidance on troubleshooting steps, relevant system logs, or known platform limitations would be greatly appreciated.