Device configuration - MobileBoost

MobileBoost picks the device each test runs on. What you choose is the kind of device: a real handset reserved for your organisation, or an emulator or simulator.

Choosing the kind of device

Set usePhysicalDevice in the POST /tests/execute payload:

{
  "organisationId": "org123",
  "buildId": "BUILD_ID",
  "tags": ["critical"],
  "usePhysicalDevice": true
}

Value	Runs on
`true`	A real handset reserved for your organisation
`false`	An emulator or simulator
Omitted	Your organisation’s default: a real handset if you have one reserved for the run’s platform, otherwise an emulator or simulator

Some runs always use a real handset, whatever you send:

iOS .ipa builds. An .ipa is signed for devices and cannot be installed on a simulator. Upload a simulator build (the .app bundle in a .zip or .tar.gz) to run on a simulator. See Build requirements.
Runs by bundleId. Only a reserved handset has your app already installed.

Device settings from QA Studio

deviceConfigs and deviceProviderSettings are not supported by POST /tests/execute: you cannot name a device model, OS version, locale or third-party device cloud per run. A request that sends either field is refused with 400, rather than run on a device you did not ask for. Remove them and use usePhysicalDevice.