Amazon Developer

as

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

Update a Published App

To update your app or add new features, submit a new version of your app through the app submission workflow in the Developer Console. Your app retains customer ratings and download statistics across versions.

When you update an existing app, Amazon must approve the updates before your updated app goes live.

You have three options available when you want to update your app:

Manage app updates and versions

Defining an app version helps the Amazon Appstore determine which version to show your users. Versioning is critical because:

  • Other apps—including apps you publish as a suite—need to query the system for your app's version to determine compatibility and identify dependencies.
  • Services where you publish your app might also need to query your app for its version so that they can display the version to users. A publishing service might also need to check the app version to determine compatibility and establish upgrade or downgrade relationships.

The Appstore uses the version code (Fire OS) or build number (Vega OS) to protect against downgrades by preventing users from installing an app package with a lower version than the one currently installed on their device.

Update your live app's metadata

You can perform a live metadata update when you want to update only the description or other assets and don't have a new binary file to publish. You don't need to create a new upcoming version of your app for these changes, but the Appstore must approve these updates before they are published on the Appstore.

To perform a live metadata update

  1. Go to the Developer Console dashboard.
  2. In the Amazon Appstore section, click App List.
  3. Select the app you want to update.
  4. In the App Setup section, edit the descriptions, images, or other assets as needed. For details on the app submission screens, see Submit Your App to the Amazon Appstore.
  5. Use the Report a significant change section to indicate any significant changes to your app and indicate the effective date. For more details about this section, see Report a significant change.
  6. When you're done making changes, click Submit for review.
  7. In the dialog box, choose Metadata update and click Submit.

After you submit, the app goes into a review state. While the metadata update is under review, the app remains available for download on the Appstore with its existing metadata. The time it takes to complete the review process depends on the metadata changes, but it's shorter than updates that include a binary file. For example, updates that require manual verification or content policy review are likely to take longer than those that don't.

You can check the status of your app from the Release Tracks screen. While Amazon reviews the app, the status is "In review". If you have a Fire OS and Vega OS release track, the status will be "In review" for both tracks. When the app is live, the status is "Live on Appstore".

Update your app's binary file

If you want to update your app's binary file, you must submit a binary file with a higher version number to Amazon.

To publish a new version of your app

  1. If uploading an Android app file (AAB or APK), first build your new binary file, giving it a new versionCode in the app's Gradle build file.

    If uploading a VPKG file, give it a new build number. For instructions, see Version your app in the Vega OS developer documentation.

  2. Sign in to your developer account and go to the Developer Console dashboard.
  3. In the Amazon Appstore section, click App List.
  4. Select the app you want to update and then select Release Tracks in the sidebar.
  5. Click Add upcoming version on the live app version that you want to update. You can use the upcoming version feature both for updating existing binary files and for adding additional binary files.
  6. Upload your binary file. You have two options for updating your existing binary:

    • Replace your previous binary file: To replace your existing binary with a new file that supports the same devices, click Replace on the uploaded file. Replacing your binary file allows you to retain all your previous Supported devices settings as before. For example, if you already selected which devices your binary file supports, and your new binary supports all the same devices, choose this replace option rather than reconfiguring your device support selections.
    • Delete your previous binary file: To delete your binary file and all previous device support selections, click Delete on the uploaded file. Then upload a new binary and configure the device support selections. To change the devices your app supports, click Edit supported devices in the Supported devices section.

    For apps with multiple binary files:

    • For each release track, you can upload multiple binary files to target different devices. For example, on the Fire OS track, you can upload multiple APKs and AABs, and on the Vega OS track, you can upload multiple VPKGs. To have different binaries support different devices, you must first clear any devices from the first binary that you want the second binary to support. After you clear the devices from the first binary, these devices become selectable options in the second binary. For more detailed instructions, see Device support for multiple binaries. For additional details on Fire OS, see Multiple APKs for the same application listing. Adding a new binary file to support additional devices doesn't push an app update for customers already using the app on previously supported devices.
    • If you have an existing APK or AAB binary file that supports Fire OS devices and want to add support for Vega OS devices, you must have a VPKG binary file. Create a Vega OS release track, upload your VPKG, and then choose Vega OS devices in the Supported devices section. For details, see Create a release.
    • If you have an existing live Vega OS release and no Fire OS release, to add Fire OS support, you must choose Add upcoming version on the single available track, and then upload and submit your Fire OS binary.
  7. In the Release notes field, describe the changes you've made in this release. A set of release notes is required for each translation defined for your app.

    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.

  8. When you've completed all required fields, click Submit for review.
  9. If you're performing a staged rollout for this release, select the initial rollout percentage, otherwise, select 100% Full release, and then click Release to All Users.
  10. If you also need to make changes to your app's metadata with this update, follow steps 1–2 in Update your app's metadata and binary file.

Update your app's metadata and binary file

For your Fire OS release, if have a new version of your app's binary file and also want to update the app's descriptions and assets, you'll use a combination of the steps from the previous sections.

To update your app's metadata and binary file

  1. Follow steps 1–5 in Update your live app's metadata.
  2. After you click Review and submit, choose App release update in the dialog box and then click Submit.
  3. Select Release Tracks from the sidebar and click Add upcoming version on your Fire OS release.
  4. Follow steps 6–9 in Update your app's binary file.

How and when app updates happen for customers on Fire TV

For updates that do not have permission changes, Fire TV applies the update in the background. For apps that do have permission changes, the customer has to manually review the permission changes and apply the update. With apps that have permissions changes, the update process differs between Fire OS 5 devices and devices running Fire OS 6 and higher.

  • Updates for Fire OS 6 and higher devices

    On Fire OS 6 devices, permission approvals are applied at runtime (rather than at installation time), so customers don't have to manually approve the permission changes before the update is applied. Instead, the update gets applied in the background; when customers launch the app, they're prompted to approve the new permissions. In short, with Fire OS 6, any update can be installed, but access to the feature is deferred to runtime. (This assumes the app supports Marshmallow or later APIs, as this is when runtime permissions were introduced on Android.)

  • Updates for Fire OS 5 devices

    Apps with API levels lower than Marshmallow (less than Level 23) require customers to manually approve the updates before the updates can be applied. For these updates, Fire TV sends an actionable heads-up notification every 24 hours letting customers know about pending approvals for updates. These notifications also stay in the Notification Center and take customers to a screen that shows all the pending updates.

    When customers launch an app that has a manual update pending, Fire TV shows a message that asks if customers want to update the app first before launching it. If customers decline, Fire TV does not prompt customers to update the app on subsequent launches for another seven days.

    If customers go to the app details page, an update button appears for apps that have a pending update.

Force update guidelines

A force update is a mandatory app update where your users must update to the latest version of your app to continue using it.

You might have a scenario where you want to use a force update in your app, such as:

  • To fix a critical security vulnerability
  • To fix a critical bug
  • To make sure users are not using an outdated version of your app and can access the latest features and improvements

You can configure a force update on your server so that when a user launches your app they are prompted to update before they can use the app. However, there are some cases where a force update might not work well. To prevent a poor customer experience during an app update, use the following guidelines:

  • If you're releasing your app in a staged rollout, configure the force update only after releasing the app to 100% of your users.
  • If you're releasing your app on a future date, set the force update to start on a date after the configured future release date.
  • If the update reduces the targeted devices or reduces region availability, configure the force update so that it doesn't unintentionally abandon current users.
  • Wait at least 24 hours after your app update is live before configuring a force update.
  • If you have multiple release tracks, configure the force update only for the devices on the release track that you're updating.

Last updated: Nov 16, 2026