Fix acceptAlertButtonSelector matching 'Don't Allow' instead of 'Allow'

[maggialejandro]

Summary

Fix the acceptAlertButtonSelector WDA setting that incorrectly matched "Don't Allow" buttons on iOS permission dialogs, causing permissions to be rejected instead of accepted on real devices.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactoring (no functional changes)

Changes Made

• Changed acceptAlertButtonSelector from CONTAINS[c] 'Allow' to BEGINSWITH[c] 'Allow' OR label ==[c] 'OK'
• CONTAINS 'Allow' matched both "Allow" and "Don't Allow" buttons — WDA tapped the first match in the hierarchy, which was "Don't Allow"
• BEGINSWITH 'Allow' correctly matches only "Allow" and "Allow While Using App"
• Added ==[c] 'OK' fallback for older iOS dialogs that use "OK" instead of "Allow"

Related Issues

N/A

Testing

• Tests pass locally (make test)
• Linting passes (make lint)
• Added tests for new functionality
• Tested manually with sample flows

Checklist

• Code follows project style guidelines
• Self-reviewed the code
• Added/updated documentation as needed
• No breaking changes (or documented if breaking)
• CHANGELOG.md updated (for notable changes)

Additional Notes

Reproduced on a real iOS device running an app that requests microphone permission. The setPermissions step with microphone: allow configured WDA's auto-alert handler, but the CONTAINS[c] 'Allow' predicate in the acceptAlertButtonSelector matched "Don't Allow" first, rejecting the permission dialog.

[omnarayan]

@maggialejandro nice catch! This one's sneaky — CONTAINS 'Allow' matching "Don't Allow" first is the kind of thing that can drive you crazy debugging on real devices.

BEGINSWITH is the right fix, and the OK fallback for older iOS dialogs is a nice touch. Thanks for the detailed write-up and screenshot too, super helpful.