KB-2147 Mobile provisioning tool fails with "The certificate provided was never sent to Appian" error

Maggie Deppe-Walker — Wed, 08 Feb 2023 05:39:31 GMT

Current Revision posted to Appian Knowledge Base by Maggie Deppe-Walker on 2/8/2023 5:39:31 AM

Symptoms

When using the mobile provisioning tool for generating iOS assets, the following error message is encountered when selecting a signing certificate:

A similar error message may be encountered when selecting an APNS Key as well.

Cause

The selected certificate or APNS key was not previously created using the provisioning tool and sent to Appian. The provisioning tool can only sign mobile builds with certificates that have previously been provided to Appian. The provisioning tool can also only use APNS keys that have previously been provided to Appian.

Action

There are three possible ways to resolve this error message:

Select another certificate that has been provided to Appian.
Use the "Create New" certificate or "Create New" APNS key option rather than use an existing certificate or APNS key.
- Note: There is a two-certificate and two-APNS key maximum. If two certificates or APNS keys are already present, one must be deleted to create a new certificate or APNS key. Be sure to confirm that the deleted certificate or APNS key is not being used by another build, as this will cause issues with the associated build.
If neither certificate or APNS key has been sent to Appian and neither certificate or APNS key can be deleted because it is actively being used by other applications, open a support case with Appian Support.

Affected Versions

This article applies to all versions of the provisioning tool.

Last Reviewed: January 2023

Tags: provisioning tool, Certificate, Mobile

KB-2147 Mobile provisioning tool fails with "The certificate provided was never sent to Appian" error

Nicholas Van Dyke — Thu, 03 Sep 2020 16:16:20 GMT

Revision 8 posted to Appian Knowledge Base by Nicholas Van Dyke on 9/3/2020 4:16:20 PM

Symptoms

When using the mobile provisioning tool for generating iOS assets, the following error message is encountered when selecting a signing certificate:

Cause

The provisioning tool can only sign mobile builds with certificates that have previously been provided to Appian. The selected certificate was not previously created using the provisioning tool and sent to Appian.

Action

There are two possible ways to resolve this error message:

Select another certificate that has been provided to Appian.
Use the "Create New" certificate option rather than use an existing certificate. Note: There is a 2 certificate maximum. If two certificates are already present, one must be deleted to create a new certificate. Be sure to confirm that the deleted certificate is not being used by another build, as this will cause issues with the associated build.

If neither certificate has been sent to Appian and neither certificate can be deleted because it is actively being used by other applications, open a support case with Appian Support.

Affected Versions

This article applies to all versions of the provisioning tool.

Last Reviewed: September 2020

Tags: provisioning tool, Certificate, Mobile

KB-2147 Mobile provisioning tool fails with "The certificate provided was never sent to Appian" error

Nicholas Van Dyke — Thu, 03 Sep 2020 16:16:20 GMT

Revision 9 posted to Appian Knowledge Base by Nicholas Van Dyke on 9/3/2020 4:16:20 PM

Symptoms

When using the mobile provisioning tool for generating iOS assets, the following error message is encountered when selecting a signing certificate:

Cause

Action

There are two possible ways to resolve this error message:

Select another certificate that has been provided to Appian.
Use the "Create New" certificate option rather than use an existing certificate. Note: There is a 2 certificate maximum. If two certificates are already present, one must be deleted to create a new certificate. Be sure to confirm that the deleted certificate is not being used by another build, as this will cause issues with the associated build.

If neither certificate has been sent to Appian and neither certificate can be deleted because it is actively being used by other applications, open a support case with Appian Support.

Affected Versions

This article applies to all versions of the provisioning tool.

Last Reviewed: September 2020

Tags: provisioning tool, Certificate, Mobile

DRAFT KB [SP-4754] Mobile Provisioning Tool fails with "The certificate provided was never sent to Appian" error

Nicholas Van Dyke — Thu, 03 Sep 2020 16:12:00 GMT

Revision 7 posted to Appian Knowledge Base by Nicholas Van Dyke on 9/3/2020 4:12:00 PM

Symptoms

When using the mobile provisioning tool for generating iOS assets, the following error message is encountered when selecting a signing certificate:

Cause

Action

There are two possible ways to resolve this error message:

Select another certificate that has been provided to Appian.
Use the "Create New" certificate option rather than use an existing certificate. Note: There is a 2 certificate maximum. If two certificates are already present, one must be deleted to create a new certificate. Be sure to confirm that the deleted certificate is not being used by another build, as this will cause issues with the associated build.

If neither certificate has been sent to Appian and neither certificate can be deleted because it is actively being used by other applications, open a support case with Appian Support.

Affected Versions

This article applies to all versions of the provisioning tool.

Last Reviewed: September 2020

Tags: provisioning tool, Certificate, Mobile

DRAFT KB [SP-4754] Mobile Provisioning Tool fails with "The certificate provided was never sent to Appian" error

Nicholas Van Dyke — Wed, 02 Sep 2020 15:24:06 GMT

Revision 6 posted to Appian Knowledge Base by Nicholas Van Dyke on 9/2/2020 3:24:06 PM

Symptoms

When using the mobile provisioning tool for generating iOS assets, the following error message is encountered when selecting a signing certificate:

The certificate provided was never sent to Appian.

Cause

Action

There are two possible ways to resolve this error message:

