Skip to main content

iOS App Resigning

When you upload an iOS app to TestingBot, we will automatically re-sign the .ipa file with our own provisioning profile, to be able to install and run your app on our mobile devices.

Your app keeps its own bundle identifier, so tests and flows that refer to it keep working. Because the app is signed with a different team, most of its entitlements are removed, as described below.

You can choose to disable this re-signing, if your app is signed using the Apple Developer Enterprise Program. This way you can test push notifications or universal links on our physical devices.

Which entitlements are kept

When we resign your app, we combine the entitlements of your signed app with those our development provisioning profile allows. Only these remain:

  • Keychain access groups: kept, but the team prefix of each group changes to TestingBot's team. Shared keychain groups between your app and its extensions keep working. If your code builds a group name with your own team ID written into it, read the prefix at runtime instead. If your Info.plist contains an AppIdentifierPrefix key, we update it to the new prefix.
  • Debugging (get-task-allow): enabled, as in any development build.
  • Application identifier: set to TestingBot's team with your app's bundle identifier.

If you upload an unsigned app (for example one built with --no-codesign), it has no entitlements of its own to keep: it is signed with the profile's entitlements only, so your app's own keychain access groups are not added.

All other entitlements are removed, so the capabilities that depend on them do not work in a resigned app. This includes:

  • Push notifications
  • Associated domains (universal links, shared web credentials)
  • App Groups (shared containers between your app and its extensions)
  • iCloud, CloudKit and iCloud key-value storage
  • Apple Pay and Wallet pass types
  • HealthKit, HomeKit, Siri, NFC tag reading and network extensions (including VPN)
  • Sign in with Apple and any other capability you enabled for your App ID

If your app needs one of these capabilities during a test, sign it with an Apple Developer Enterprise Program certificate and disable resigning. If iOS refuses to install a resigned app in an Appium session, the session fails with an error saying that the app may use capabilities that cannot be resigned for the device.

Disable iOS Resigning

capabilities = {
  "tb:options" => {
    "resigningEnabled" => false
  }
}
Map<String, Object> tbOptions = new HashMap<>();
tbOptions.put("resigningEnabled", false);
options.setCapability("tb:options", tbOptions);
$capabilities = [
  "tb:options" => [
    "resigningEnabled" => false
  ]
];
capabilities = {
  "tb:options": {
    "resigningEnabled": False
  }
}
const capabilities = {
  "tb:options": {
    "resigningEnabled": false
  }
};
var tbOptions = new Dictionary<string, object>
{
  ["resigningEnabled"] = false
};
options.AddAdditionalAppiumOption("tb:options", tbOptions);
Was this page helpful?
Last updated