Signing Status Messages¶

The following is the list of messages that may be returned in the signing_status_details field for each signing status: in_progress, cancelled, signed, or error:

Signing Status¶

in_progress

Message: The application is being signed.

Description and Troubleshooting: No problems yet. The signing process has successfully started.

cancelled

Message: The signing request was cancelled.

Description and Troubleshooting: The signing request was cancelled. Currently, you cannot cancel a signing request through the API. You can cancel a signing request from the Admin Portal (on the Signing tab).

If the status is cancelled, you will need to issue a new request to sign the app.

signed

Message: The application was signed successfully.

Description and Troubleshooting: The application is successfully signed and can now be distributed to your users.

error

Message: The appid is not a wildcard and does not match the bundleid's second value.

Description and Troubleshooting: This is an error that may be returned when signing an iOS application.

The App ID associated with the provisioning profile is an explicit App ID and it does not have a suffix that matches the bundle ID of the app that you are signing. Check that you are signing with the proper signing credentials. For more information on App IDs, see App Identifiers.

error

Message: The application is missing a distribution profile.

Description and Troubleshooting: The application needs to be built with a distribution provisioning profile. Be sure to have the app developer build it with a distribution provisioning profile rather than a development provisioning profile. For a description of the difference, see the Signing FAQ.

error

Message: The application has a development-only distribution profile and cannot be distributed to other devices.

Description and Troubleshooting: The application is built with a development provisioning profile instead of a distribution provisioning profile. For a description of the difference, see the Signing FAQ.

error

Message: The signing service is not responding.

Description and Troubleshooting: There may be a network problem connecting with the signing server. Try the request again.

error

Message: Expired session.

Description and Troubleshooting: The authentication token has expired. Use POST /users/authenticate to generate a new token.

error

Message: A parameter is invalid.

Description and Troubleshooting: Check the syntax of your API request.

error

Message: The credentials are invalid.

Description and Troubleshooting: Check that the signing credentials are appropriate for the type of app you are signing. Use the GET /credentials resource to return information about the signing credentials stored in Apperian for your organization.

Note

As features are added and enhanced in Apperian, the number of errors and the exact wording of messages may change. The messages are written to provide helpful debugging information for anyone who examines the log files that your application captures.

Signing Error Messages¶

The following is the list of errors that may be returned if the signing process cannot start. Replace {0} or {1} with the relevant app_psk or credentials_id.

Message	Troubleshooting
`Application {0} does not exist.`	Check that the correct `app_psk` was specified.
`Credentials {0} does not exist.`	Check that the correct `credentials_id` was specified.
`Application {0} is not a signable application type.`	The Signing API can be used to sign iOS and Android applications only. Check that the `app_psk` is for one of those application types and that you provided the correct credentials.
`Credentials {0} has expired.`	The signing credentials specified with `credentials_id` are expired. Use the GET /credentials resource to check the `expiration_date` of credentials in your organization and to get the `credentials_id` for credentials that are still valid. You can also view the status of signing credentials in the Admin Portal.
`Platform types of application {0} and credential {1} don't match.`	You specified signing credentials that do not correspond to the application type of `app_psk`. For example, `app_psk` is an iOS app, and you specified the `credentials_id` for an Android certificate/key pair.

Note that as features are added and enhanced in Apperian, the number of errors and the exact wording of messages may change. The messages are written to provide helpful debugging information for anyone who examines the log files that your application captures.