Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Devices
Build
Test
Publish
Connect
Documentation

Step 5: Add Release Details

On the Release Tracks screen, you can view the currently submitted releases for your app and track the status. When you create a release, you can manage your app's binary file, target which devices you want your app to be available on, and schedule the release date. You can choose to release your app on Fire OS devices, Vega OS devices, or both. Appstore provides separate release tracks for Fire OS and Vega OS, therefore you manage the binary files and publish dates separately.

Release Tracks screen with a track for Fire OS and a track for Vega OS.

Create a release

If your app has no releases yet, the Release Tracks screen shows a single card where you can create a release. You can create a release for either Fire OS, Vega OS, or both. To get started, choose Create a release and then complete all required input fields. The following sections describe each input field.

App files

This section describes how to upload your app file and add supported devices. Here, you can upload a Fire OS binary, a Vega OS binary, or both.

Upload your app file

To upload your app file for Fire OS, drag an Android App Bundle (AAB) or an APK file to the box, or click the box and choose your file. For a Vega OS, upload a VPKG file. If you plan to submit an APK and you didn't use Android Studio to build your signed APK, you might need to zipalign your file.

You can upload multiple binary files by dropping one file at a time into the box. When you add a binary file, you can see its details by clicking Manifest. The version code or build number, version name, file size, package name, minimum SDK version, features, libraries, permissions, localizations, supported screens, compatible screens, OpenGL details, and native platforms are shown. These details determine which devices are supported by your binary file. For details on filtering on Fire OS, see Device Filtering and Compatibility on Fire OS.

After you upload a binary, the file receives an alias, for example, "APK1" or "VPKG1". You can rename the alias as desired. The custom alias is used internally and not seen by customers. For more details related to binary files, see Preparing your binary file.

Update an existing app

If you're updating an existing app, see Update a Published App. When you make the update, you have the option of replacing the existing binary file and retaining the same device support selections, or removing the previous binary file and re-selecting your device support details.

If you have an existing release for one OS and want to create a release for the other OS, follow the guidance in View release tracks and manage OS support.

Add multiple binary files for the same app

The Amazon Appstore supports uploading multiple binary files to the same app listing. You might use this feature for the following:

  • To support differences in Fire OS devices. For example, uploading one APK for Fire TVs and another APK for Fire tablets.
    For more conceptual details about uploading multiple APKs, see Multiple APKs for the same application listing.

  • To target devices with different OSes. For example, uploading an APK binary for Fire OS devices and a VPKG binary for Vega OS devices. If you're supporting both Fire OS and Vega OS devices, you upload and manage the binary files separately through releases tracks after the initial release.
    For more information about supporting both Fire OS and Vega OS devices under the same app listing, see Release tracks for Fire OS and Vega OS.

When uploading multiple binary files, make sure each file has the same package name in the manifest; however, each individual binary should have a unique versionCode for Fire OS or build number for Vega OS.

To upload multiple binary files to the same release track

  1. If you haven't already uploaded your first binary file, upload it by dragging the file into the Upload your app file box.
  2. Optionally give your binary a recognizable alias to distinguish it from the next file you upload. For APKs, the default alias for the first file is "APK1" and for VPKGs, "VPKG1".
  3. Drag another binary file into the Upload your app file box. Optionally, change the alias for the new file you upload to distinguish it from the first file.

You can add a maximum of 15 files.

Upload app bundles

For a Fire OS app, you can submit Android App Bundle  files to the Amazon Appstore, without the need to create separate APKs. The Appstore uses bundletool (version 1.11) to convert the app bundle files into optimized APKs that can be downloaded and installed across client devices. The size of the APK file that a customer installs is optimized for their device configuration.

For details on how to create, test, and submit app bundles, see App Bundles.

Appstore certificate hashes

At the top of the App files section, you can view your Appstore certificate hashes. Certificate information includes the SHA-1, MD5, and SHA-256 hashes. As part of the ingestion process, Amazon removes your developer signature and applies an Amazon signature. This signature is unique to you, does not change, and is the same for all apps in your account. For more details, see Amazon App Signatures.

Apply Amazon DRM?

