Skip to main content

SeeTestAutomation- iOS Profile Management and Creating Certificates And Provision Profiles

info

Please note that this tool is classified as a Legacy tool. We recommend transitioning to our updated solutions to maintain optimal performance and security in your workflows. For more information on this matter, please reach out to technical support .

This section explains how to create certificates, provision profiles, p12 files, and a developer profile (.developerprofile) that our products can work with.

These are used in the iOS profile management.

  1. Create an Apple Certificate
  2. Create a Provision Profile
  3. Create a Developer Profile or Create a .p12 file

In order to get to the iOS profile management:

  1. Click Tools → iOS Provision Profile Management.

  2. Click Import from Apple developer account.

  3. Export the Apple Developer Account file (.developerprofile).

  4. Upload it

  5. Enter the file's password. The file contains several signing identities and provision profiles, choose the combination to work with. 

  6. Generate the Certificate file (.p12) and Apple provision profile (.mobileprovision).

  7. Enter certificate's password, then click OK.

Troubleshooting​

When adding a device, if 'Full control' is checked it means the device has a valid matching profile. 

In a case where the device does not open, look for the following exceptions on a log.

 Signing Identity Profile Not Found​

When working on a Mac your Keychain must contain the iPhone developer certificate which is used from Continuous Testing. The certificate will be on the Login user and must have its private key. If it isn't there, import to your keychain the .p12 file for this certificate. 

Apple Worldwide Developer Relations Certification Authority Doesn't Exist​

When working on a Mac your Keychain must contain this certificate. The certificate will be on the System user. 

Wrong Trust Settings for Apple Worldwide Developer Relations Certification Authority​

Change the trust settings to use the system default.

All signing identities on Keychain need to have the trust setting 'Use system default'.

Last updated on