Select another certificate that has been provided to Appian.
Use the "Create New" certificate option rather than use an existing certificate. Note: There is a 2 certificate maximum. If two certificates are already present, one must be deleted to create a new certificate. Be sure to confirm that the deleted certificate is not being used by another build, as this will cause issues with the associated build.

If neither certificate has been sent to Appian and neither certificate can be deleted because it is actively being used by other applications, open a support case with Appian Support.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: provisioning tool, Certificate, Mobile

DRAFT KB [SP-4754] Mobile Provisioning Tool fails with "The certificate provided was never sent to Appian" error

Nicholas Van Dyke — Wed, 02 Sep 2020 15:20:34 GMT

Revision 5 posted to Appian Knowledge Base by Nicholas Van Dyke on 9/2/2020 3:20:34 PM

Symptoms

When using the mobile provisioning tool for generating iOS assets, the following error message is encountered when selecting a signing certificate:

The certificate provided was never sent to Appian.

Cause

Action

There are two possible ways to resolve this error message:

Select another certificate that has been provided to Appian.
Use the "Create New" certificate option rather than use an existing certificate. Note: There is a 2 certificate maximum. If two certificates are already present, one must be deleted to create a new certificate. Be sure to confirm that the deleted certificate is not being used by another build, as this will cause issues with the associated build.

If neither certificate has been sent to Appian and neither certificate can be deleted because it is actively being used by other applications, open a support case with Appian Support.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: provisioning tool, Certificate, Mobile

DRAFT KB [SP-4754] Mobile Provisioning Tool fails with "The certificate provided was never sent to Appian" error

Nicholas Van Dyke — Wed, 02 Sep 2020 15:16:37 GMT

Revision 4 posted to Appian Knowledge Base by Nicholas Van Dyke on 9/2/2020 3:16:37 PM

Symptoms

When using the mobile provisioning tool for generating iOS assets, the following error message is encountered when selecting a signing certificate:

The certificate provided was never sent to Appian.

Cause

Action

There are two possible ways to resolve this message:

Select another certificate that has been provided to Appian.
Use the "Create New" certificate option rather than use an existing certificate. Note: There is a 2 certificate maximum. If two certificates are already present, one must be deleted to create a new certificate. Be sure to confirm that the deleted certificate is not being used by another build, as this will cause issues with the associated build.

If neither certificate has been sent to Appian and neither certificate can be deleted because it is actively being used by other applications, open a support case with Appian Support.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: Mobile

DRAFT KB [SP-4754] Mobile Provisioning Tool fails with "The certificate provided was never sent to Appian" error

Nicholas Van Dyke — Wed, 02 Sep 2020 15:16:07 GMT

Revision 3 posted to Appian Knowledge Base by Nicholas Van Dyke on 9/2/2020 3:16:07 PM

Symptoms

When using the mobile provisioning tool for generating iOS assets, the following message is encountered when selecting a signing certificate:

The certificate provided was never sent to Appian.

Cause

Action

There are two possible ways to resolve this message:

Select another certificate that has been provided to Appian.
Use the "Create New" certificate option rather than use an existing certificate. Note: There is a 2 certificate maximum. If two certificates are already present, one must be deleted to create a new certificate. Be sure to confirm that the deleted certificate is not being used by another build, as this will cause issues with the associated build.

If neither certificate has been sent to Appian and neither certificate can be deleted because it is actively being used by other applications, open a support case with Appian Support.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: Mobile

DRAFT KB-[SP-4754[ Mobile Provisioning Tool fails with "The certificate provided was never sent to Appian" error

Zach Puderbach — Fri, 14 Aug 2020 18:22:17 GMT

Revision 2 posted to Appian Knowledge Base by Zach Puderbach on 8/14/2020 6:22:17 PM

Symptoms

When using the mobile provisioning tool for generating iOS assets, the following message is encountered when selecting a signing certificate The certificate provided was never sent to Appian.

Cause

Action

There are two possible ways to resolve this message:

Select another certificate that has been provided to Appian.
Use the "Create New" certificate option rather than use an existing certificate. Note: There is a 2 certificate maximum. If two certificates are already present, one must be deleted to create a new certificate. Be sure to confirm the deleted certificate is not being used by another build, as this will cause issues with the associated build.

If neither certificate has been sent to Appian and neither can be deleted because they are actively being used by other apps, open a support case with Appian support.

Affected Versions

This article applies to all versions of the provisioning tool.

Last Reviewed: August 2020

Tags: Mobile

DRAFT KB-[SP-4754[ Mobile Provisioning Tool fails with "The certificate provided was never sent to Appian" error

Zach Puderbach — Fri, 14 Aug 2020 18:21:50 GMT

Revision 1 posted to Appian Knowledge Base by Zach Puderbach on 8/14/2020 6:21:50 PM

Symptoms

When using the mobile provisioning tool for generating iOS assets, the following message is encountered when selecting a signing certificate The certificate provided was never sent to Appian

Cause

Action

There are two possible ways to resolve this message:

Select another certificate that has been provided to Appian.
Use the "Create New" certificate option rather than use an existing certificate. Note: There is a 2 certificate maximum. If two certificates are already present, one must be deleted to create a new certificate. Be sure to confirm the deleted certificate is not being used by another build, as this will cause issues with the associated build.

If neither certificate has been sent to Appian and neither can be deleted because they are actively being used by other apps, open a support case with Appian support.

Affected Versions

This article applies to all versions of the provisioning tool.

Last Reviewed: August 2020

Tags: Mobile