[KazuCocoa]

Appium 4 initializes timeout capabilities by assigning BaseDriver properties directly, bypassing the XCUITest timeout setters. A session created with timeouts: {pageLoad: 45000} therefore reports 45 seconds while the remote debugger still uses the default 6 seconds.

Synchronize the initial page-load timeout through the existing setter before backend startup. This preserves the reported capability value while applying the existing internal timeout limit. Regression tests exercise the real session capability handling and remote debugger construction for explicit, zero, null, oversized, and omitted page-load timeouts.

Addresses finding 1 from the review of #3111. Targets beta, where the Appium 4 migration lives.

Validation:

• The four explicit-value regression cases failed before the fix; the omitted-value case passed.
• Build passed.
• Timeout, automation-session, and context unit tests: 53 passed.
• Lint and formatting checks passed.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

Applies the initial page-load timeout before backend startup.

• Initial page-load timeouts reach the remote debugger before backend startup.

_{Reviews (2) · Last reviewed commit: "fix: apply initial page-load timeout bef..." · Reviewed by Greptile}

[mykola-mokhnach]

beta was promoted to master (released as 13.0.0) and the beta branch is being removed, so this PR was retargeted to master. beta was rebased onto master with new commit SHAs, so please rebase this branch onto master (e.g. git rebase --onto origin/master <old-beta-base> <branch>); until then the commit list/diff will include the old beta commits.

[KazuCocoa]

Looks like this CI failure is the webdriverio's version update reason from v9 to v10 - /property/value by #3114. I'll create a followup

[github-actions]

🎉 This PR is included in version 13.0.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