Error codes for locally built mobile apps
The following table lists error codes that might be returned when you build a mobile app locally.
| Error | Error code | Error message |
|---|---|---|
| SUCCESS | 0 | Success. |
| UNKNOWN | 1 | Unknown. |
| MOBILE_PROVISIONING_FILE_MISSING | 2000 | The mobile provisioning file does not exist. The error message is returned with one field that contains the name of the missing file: "{0} mobile provisioning file not exists". |
| CERTIFICATE_FILE_MISSING | 2001 | The certificate file does not exist. The error message is returned with one field that contains the name of the missing file: "{0} certificate file not exists". |
| MOBILE_PROVISIONING_INVALID | 2002 | The mobile provisioning file is invalid. The error message is returned with one field that contains the name of the invalid file: "{0} invalid mobile provisioning file". |
| INVALID_PASSWORD | 2003 | The certificate password is invalid. |
| INVALID_CERTIFICATE | 2004 | The certificate file is invalid. The error message is returned with one field that contains the name of the invalid file: "{0} invalid certificate file". |
| KEYCHAIN_FILE_EXIST | 2005 | Unable to create the keychain file, because the file already exists. The error message is returned with one field that contains the name of the existing file: "Unable to create keychain file {0} already exist". |
| KEYCHAIN_ADD_TO_SEARCH_LIST_EXIT_CODE | 2006 | Adding the keychain to the search list failed (exit code). The error message is returned with one field that contains the exit code: "Add keychain to search list failed with exit code {0}". |
| KEYCHAIN_ADD_TO_SEARCH_LIST_EXCEPTION | 2007 | Adding the keychain to the search list failed (reason). The error message is returned with one field that contains the cause of the failure: "Add keychain to search list failed. Reason {0}". |
| KEYCHAIN_CREATE_EXIT_CODE | 2008 | Creating the keychain failed (exit code). The error message is returned with one field that contains the exit code: "Create keychain failed with exit code {0}". |
| KEYCHAIN_CREATE_EXCEPTION | 2009 | Creating the keychain failed (reason). The error message is returned with one field that contains the cause of the failure: "Create keychain failed. Reason {0}". |
| KEYCHAIN_FILE_NOT_EXIST | 2010 | Unable to delete the keychain file, because the file does not exist. The error message is returned with one field that contains the name of the missing file: "Unable to delete keychain file {0} already not exist". |
| KEYCHAIN_DELETE_EXIT_CODE | 2011 | Deleting the keychain failed (exit code). The error message is returned with one field that contains the exit code: "Delete keychain failed with exit code {0}". |
| KEYCHAIN_DELETE_EXCEPTION | 2012 | Deleting the keychain failed (reason). The error message is returned with one field that contains the cause of the failure: "Delete keychain failed. Reason {0}". |
| KEYCHAIN_UNLOCK_EXIT_CODE | 2013 | Unlocking the keychain failed (exit code). The error message is returned with one field that contains the exit code: "Unlock keychain failed with exit code {0}". |
| KEYCHAIN_UNLOCK_EXCEPTION | 2014 | Unlocking the keychain failed (reason). The error message is returned with one field that contains the cause of the failure: "Unlock keychain failed. Reason {0}". |
| KEYCHAIN_IMPORT_EXIT_CODE | 2015 | Importing the certificate to the keychain failed (exit code). The error message is returned with one field that contains the exit code: "Import certificate to keychain failed with exit code {0}". |
| KEYCHAIN_IMPORT_EXCEPTION | 2016 | Importing the certificate to the keychain failed (reason). The error message is returned with one field that contains the cause of the failure: "Import certificate to keychain failed. Reason {0}". |
| KEYSTORE_CREATE_EXCEPTION | 2017 | Unable to create the keystore (reason). The error message is returned with one field that contains the cause of the failure: "Create keystore failed. Reason {0}". |
| SINGLE_CERTIFICATE_EXPECTED. | 2018 | A single certificate expected. |
| INVALID_CERTIFICATE_TYPE | 2019 | The certificate type is invalid – expected X.509. The error message is returned with one field that contains the type of the provided certificate: "Invalid certificate type. Expected X.509 but was {0}". |
| P12_NO_CERTIFICATE | 2020 | The P12 file does not contain the certificate. |
| P12_NO_PRIVATE_KEY | 2021 | The P12 file does not contain the private key. |
| P12_INVALID_KEY_TYPE | 2022 | The key type in the P12 file is invalid – expected an RSA private key. The error message is returned with one field that contains the type of the provided key: "Invalid key type in P12 file. Expected RSA private key but was {0}". |
| NOT_CODE_SIGN_USAGE_PURPOSE | 2023 | The certificate cannot be used for signing the code. |
| CERTIFICATE_EXPIRED | 2024 | The certificate has expired. The error message is returned with one field that contains the expiration date: "Certificate has expired {0} (YYYY-MM-DD)". |
| CERTIFICATE_BEFORE_START | 2025 | The certificate is before the start date. The error message is returned with one field that contains the start date: "Certificate is before start date {0} (YYYY-MM-DD)". |
| MOBILE_PROVISIONING_NO_PREFIX | 2026 | The mobile provisioning file is invalid. The application identifier prefix cannot be retrieved. |
| MOBILE_PROVISIONING_EXPIRED | 2027 | The mobile provisioning file has expired. The error message is returned with one field that contains the expiration date: "Mobile provisioning file has expired {0} (YYYY-MM-DD)". |
| INVALID_IOS_CERTIFICATE_NO_SUBJECT | 2028 | Expected an iOS platform code signing certificate. The certificate subject is missing. |
| IOS_CERTIFICATE_MOBILE_PROVISIONING_MISMATCH | 2029 | The iOS platform code signing certificate does not match any developer certificates in the mobile provisioning file. |
| INVALID_BUNDLE_IDENTIFIER | 2030 | The bundle identifier is invalid. The error message is returned with one field that contains the invalid identifier: "Invalid bundle identifier {0}". |
| BUNDLE_IDENTIFIER_NOT_MATCHING_MOBILE_PROVISIONING | 2031 | The bundle identifier does not match the specification in the mobile provisioning file. The error message is returned with one field that contains the invalid identifier: "Bundle identifier {0} not matches specification in mobile provisioning". |
| INVALID_IOS_CERTIFICATE_INVALID_SUBJECT | 2032 | Expected iOS platform code signing certificate. The certificate subject structure is invalid. |
| INVALID_IOS_CERTIFICATE_NO_OU | 2033 | Expected iOS platform code signing certificate. The organizational identifier is missing. |
| INVALID_IOS_CERTIFICATE_NO_CN | 2034 | Expected iOS platform code signing certificate. The CN identifier is missing. |
| KEYSTORE_FILE_EXIST | 2035 | The keystore file already exists. The error message is returned with one field that contains the name of the existing file: "Keystore file {0} already exist". |
| KEYSTORE_PERSISTENCE_ERROR | 2036 | Unable to persist the keystore (reason). The error message is returned with one field that contains the cause of the failure: "Unable to persist keystore. Reason {0}". |
| FILE_NOT_EXIST | 2037 | The file does not exist. The error message is returned with one field that contains the name of the file: "File {0} not exist". |
| DIR_EXPECTED | 2038 | Must be a directory. The error message is returned with one field that contains the name of the directory: "{0} must be directory". |
| FILE_EXIST | 2039 | The file already exists. The error message is returned with one field that contains the name of the file: "File {0} already exist". |
| LACK_OF_MANDATORY_BUILD_PARAMETER | 2040 | A mandatory build parameter is missing. The error message is returned with one field that contains the name of the missing parameter: "Lack of mandatory build parameter {0}". |
| MALFORMED_PROPERTIES_FILE | 2041 | Malformed properties file. The error message is returned with one field that contains the name of the file: "Malformed properties file {0}". |
| LACK_OF_MANDATORY_JOB_PROPERTY | 2042 | A mandatory build job property is missing. The error message is returned with one field that contains the missing property: "Lack of mandatory build job property {0}". |
| UNSUPPORTED_CONFIG_VERSION_OF_DEVICE_AGENT | 2043 | An unsupported config version of the device agent has been set in the job build properties file. The error message is returned with one field that contains the version of the agent: "Unsupported config version of device agent {0} has been in job build properties". |
| CUSTOMIZATION_ZIP_EMPTY_OR_NOT_PROVIDED | 3000 | The customization.zip file is empty or missing. |
| CUSTOMIZATION_ZIP_MISSING_MANDATORY_RESOURCES | 3001 | The customization.zip does not contain mandatory resources. The error message is returned with one field that contains missing resource(s): "Customization zip does not contain mandatory resources {0}". |
| CUSTOMIZATION_PROPERTIES_MISSING_REQUIRED_PROPERTIES | 3002 | The customization.properties file does not contain mandatory parameters. The error message is returned with one field that contains the missing mandatory parameters: "customization.properties file does not contain mandatory parameter(s) {0}". |
| CUSTOMIZATION_PROPERTIES_INVALID_VALUE | 3003 | A property defined in the customization.properties file has invalid value. The error message returns two fields that contains the incorrectly configured property and its value: "Property {0} defined in customization.properties has invalid value {1}". |
| CUSTOMIZATION_PROPERTIES_CERTIFICATE_PASSWORD_MISSING | 3004 | Integrity of custom certificate: missing certificate password. The error message is returned with one field that contains the name of the property that should be used to set the password: "Integrity of custom certificate. Lack of certificate password. Use {0} property". |
| CUSTOMIZATION_ZIP_CUSTOM_CERTIFICATE_INTEGRITY | 3006 | Integrity of custom certificate: missing file. The error message is returned with two properties that contains the names of the provided and missing files: "Integrity of custom certificate. Provided file {0} but lack of file {1}". |
| CUSTOMIZATION_PROPERTIES_UNSUPPORTED_KEY | 3007 | Unsupported property key. The error message is returned with one field that contains the unsupported key: "Unsupported property key {0}". |