Uploading a Signed Apk to the App Store

Step seven: Upload App Files (APK Files)

The documentation here relates to the APK Files tab:

APK Files tab

On the APK Files tab, you lot upload your APK files, bespeak which devices your APKs support, and more. For more conceptual topics related to APKs, see the following:

• Preparing the APK File for Your App: Provides data near preparing your APK and the code wrapper that Amazon uses with your APK, every bit well as APK size limitations and other details.
• Device Filtering and Compatibility: Explains how attributes in your manifest decide the devices your APK supports.

(If you're uploading a web app, see Upload Web App Files instead of this topic.)

• APK Files Fields
• Public Key and PEM File
• Appstore Certificate Hashes
• Update an Existing APK
• Suit Device Support for Your APK
• Add Multiple APKs for the Same App
• Troubleshooting Common Errors
  • Error: Indistinguishable package proper name
  • Warning: Reduced device back up
  • Target device non bachelor
  • Targeted by another binary in the electric current version
• Adjacent Steps

APK Files Fields

The following table describes each field and section on the APK Files tab.

APK Files tab fields

Field	Description
Utilise Amazon DRM?	For each app that you submit to Amazon (a single app might contain multiple APKs), you tin can choose either to apply DRM or make your app available without any rights management constraints. DRM (digital rights management) protects your app from unauthorized employ. The DRM setting applies to all of your app's APKs. Without DRM, your app tin can be used without restrictions by whatever user. If you lot choose to apply DRM to i of your apps, you must use the DRM arrangement provided by Amazon through the Developer Portal. Note that the DRM setting applies to all of your app's APKs. If y'all have previous APKs uploaded and are calculation a new APK with different DRM settings than your previous APKs, you'll need to supersede the previous APKs too and so they can receive the updated DRM settings. Otherwise, your previous APKs will retain the same DRM settings as before, regardless of your pick here. See About DRM for more information.
APK File	Upload your Android APK files (drop one file at a time into the box). If didn't use Android Studio to build your signed APK, you might need to zipalign your file. When you add an APK file, you lot tin come across its details by clicking the information icon . These details include the version code, version name, file size, package name, minimum SDK version, features, libraries, permissions, localizations, supported screens, compatible screens, OpenGL details, and native platforms. For case: These details determine what devices are supported by your APK (filtering is explained in Device Filtering and Compatibility). Afterwards you upload an APK, the APK receives an allonym named after the API level (for example, "apilevel22"). You tin can rename the alias as desired. The custom alias is used internally and non exist seen past customers. See Preparing the APK File for Your App and Updating a Published App for more details related to APK files.
Language Support	Select at least one language supported by your APK. Your option here appears in a "Supported Languages" section in the device app details page in the Appstore to permit users know which language is available in the app. (The "Supported Languages" section appears but on the device's brandish of Appstore apps, not on the Amazon Appstore website.) The Linguistic communication Support choice here doesn't influence whether your app becomes available in localized Appstore marketplaces. Whatever localization interfaces in your APK must exist handled by your APK itself, not through settings in the Appstore submission process. Yet, if you practice accept a localized APK, you tin can add localized descriptions and prototype assets. The descriptions, epitome avails, and linguistic communication support option selected here all inform your app details page in the Amazon Appstore. See Distribute Your App Internationally for more details on localization.
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-detect features, include directions here for finding those features. Besides, if you demand to resubmit your app based on feedback from Amazon, you tin use this field to respond to the test report emails. If your app requires users to log in earlier launching and using the app, include a set up of test credentials for the Amazon test squad to employ. If Amazon cannot successfully launch your app during testing, the app volition exist rejected.
Export Compliance	Asks you lot 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" department in the Amazon Programmer Services Agreement
Use Amazon Maps Redirection	Allows you lot to automatically redirect Google Maps v1 API calls from your app to the Amazon Maps API. Merely used in tablet and phone apps if you lot have the Google Maps API implemented.

Public Key and PEM File

In the upper-right expanse of the tab, there is a link for a Public Key. This public key, which is unique per app, establishes a secure advice channel between the Amazon Appstore and your app. When you generate the public cardinal from the Programmer Console, Amazon generates a corresponding individual 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 primal 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 Public Key.

2. In the Public Key dialog box that appears, click the AppstoreAuthenticationKey.pem link to download the PEM file.

   

   PEM file 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/primary/assets folder of your Android Studio project.
   2. In the Project view, the assets binder is usually in app/src/primary/avails. If your app doesn't accept an assets folder, y'all must create one. Then elevate 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, run into Configure Appstore SDK with your public key or Configure Unity App with Public Key.

Appstore Certificate Hashes

Certificate information, which includes the SHA-1, MD5, and SHA-256 hashes, is available from a link in the upper-correct expanse of the tab. As part of the ingestion process, Amazon removes your developer signature and applies an Amazon signature. This signature is unique to you, does not alter, and is the aforementioned for all apps in your account. For more details, see Amazon App Signatures.

Update an Existing APK

If you're updating an existing APK, run across Updating a Published App. When y'all brand the update, yous accept the pick of replacing an existing APK and retaining the same Device Support selections, or removing the previous APK and re-selecting your Device Support details.

Adjust Device Support for Your APK

After you upload your APK, the number of supported devices appears in the Uploaded APKs section.

To manage which devices your APK supports, select Edit next to the number of supported devices. In the Device Back up overlay, devices with an 'Ten' next to their name are unsupported. Unsupported devices are determined by the attributes in your manifest and the countries you lot targeted in Stride three: Add Availability & Pricing.

To understand why a device isn't supported by your APK, move your mouse over the help icon adjacent to the device proper noun in the Device Support dialog box, as shown in the post-obit epitome.

If necessary, you can manually remove support for devices that have known compatibility issues. The supported devices are grouped into three categories:

• Amazon Fire phones and tablets: Shows the Fire phones and tablet support for your app. Encounter the Tablet Device Specifications for more details. Past default, device support for your uploaded APK is turned on for all Amazon Burn Phone and Fire tablet devices, and for all non-Amazon Android devices.

• Amazon Burn TV devices: Shows the Fire TV device support for your app. For details on Fire TV device names, see Burn down Boob tube naming conventions; for specifications, see Device Specifications for Burn Tv set.

• Non-Amazon Android devices: Shows Android devices on which your app could be installed through the Amazon Appstore for Android app. The Amazon Appstore supports non-Amazon devices running Android 5.0 and above. This option provides additional distribution avenues for your app (and is particularly helpful if your app is only available in the Amazon Appstore, not on Google Play). Within this non-Amazon Android devices grouping, devices are sorted into three groups: Supported (compatible), Excluded (manually de-selected), and Unsupported (incompatible based on your manifest settings).

To adjust which devices are supported by your app, click Edit device support and update the devices indicated. Toggle device support on (green) or off (gray) as appropriate. Use the tabs at the top of the dialog to motility between categories.

For instance, if you're uploading a streaming media app designed for Burn TV devices, click Edit device back up on the Amazon Fire TV devices row and select the advisable device support options on the Amazon Fire Tv tab:

For additional information about supported devices for your APK, run across the following:

• Troubleshooting Android Manifest and Device Filtering
• Device Filtering and Compatibility
• Supported Filters on the Amazon Appstore.

For not-Amazon devices, at the bottom of the Device Support dialog, there's an option for All other Android devices. The Non-Amazon Android devices can exist toggled on or off as a whole, or you lot tin manually adjust device support. This setting allows your app to be distributed to any other Android devices, including future compatible Android devices. New devices are added regularly based on device popularity. Through manifest filtering, the Appstore automatically determines the device'due south compatibility.

If y'all turn off "All other Android devices," you modify your compatibility strategy from using a deny listing to using an allow list for non-Amazon devices. In other words, your APK won't be compatible by default on those devices; instead, you lot'll need to manually select which tertiary-party devices your APK will back up.

To add together an additional APK for the same app, come across the next section, Add Multiple APKs for the Same App.

Add together Multiple APKs for the Same App

When uploading multiple APKs, brand certain each APK has the same bundle name in the manifest; however, each individual APK should have a unique versionCode in your Gradle build file.

When you add multiple APKs, because each APK can only be available for a unmarried device, you lot have to remove support for devices from your first APK that you want to be available for the boosted APKs. The post-obit step-past-step instructions and screenshots will analyze this choice process.

To upload multiple APKs:

1. If you haven't already uploaded your first APK, upload it by dragging the APK into the APK Files box.

2. For the get-go APK you uploaded, next to "Supported Devices," click Edit and remove support for devices that you programme to target with your second APK.

   For example, suppose you have 2 APKs for your Burn down Television app — "APK1" and "APK2". With APK1, you want to target all Burn TV devices except Fire Idiot box (iii^rd Gen). For APK1, click Edit next to "Supported Devices" in the APK File department. In the Device Support dialog box that appears, clear the checkbox side by side to "Burn down Goggle box (three^rd Gen)." This volition make Fire Idiot box (3^rd Gen) bachelor for APK2 to target. If yous don't remove the device support from the start APK, you won't be able to target it with the second APK.

   

   In this scenario, we removed support for Fire TV (3^rd Gen) considering we want to select it with our second APK

   Note that if you're updating an existing APK, when you clear the checkbox next to some supported devices, you lot may see a "Reduced device support" warning. This alert lets yous know that y'all're shrinking the number of supported devices for your app. Customers who previously installed your app on those devices (now unsupported past this APK) won't get the update. (You can read more than in Warning: Reduced device support.) Since you're uploading multiple APKs, you lot can disregard this notice. After you upload another APK and target these devices removed from your first APK, the alarm will no longer be applicable.

3. (Optional) Give your APK a recognizable allonym to distinguish it from the next APK you upload.

4. Drag another APK file into the APK Files box. Optionally, alter the alias for the new APK you uploaded to distinguish information technology from the first APK.

   When you drag another APK into the APK Files tab, the devices supported by the first APK are unavailable for the second APK — because 2 APKs tin can't be installed on the aforementioned device. Under the greyed-out devices, you lot should see the phrase "Targeted by another APK in the current version." ("Targeted" only means that you selected support for the device with your app.) Remember this rule: Multiple APKs cannot be installed on the same device. With the second APK, you tin select support for devices not already selected by the beginning APK.

   Continuing with our previous example, suppose y'all upload "APK2" and desire Fire Television receiver (3^rd Gen) to support this APK. You lot already cleared back up for this device with the previous APK, and then it should at present be selectable with this 2d APK.

   

   Burn TV (three^rd Gen) tin exist selected because you didn't already select back up for it with the previous APK. The other devices have a gray 10, pregnant they are unavailable to exist supported by this APK because they are already supported by the previous APK.

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

5. When finished, click Save.

   Yous can add more than than ii APKs per app. Proceed adding equally many APKs as desired.

Troubleshooting Common Errors

This section provides troubleshooting information related to APK submissions on the APK Files tab.

Error: Duplicate package proper name

When uploading an APK, yous see the following error:

"Failed to upload APK. The parcel 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 than data.

Offset, bank check to make sure that yous have non uploaded this APK file on another Amazon developer account as either an app submission or Alive App Test. If you haven't uploaded this same APK nether another business relationship, submit a back up example reporting the issue and noting the package proper name. To submit a support case, sign in to the Developer Console, click the ? in the upper-correct corner, and click Contact Us

Note that when using development environments such as Unity or pre-existing manifest files, information technology's possible that your app'south package name will have a placeholder value that should be inverse prior to submission. The package name of your APK file must be unique to the app you are publishing and is normally in the format of com.companyname.appname.

If you lot have an association with a developer or publishing company that might take uploaded your app for Alive App Testing, contact your development partner to confirm that they have non submitted your app's APK file on their business relationship. If they have, ask them to end the current Live App Test. Then contact united states of america with the package name to resolve the result.

Alarm: Reduced device back up

When adjusting device support for an APK, you meet a warning that says the following:

Device back up 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 back up.

This message means that, with your newly uploaded APK, you accept introduced new attributes in your manifest or build.gradle file that shrink the number of uniform devices. Most unremarkably, you may have incremented the API level, which reduces the number of devices that can support the update. Every bit such, the Appstore is warning you that some devices may non be able to install this update.

For instance, suppose you lot publish an APK with manifest attributes that require at minimum API level xix, and customers with a device supporting API level 19 (simply not back up for any level greater) install the app. Subsequently, 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. Equally a result, the client will not come across that an update is available.

Target device non bachelor

When uploading a new APK, y'all see a message that says a particular device is not supported for your APK. The message might be as follows:

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

To see the reason the device isn't supported, move your mouse over the aid icon next to the device name in the Device Support dialog box. Run into Adjust Device Support for your APK above for more than details. The incompatibility could exist due to the API level, OpenGL compression format, CPU, screen size and density, device features, or fifty-fifty other factors about your app such as lack of availability in the geographic locale.

Targeted by another binary in the current version

If y'all're uploading multiple APKs, the device might already be supported by some other APK. If so, when you move your mouse over the unsupported device, it says:

Targeted by some other binary in the current version.

Multiple APKs cannot support the same device. Y'all'll need to edit the device support for one APK so that you can select back up for the device with the other APK. Come across Add Multiple APKs for the Same App for pace-by-step details. Come across Multiple APKs for the Aforementioned Application Listing for a more conceptual background.

Side by side Steps

Go to the adjacent step: Step 8: Submit Your App and Bank check Condition.

---

Last updated: Mar fifteen, 2022

petersonxylashe.blogspot.com

Source: https://www.developer.amazon.com/docs/app-submission/publish-app-upload-apk-files.html

Share this post