This is a conditional field on the Fire OS track that appears only if your app isn't using the Appstore SDK. If your app uses the Appstore SDK, you won't see this option. To add DRM with the Appstore SDK, use the DRM API included in the SDK. For more information, see DRM Overview.

DRM (digital rights management) protects your app from unauthorized use. Without DRM, your app can be used without restrictions by any user.

If your app isn't using the Appstore SDK, Amazon can automatically add DRM functionality to your app. Select Yes to allow Amazon to add DRM to your app. Select No if you do not want Amazon to add DRM to your app.

If you have multiple binary files, select a DRM setting for each binary. If you have previously uploaded binary files and are adding a new binary with different DRM settings, you must replace the previous binary files if you want them to receive the updated DRM settings. Otherwise, your previous binary files retain the same DRM settings as before. For more information about automatically-applied Amazon DRM, see About DRM.

Troubleshoot common errors

This section provides troubleshooting information related to binary file submissions.

Error: Duplicate package name

When uploading a binary file, you see one of the following errors:

Failed to upload APK. The package name of the uploaded APK, com.amazon.android.yourapp, is already in use by an app owned by a different developer. Please contact us for more information.

Failed to upload App Bundle. The package name of the uploaded bundle, com.amazon.android.yourapp, is already in use by an app owned by a different developer. Please contact us for more information.

Failed to upload VPKG. The package name of the uploaded VPKG, com.amazon.yourapp, is already in use by an app owned by a different developer. Please contact us for more information.

First, check to make sure that you have not uploaded this binary file on another Amazon developer account as either an app submission or Live App Test. If you haven't uploaded this same file under another account, submit a support case reporting the issue and noting the package name. To submit a support case, sign in to the Developer Console, click the ? in the upper-right corner, and click Contact Us.

When using development environments such as Unity, or with pre-existing manifest files, it's possible that your app's package name will have a placeholder value that should be changed prior to submission. The package name of your binary file must be unique to the app you are publishing and is usually in the format of com.companyname.appname.

If you have an association with a developer or publishing company that might have uploaded your app for Live App Testing (LAT) contact your development partner to confirm that they have not submitted your binary file on their account. If they have, ask them to end the current live app test. Then contact Amazon with the package name to resolve the issue. For more information on LAT, see Get Started with Live App Testing for Fire OS and Get Started with Live App Testing for Vega for Vega OS.

App bundle-specific errors

When uploading an app bundle file for your Fire OS app, you might see a message that the app bundle failed to upload. Use the following troubleshooting instructions to help resolve these issues.

Error message:

Failed to upload App Bundle. The submitted bundle file is invalid. Please upload a valid bundle.

If you see this message, the Developer Console was unable to parse the Android App Bundle file successfully. The bundle might be malformed. Before you upload, use the validate command of bundletool to verify that the AAB file is correctly formed. Here is a usage example of the command:

bundletool validate --bundle=/path/to/bundle.aab

Error message:

Failed to upload App Bundle. Verify the bundle contains only install-time asset packs and try again.

The Developer Console can't parse Android App Bundle files that have asset packs that aren't install-time. If you see this message, verify that your app contains only install-time asset packs. If your app contains asset packs that aren't install-time, convert them to install-time asset packs before you upload.

Release notes

This field appears only if you are submitting a new version of an existing app. Describe the changes you've made in this update. On your app's Appstore details page, release notes appear in the Latest updates section. On Fire TV devices, users (who have installed the app) see the release notes in the Notifications section in settings. On Fire tablets, users see the updates in the notifications pull-down menu at the top.

If you previously published an updated version of your app and entered release notes, an option to Copy release notes from the previous app version for all languages will be available to you. Select this option to populate the field with the release notes from the previous version of your app.

Supported devices

After you upload your app file, the number of supported devices appears in this section. Only the devices that are valid targets of the chosen track and supported by your manifest are selectable. For more information on how attributes in your manifest determine the devices your Fire OS binary supports, see Device Filtering and Compatibility.

Edit supported devices

