-
Notifications
You must be signed in to change notification settings - Fork 15
Description
Problem Statement
For real iOS devices, The WDA build failed when using the default bundle id (com.facebook.WebDriverAgentRunner / .xctrunner) due to provisioning / bundle registration errors.
Proposed Solution
Support configuring the WDA bundle id directly from CLI / env, for example with something like --wda-bundle-id.
Use Case
I want to run Maestro flows on real iPhones in a team environment where the default WDA bundle id cannot be signed under our Apple Development Team.
In that setup, I need to use a team-owned bundle id for WDA so teammates can run the same flows on connected real devices without manually patching WDA source files.
Example
appId: com.example.app
---
- launchApp
- tapOn: "Login"
- assertVisible: "Home"
Example command:
maestro-runner \
--platform ios \
--team-id ABCDE12345 \
--wda-bundle-id com.myteam.WebDriverAgentRunner \
test flow.yamlAlternatives Considered
The workaround I used was to manually patch the downloaded WebDriverAgent project and replace the default bundle id with a team-owned one.
That works, but it is not ideal because:
- it is manual
- it is easy to forget
- it is harder for teammates to reproduce consistently
Additional Context
This may not affect simulator users, but it seems important for real-device onboarding. I’m happy to submit a PR for CLI/config support for custom WDA bundle id