Updating a Published App

If you update your app with new features, you can simply update your existing, published app in the Amazon Appstore rather than creating a new one. By updating your existing app (rather than creating a new one), you retain your app's customer ratings and download statistics across versions. You also enable your customers to receive app updates.

Update an Existing App

When you update an existing app, your updates will need to be approved before your updated app goes live. If you're making updates to descriptions or assets only, the submission process turnaround time is shorter than updates that involve app files. To update your app:

  1. If your app includes an Android APK, first build your new APK, giving it a new versionCode in the app's Gradle build file.

  2. Sign in to the Developer Portal.
  3. From the Dashboard (the default homepage), under the Amazon Appstore section, click App List.

    Amazon Appstore section in Dashboard
  4. Click the app you want to update.
  5. Near the top of the page, in the area below the name of your app, click Add Upcoming Version. A confirmation message appears — click OK to proceed. (You use the Upcoming Version feature both for updating existing APKs and for adding new APKs.)

    The portal creates a new set of tabs for you. The General InformationAvailability & PricingDescriptionImages & Multimedia, Content Rating, and APK Files tabs are shown with green checkmarks to indicate that the required fields have been pre-filled with the information associated with the live version your app. This information is simply copied from your live app.

  6. On the Description tab, a Release Notes field appears where you can describe the changes you've made in this release. Click Edit and add your release notes. Note that a set of release notes is required for each translation defined for your app.
  7. As desired, edit the information on the tabs. For details with each tab, see the documentation for Submitting Apps to the Amazon Appstore.
  8. Android apps have an APK Files tab instead of an App Files tab. For APK files, you have two options for updating your existing APK:

    • Replace your previous APK: To replace your existing APK with a new file that supports the same devices, in the APK files section, click Replace. Replacing your APK allows you to retain all your previous Device Support settings as before. For example, if you already selected which devices your APK supports, and your new APK supports all the same devices, choose this replace option rather than reconfiguring your device support selections.
    • Delete your previous APK: To delete your APK and all previous device support selections, click the Remove Delete APK File button button next to your previous APK. Then upload a new APK and configure the Device Support selections from scratch. To change the devices your APK supports, click Edit next to "Supported Devices" in the APK File section and update the supported devices.

    For apps with multiple APKs: Suppose you have multiple APKs for your app. If you want different APKs to support different devices, you must first clear any devices from the first APK that you want the second APK to support. After you clear the devices from the first APK, these devices become selectable options in the second APK. More detail is provided in Add Multiple APKs for the Same App (in Step 7: Upload APK Files). See also Multiple APKs for the Same Application Listing. Note that when you add APKs for new devices, customers using the app on previously supported devices will not receive an app update.

    Web apps: For web apps, you will see an App Files tab rather than an APK Files tab. On the App Files tab, update your web app files as desired.

    When you're finished making updates on every tab, as long as the information is complete, green check marks appear on the tabs. When all tabs for your app have green check marks, the Submit App button is enabled. You can change the information on any tab until you submit your app.

  9. Click Submit App.

How and When App Updates Happen for Customers (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 6 and Fire OS 5 devices:

  • Updates for Fire OS 6 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.