To manage the specific devices your app file supports, select Edit supported devices. For the Fire OS release track, you can also create rules based on specific parameters to determine supported devices. For details on the rules-based method, see Create and manage rules.

When you click Edit supported devices, the Supported devices overlay opens. Devices that you can't select are unsupported. Unsupported devices are determined by the chosen release track, attributes in your manifest, and the countries you target in the Availability section.

In the Vega OS release track, you can target Vega OS devices by selecting the Amazon Fire TV tab. Then, in the Amazon Vega TV section, select the checkbox for the device you want to target.

If you see an unsupported device, you can find out why by moving your mouse over the help icon next to the device's name, as shown in the following image.

The Supported devices screen with a mouse pointer over the help icon of a device. The mouse-over message says 'Your APK manifest requires capabilities not present on this device'.

The supported devices are grouped into the following categories:

  • Amazon Fire Tablets: Shows Fire tablet support for your app. For more details about Fire tablets, see Fire Tablet Device Specifications.
  • Amazon Fire TV: Shows Fire TV support for your app. For details on Fire TV device names and specifications, see Fire TV Device Specifications.
  • Amazon Automotive: Shows Amazon Automotive support for your app.

If necessary, you can manually remove support for devices that have known compatibility issues. Use the tabs at the top of the overlay to move between categories.

For additional information about supported devices for your app, see the following:

Create and manage rules

In the Fire OS track, another method to target devices is to use rules. Rules apply filtering that is based on device specifications, which includes CPU architecture, device type, and device RAM. Appstore applies rules-based device filtering on top of the requirements set in your app's manifest file.

Consider a scenario where you are submitting a gaming app that requires significant memory resources. To make sure your app can't be installed on a device that would provide a suboptimal performance, you can set a rule to target devices with greater than 1 GB RAM.

Keep in mind the following points when you set up your rules:

  • Rules you configure are applied on top of the device compatibility determined by your app's manifest file.
  • Rules-based filtering applies to new devices added to the Appstore catalog that meet the filtering criteria.
  • Setting a rule determines which devices are available when you select Edit supported devices. If a rule you create makes a device incompatible, you will be unable to select that device.

To set up device filtering rules

  1. Select your app from the App List screen in the Developer Console.
  2. If needed, create an upcoming version of your app and upload your app files.
  3. In the Supported devices section, click Manage rules to configure rules for the associated binary, as shown in the following image.
    'Manage rules' is clickable text next to 'Supported devices'.
  4. Click Add rule. Rules consist of a variable, an operator, and a value. Use the available dropdowns to create a rule.
    Manage rules overlay. When you add a rule, you can select a variable, an operator, and a value.
    1. Select a variable from the first dropdown.
    2. Select an operator from the second dropdown.
    3. Select a value from the third dropdown.

    The following table lists the available variables and their associated operators and values.

    Variables to manage rules
    Variable Associated operators Associated values
    RAM Greater than equals to 1GB, 1.5GB, 2GB
    Device type Excludes Fire Tablet, Fire TV, Amazon Automotive
    CPU architecture Excludes 32-bit, 64-bit
  5. To add another rule, click Add another rule.
  6. When finished adding rules, click Save.
  7. Click Edit supported devices to review the device list and make sure the supported devices are expected. If you need to modify the device list, return to the Manage Rules screen and make any necessary updates.

Devices supporting only 64-bit apps

Some devices no longer support 32-bit apps, including any 32-bit apps currently available on Amazon Appstore. Customers attempting to download a 32-bit app on one of these devices will receive a notification alerting them that the app is not compatible with system requirements.

To make your app available to customers using one of these devices, add 64-bit (arm64-v8a) support to your app and submit an update using the Amazon Developer Console. Do not remove support for 32-bit (armeabi-v7a) while building your app, as it may impact current Amazon device selection.

Device support for multiple binaries

If you are submitting multiple binary files to the same release track, you must choose the devices supported by each binary. After you upload your first binary, the Developer Console automatically filters the devices based on your manifest. When you upload an additional binary, you must manually select the devices you want to be supported.

When your app is available on the Appstore, each device has one app binary associated with it. During app submission, when you add multiple binary files, you have to remove support for devices from your first binary that you want to be available for the additional binary files. The following instructions and screenshots clarify this selection process.

