# Processing Error Codes

> Reference guide for Applivery Build processing error codes — diagnose and resolve failures across iOS, Android, macOS, Windows, and Homebrew.

Source: https://docs.applivery.com/en/app-distribution/builds/processing-error-codes/  •  Last updated: 2026-03-31

**Key topics:** Error codes, Build processing, Troubleshooting, Applivery, Mobile app deployment, iOS, Android, macOS, Windows, Homebrew, IPA, APK, DMG, PKG, APPX, MSIX, AAB

---

**TL;DR:** This guide lists Applivery build processing error codes and provides solutions for common issues across different platforms.

When a Build is uploaded to Applivery, it goes through an automated processing pipeline that validates and extracts metadata from the file. If processing fails, one of the error codes below will be returned.

This reference lists all possible error codes, what they mean, and what to do to resolve them. Codes are grouped by platform to make it easier to find what you are looking for.

* * *

## iOS

| Code | Description | Resolution |
| --- | --- | --- |
| `IOS_INVALID_PACKAGE` | The package inside the `.ipa` file is not valid. | Make sure the App has been built and signed correctly, and that the `.app` bundle inside the `.ipa` is not corrupted. |
| `EMBEDDED_MOBILEPROVISION_NOT_FOUND` | The Embedded Mobile Provisioning Profile is missing, and the Build cannot be processed. | Make sure the App contains a valid Provisioning Profile file embedded in the `.ipa`. |
| `PAYLOAD_NOT_FOUND` | The `Payload` directory was not found inside the `.ipa`. | Verify that the `.ipa` contains a valid `Payload` directory with the `.app` bundle inside it. |

* * *

## Android

| Code | Description | Resolution |
| --- | --- | --- |
| `ANDROID_MANIFEST_NOT_FOUND` | The `AndroidManifest.xml` file is missing, and the Build cannot be processed. | Make sure the App contains a valid `AndroidManifest.xml` file. |
| `ANDROID_FAILED_PARSE_BINARY_ANDROID_MANIFEST` | The Android Manifest XML is invalid or not in binary format. | The APK contains a non-binary XML manifest that cannot be parsed. Check the Build process to ensure the APK has been compiled correctly. |
| `ANDROID_AAB_CONFIGURATION_NOT_FOUND` | The Android App Bundle (AAB) configuration is missing or invalid. | Go to **App > Settings > Android App Bundle** and review or add a valid AAB configuration. |
| `ANDROID_AAB_NO_KEY_FOUND_FOR_ALIAS_IN_KEYSTORE` | The signing key alias was not found in the provided Keystore. | Configure the correct AAB signing key under your project's **Android App Bundle Settings**. |
| `ANDROID_AAB_INCORRECT_KEYSTORE_PASSWORD` | The Keystore password provided is incorrect. | Verify that the Keystore password configured in your **Android App Bundle Settings** is correct. |
| `ANDROID_AAB_INCORRECT_KEY_PASSWORD` | The signing key password provided is incorrect. | Verify that the signing key password configured in your **Android App Bundle Settings** is correct. |

* * *

## macOS

| Code | Description | Resolution |
| --- | --- | --- |
| `PKG_ARCHIVE_OPEN_FAILED` | The package inside the `.pkg` file is not valid. | Make sure the App has been built and signed correctly, and that the `.pkg` package is not corrupted. |
| `NO_BUILD_INSIDE_DMG` | The `.dmg` file does not contain a valid build. | Make sure the `.dmg` contains a valid `.app` or `.pkg` file for processing. |

* * *

## Windows

| Code | Description | Resolution |
| --- | --- | --- |
| `APPX_BUNDLE_MANIFEST_NOT_FOUND` | The `AppxBundleManifest.xml` file is missing from the `.appxbundle` or `.msixbundle` package. | Make sure your App package contains a valid `AppxBundleManifest.xml` file. |
| `APPX_MANIFEST_NOT_FOUND` | The `AppxManifest.xml` file is missing from the `.appx` or `.msix` package. | Make sure your App package contains a valid `AppxManifest.xml` file. |

* * *

## Homebrew

| Code | Description | Resolution |
| --- | --- | --- |
| `ERROR_ARTIFACT_FROM_HOMEBREW_TOKEN` | No artifact was found using the provided Homebrew token. | Make sure your App is publicly available on Homebrew, and the token is correct. |

* * *

## General / File Errors

These codes are not specific to a single platform and can appear with any file type.

| Code | Description | Resolution |
| --- | --- | --- |
| `UNSUPPORTED_FORMAT` | The uploaded file format is not supported for processing. | Check the supported file formats and re-upload in a compatible format. |
| `BUILD_TYPE_NOT_FOUND` | No processable file was found inside the uploaded package. | Ensure the uploaded file contains a supported build artifact. |
| `NO_VALID_FILE_FOUND_FOR_PROCESSING` | No file with a supported extension was found inside the package. | Ensure the file contains one of the following extensions: `.pkg`, `.app`, `.exe`, `.msi`, `.appxbundle`, or `.msixbundle`. |
| `NO_FILES_EXTRACTED_FROM_COMPRESSED_FILE` | The `.zip` file contains no processable files. | Make sure the `.zip` contains a valid build file and is not empty or corrupted. |
| `{FILE}_CURRENTLY_ONLY_ONE_BUNDLE_SUPPORTED` | The file contains multiple items of the same type and cannot be extracted. `{FILE}` will be one of: `PKG`, `APP`, `EXE`, `MSI`, `APPXBUNDLE`, `MSIXBUNDLE`. | Ensure the uploaded file contains only one item of each supported type. |
| `UPLOAD_FILE_FAILED` | An error occurred while uploading the file to Applivery. | Retry the upload. If the issue persists, contact support. |
| `COPY_FILE_FAILED` | An error occurred while copying the file during processing. | Retry the upload. If the issue persists, contact support. |

* * *

## Supported File Formats

Applivery supports the following file formats for build uploads:

| Platform | Supported formats |
| --- | --- |
| **iOS** | `.ipa`. |
| **Android** | `.apk`, `.aab`. |
| **macOS** | `.pkg`, `.app`, `.dmg`. |
| **Windows** | `.exe`, `.msi`, `.appx`, `.msix`, `.appxbundle`, `.msixbundle`. |
| **macOS (package manager)** | Homebrew token. |
| **Cross-platform** | `.zip` containing a supported format and `.tar.gz`. |