I am unable to use prepare wda command to build the resigned ipa. It gives blank bundle identifier after it has created the ipa, Can someone help me with this. I am using macbook with iOS 26 and iPhone 17 with iOS 26 #1987
Unanswered
Mridul2110
asked this question in
Q&A
Replies: 1 comment 5 replies
-
|
U have issue with your provision profile. I would say open xcode and allow it to automatically sync n create a new profile |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Component
Version
Appium
3.0.0 (also tested on 2.19.0)
appium-xcuitest-driver
10.9.0
Device Farm Plugin
11.1.3 → 11.2.10 → 11.2.11 tested
macOS
Sequoia 15.x
Xcode
16.1 / 16.2
iOS devices
iOS 18.x (model with UDID 00008150…)
Signing
Free Apple Developer account
Issue Summary
Preparing WebDriverAgent IPA using:
appium plugin run device-farm prepare-wda
--mobile-provisioning-file="/Users/.../Provisioning Profiles/.mobileprovision"
✓ WDA project is found
✓ Build is successful
✗ Signing step corrupts generated IPA
plutil -p Payload/WebDriverAgentRunner-Runner.app/Info.plist | grep CFBundleIdentifier
"CFBundleIdentifier" => ""
Meaning:
• Bundle identifier becomes empty string
• Installed app fails integrity verification
• App does not launch or quits instantly
• Appium logs:
Failed to start the preinstalled WebDriverAgent in XXXX ms
Integrity could not be verified
CFBundleIdentifier is empty / missing
So preinstalled WDA sessions always fail.
⸻
Expected Behavior
prepare-wda should produce a valid IPA using the correct bundle identifier derived from:
• provisioning profile
• or updatedWDABundleId capability
• or Xcode project defaults
⸻
What does work
✔ Building and running WebDriverAgent directly from Xcode
✔ Appium Inspector can establish a session using Xcode-launched WDA
✔ Device Farm works fine for Android and iOS simulators
→ Issue is isolated to signing WDA IPA via prepare-wda.
Attempt
Result
Different plugin versions (11.1.3 → 11.2.11)
Same issue
Different provisioning profiles
Same issue
Using correct capabilities (usePreinstalledWDA=true)
WDA does not start — /status fails
Custom manual ZIP packaging
Bundle ID preserved, install succeeds
prepare-wda IPA resign logic
Always results in empty bundle identifier
Beta Was this translation helpful? Give feedback.
All reactions