To configure support for multiple binary files:

Edit supported devices for the first binary

Click Edit supported devices and remove support for devices you plan to target with your other binary files.

For example, suppose you have two APKs for your Fire TV app named "APK1" and "APK2". With APK1, you plan to target all Fire TV devices except Fire TV (Gen 3). To do this, click Edit supported devices for APK1. In the Supported devices overlay that appears, clear the checkbox next to Fire TV (Gen 3). This makes Fire TV (Gen 3) available for APK2 to target. If you don't remove the device support from the first APK, you won't be able to target it with the second APK.

All Fire TV devices have their checkboxes marked, except for Fire TV (Gen 3)
In this scenario, remove support for Fire TV (Gen 3) to make it available for the second APK
Edit supported devices for the second binary

Click Edit supported devices on the next binary. Because two binary files for the same app can't be installed on the same device, the devices supported by the first binary are unable to be selected. If you hover over the help icon for those devices, the message "Targeted by another App file in the current version" appears. Targeted means that you selected support for the device with your app. With the second binary file, you can select support for devices not already selected by the first binary.

Continuing with the example, suppose you upload "APK2" and plan to target the Fire TV (Gen 3) with this APK. You already cleared support for this device with APK1, so it will be selectable with this second APK.

All Fire TV devices are unable to be selected, except for Fire TV (Gen 3), which has its checkbox marked
Fire TV (Gen 3) can be selected because you didn't already select support for it with the previous APK. The other devices are unavailable to be supported by this APK because they are already supported by the previous APK.

With multiple binary files, the Amazon Appstore does not automatically assign the binary based on the API level or versionCode(unlike with Google Play). You must manually select the supported devices when uploading multiple binary files.

When finished, click Save.

Conditional fields

During the app submission process, some fields only appear under certain conditions. Here, learn about those fields contained in the Supported devices section, and the conditions under which they appear.

Does your app have touch capabilities?

This field appears if you target Amazon Automotive devices. Indicate if your app is touch enabled.

Does your app support offline consumption of the app content?

This field appears if you target Amazon Automotive devices. Indicate if your app works offline, or if it allows users to download content, such as videos or games, to use offline.

Troubleshoot common errors

This section provides troubleshooting information related to Android binary file submissions.

Warning: Reduced device support

When adjusting device support for a binary file, you see a warning that says the following:

Device support has been reduced from the previous version. Some existing customers will not be able to upgrade. To resolve manifest conflicts, Amazon recommends editing the manifest to retain your current device support.

This message means that, with your newly uploaded binary file, you have introduced new attributes in your manifest or build.gradle file that shrink the number of compatible devices. Most commonly, you might have incremented the API level, which reduces the number of devices that can support the update. As such, the Appstore is warning you that some devices might not be able to install this update.

For example, suppose you publish an APK with manifest attributes that require at minimum API level 19, and customers with a device supporting API level 19 (but not support for any level greater) install the app. Later, you update the app with new features or permissions requiring APK level 22 as a minimum. This new update will be incompatible with the previous version of the app the customer (with API level 19) installed. As a result, the customer will not see that an update is available.

Target device not available

When uploading a new binary file, you see a message that says a particular device is not supported. These messages can occur for multiple reasons. The following are a few examples you might encounter.

Your App Bundle manifest requires capabilities not present on this device.
android:minSdkVersion = '22'; device supports '15'

Your APK manifest requires capabilities not present on this device.
android:minSdkVersion = '22'; device supports '15'

Device is not available for the selected region.
To enable this device, update your region selection.

Your binary is incompatible with this device due to different device OS.

To see the reason the device isn't supported, move your mouse over the help icon next to the device name in the Supported devices overlay. For more details, see Supported devices. The incompatibility could be due to the API level, OpenGL compression format, CPU, screen size and density, device features, or other factors about your app such as lack of availability in the geographic locale.

Targeted by another app file in the current version

If you're uploading multiple binaries, the device might already be supported by another binary file. If so, when you move your mouse over the unsupported device, it says:

Targeted by another App file in the current version.

Multiple binaries cannot support the same device. You must edit the device support for one binary file so that you can select support for the device with the other binary. For step-by-step details, see Device support for multiple binaries. For a more conceptual background, see Multiple APKs for the same application listing.

Release date

Specify the time and date when you would like your app to be available in the Amazon Appstore. Leaving this field blank (the default) enables Amazon to make your app available as soon as it passes Amazon's testing. Your app will be available in the Appstore a few hours after the time you select. The time you select is when the publishing process starts. The publishing process can take a few hours before your app is live and available to customers.

If you need to change the publishing date or time after your app is submitted, update this field. The date you set can be sooner than your original date, or further in the future. If the date originally entered has passed, the field will not be editable.

Testing instructions

Use this field to communicate with the Amazon testing team. If no testing instructions are needed, leave this field blank. Testing instructions might include the following.

  • If your app has difficult-to-discover features, include directions here for finding those features. Also, if you need to resubmit your app based on feedback from Amazon, you can use this field to respond to the test report emails.
  • If your app requires users to log in before launching and using the app, include a set of test credentials for the Amazon test team to use. If Amazon cannot successfully launch your app during testing, the app will be rejected.

Export compliance

This field asks you to certify that your app is compliant in all countries in which you've chosen to make it available. You can read more details in the "Compliance with Laws; Privacy and Security Obligations" section in the Amazon Developer Services Agreement.

Additional information

This section describes the Additional information fields.

App ID and Release ID

An app ID uniquely identifies your app and a release ID uniquely identifies a version of your app. These are generated after you create an app through the Developer Console. The app ID allows you to manage your app information programmatically through the App Submission API.

Public key and PEM file

A public key, which is unique per app, establishes a secure communication channel between the Amazon Appstore and your app. When you generate the public key from the Developer Console, Amazon generates a corresponding private key. These public and private keys form a key pair to sign license responses. Through this key pairing, you ensure that the users who install your app are authorized.

The public key is stored in a PEM file. If your app uses the Appstore SDK or the Appstore SDK plugin for Unity for In-App Purchasing (IAP) or DRM, you must add the PEM file to your project. To configure your app with the public key:

  1. Click View public key.
  2. In the Public Key dialog box that appears, click the AppstoreAuthenticationKey.pem link to download the PEM file.

    The Public Key window showing a public key string. A download icon followed by the link text 'AppstoreAuthenticationKey.pem' is shown.
    PEM file download link
  3. Copy the AppstoreAuthenticationKey.pem file.
  4. Follow the instructions for your project type.

    Android project instructions

    1. Paste the PEM file into the app/src/main/assets folder of your Android Studio project.
    2. In project view, the assets folder is usually in app/src/main/assets. If your app doesn't have an assets folder, you must create one. Then drag your PEM file into it.

    Unity project instructions

    1. In the Assets folder of your project, create a new folder named StreamingAssets.
    2. Paste the PEM file in your Assets/StreamingAssets folder.

For more details, see Configure Appstore SDK with your public key or Configure Unity App with Public Key.

Submit your app

Complete the app submission process by clicking Submit for review.

After you submit an app to the Amazon Appstore, the Appstore routes the app through its approval process before it's published and available for download. You can track the status of your app submission by clicking App Status on the Release Tracks screen. The following sections provide an overview of the approval process and describe the possible submission statuses for an app that has been submitted.

View release tracks and manage OS support

What you see on the Release Tracks screen and how you manage OS support depend on which releases are currently live.

Currently live release What the Release Tracks screen shows How to add OS support
Both Fire OS and Vega OS Two separate tracks: one for Fire OS and one for Vega OS, each displaying their release status.

You see this if you submitted both a Fire OS and a Vega OS binary with your initial release, or if you added the support for the other OS later.
Not applicable, your app supports both Fire OS and Vega OS.
Fire OS only Two separate tracks: a Fire OS track with its release status, and a Vega OS track with no release. To add Vega OS support, choose Create a release on the Vega OS track. Then, upload your VPKG and complete the fields as described in Create a release.
Vega OS only A single track with its release status. To add Fire OS support, choose Add upcoming version. Then, upload your Fire OS binary and submit your app for review. For complete instructions, see Update your app's binary file.

After your Fire OS binary goes live, the Release Tracks screen show two separate tracks, one for each OS, which displays their individual release status.
No live release Before submission: a single track with the option to create a release.

After submission but before publishing: a single track with the current submission status.
Wait for publishing to complete, then follow the guidance in this table based on the release state.

Overview of the app approval process

Before approving an app and making it live on the Amazon Appstore, Amazon verifies your app does the following.

The following flowchart shows the app approval process:

App approval workflow; text description is available in the expandable button.
Click to enlarge image.

After approving your app, Amazon sends an email to the Amazon developer account owner. This email address might not be the same as the address you use to log in to the Developer Console. For more information about which email address is used, see Receiving communications. If after waiting for six days your app is still in review, you can optionally use the Contact Us form to seek clarification.

App submission status reference

The Amazon Developer Console displays the status of every app that you submit to Amazon. The status messages on the Release Tracks screen have the following meanings.

Review status descriptions
Status Description
In progress You have not yet completed your app submission. The app might be missing fields required for submission to Amazon.
Submitted You have submitted the app for review, and it can no longer be edited. At this time, you can cancel the request for review and continue to edit your app by clicking the Cancel Release link.
In review Amazon is reviewing the app. If you wish, you can choose to cancel the release and re-start the submission process.
Approved The app has completed at least one stage of the testing and content review process and may soon be ready for publication. No changes can be made to the app while in this status. You must wait until the app is live before making changes.
Live rollout The app version is in a staged rollout and live only for the percentage of users that you configured. The remaining percentage of users have the previously live version.
Live on Appstore The app is now live on the store.
Pending action You will receive an email from our team explaining why the review process for your app was paused and asking you to perform some action. You must address the relevant metadata or binary issues before your app can successfully continue through the process.
Rejected The app did not pass the review process. You will receive an email from Amazon explaining the reasons for the failed approval.
Suppressed The app was live at one point but is no longer in the store.

FAQ for submission status and app approval

Q: How can I ensure that the app I submit will be approved for the Amazon Appstore?
Amazon wants to ensure that apps listed in the Amazon Appstore meet certain quality requirements and tests all submitted apps to verify that they meet the following standards:
  • All apps work as outlined in their product description.
  • Apps do not impair the functionality of the Fire device.
  • Apps do not put customer data at risk once installed
  • All apps comply with the terms of the Amazon Developer Services Agreement and Amazon's Content Guidelines.
Q: Will Amazon tell me when my app is approved or if it fails testing?
Yes. You can track the approval status of your app by signing in to the Developer Console and finding your app in the Dashboard on the home page. Amazon will also send you an email when the submission status of your app changes under the following circumstances:
  • Your app has been accepted into the Amazon Appstore and will be made available on the date you specified in the console.
  • Amazon requires more information to complete the testing process. (Your app submission might be missing a critical asset or a critical asset might not meet Amazon's specifications.) Amazon will provide you with details on the information or assets needed to resume testing.
  • Your app has failed Amazon's testing process. Amazon will provide you with details on the failure and guidance on resubmission.
Q: What are the status codes for apps that have been submitted to the Amazon Appstore?
For a list of app status codes and their descriptions, see App submission status reference.
Q: There is a review of my app that I feel is inappropriate. How can I resolve this?
Click the Report abuse link below the review. The information you submit will be reviewed by Amazon, and we will take appropriate action.
Q: Why didn't my launcher, widget, or lock screen app go live for Amazon devices?
Amazon seeks to preserve a consistent customer experience on Amazon devices. If your app overrides the native user experience, it will not be published on Amazon devices.
Q: Are there any specific restrictions that apply to keyboard apps?
Yes. Keyboard apps must function whether or not a customer's device is connected to the internet. Any tracking of user activity (including keystroke logging) through a keyboard app must be clearly disclosed to customers and may be used only to provide or improve the app's keyboard functionality (and not, for example, for advertising purposes).

Last updated: Nov 16, 2026