Where Do I Upload My Apk to Amazon?

Stride 7: Upload App Files (APK Files)

The documentation here relates to the APK Files tab:

On the APK Files tab, y'all upload your APK files, signal which devices your APKs back up, and more. For more than conceptual topics related to APKs, encounter the following:

Preparing the APK File for Your App: Provides data about preparing your APK and the code wrapper that Amazon uses with your APK, also as APK size limitations and other details.
Device Filtering and Compatibility: Explains how attributes in your manifest make up one's mind the devices your APK supports.

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

APK Files Fields
Public Fundamental and PEM File
Appstore Certificate Hashes
Update an Existing APK
Adjust Device Back up for Your APK
Add Multiple APKs for the Same App
Troubleshooting Common Errors
- Fault: Duplicate package name
- Alert: Reduced device support
- Target device not available
- Targeted by another binary in the current version
Side by side Steps

APK Files Fields

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

APK Files tab fields
Field	Clarification
Apply Amazon DRM?	For each app that y'all submit to Amazon (a single app might contain multiple APKs), you can choose either to apply DRM or make your app available without whatsoever rights management constraints. DRM (digital rights management) protects your app from unauthorized use. The DRM setting applies to all of your app's APKs. Without DRM, your app can be used without restrictions past whatsoever user. If yous choose to apply DRM to one of your apps, yous must use the DRM organization provided past 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 adding a new APK with different DRM settings than your previous APKs, you'll demand to replace the previous APKs as well so they can receive the updated DRM settings. Otherwise, your previous APKs volition retain the same DRM settings equally earlier, regardless of your selection here. Come across About DRM for more information.
APK File	Upload your Android APK files (drop 1 file at a fourth dimension into the box). If didn't use Android Studio to build your signed APK, you might need to zipalign your file. When y'all add an APK file, you tin see its details by clicking the data icon . These details include the version code, version name, file size, packet proper name, minimum SDK version, features, libraries, permissions, localizations, supported screens, compatible screens, OpenGL details, and native platforms. For example: These details decide what devices are supported by your APK (filtering is explained in Device Filtering and Compatibility). After y'all upload an APK, the APK receives an alias named later on the API level (for example, "apilevel22"). You can rename the alias every bit desired. The custom alias is used internally and non exist seen by customers. See Preparing the APK File for Your App and Updating a Published App for more than details related to APK files.
Language Support	Select at to the lowest degree one language supported past your APK. Your selection here appears in a "Supported Languages" section in the device app details page in the Appstore to let users know which language is available in the app. (The "Supported Languages" department appears only on the device's display of Appstore apps, not on the Amazon Appstore website.) The Linguistic communication Support choice hither doesn't influence whether your app becomes bachelor in localized Appstore marketplaces. Whatever localization interfaces in your APK must be handled by your APK itself, not through settings in the Appstore submission procedure. All the same, if you do take a localized APK, you tin add localized descriptions and paradigm assets. The descriptions, prototype avails, and linguistic communication support option selected here all inform your app details folio 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 post-obit — If your app has hard-to-discover features, include directions here for finding those features. As well, if you need to resubmit your app based on feedback from Amazon, you tin utilise this field to respond to the exam study emails. If your app requires users to log in before launching and using the app, include a set of exam credentials for the Amazon test team to employ. If Amazon cannot successfully launch your app during testing, the app volition exist rejected.
Export Compliance	Asks you to certify that your app is compliant in all countries in which you've chosen to make information technology available. You lot can read more than details in the "Compliance with Laws; Privacy and Security Obligations" section in the Amazon Developer 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 take the Google Maps API implemented.

Public Cardinal and PEM File

In the upper-right area of the tab, there is a link for a Public Key. This public cardinal, which is unique per app, establishes a secure communication channel betwixt the Amazon Appstore and your app. When you generate the public key from the Programmer Console, Amazon generates a corresponding private key. These public and individual keys form a cardinal pair to sign license responses. Through this fundamental pairing, you lot 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 together the PEM file to your project. To configure your app with the public primal:

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

PEM file link
Copy the AppstoreAuthenticationKey.pem file.
Follow the instructions for your project type.

Android project instructions
1. Paste the PEM file into the app/src/chief/avails folder of your Android Studio projection.
2. In the Projection view, the assets folder is usually in app/src/main/assets. If your app doesn't have an avails folder, you must create i. So 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 Avails/StreamingAssets folder.

For more details, run across Configure Appstore SDK with your public central or Configure Unity App with Public Key.

Appstore Document 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 function of the ingestion process, Amazon removes your developer signature and applies an Amazon signature. This signature is unique to you, does non change, and is the same for all apps in your account. For more than details, meet Amazon App Signatures.

Update an Existing APK

If yous're updating an existing APK, encounter Updating a Published App. When you make the update, you lot have the option 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

Afterwards 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 'X' next to their name are unsupported. Unsupported devices are adamant past the attributes in your manifest and the countries you targeted in Step 3: Add Availability & Pricing.

To understand why a device isn't supported by your APK, motility your mouse over the aid icon next to the device name in the Device Support dialog box, equally shown in the following image.

If necessary, you lot tin can manually remove back up for devices that have known compatibility issues. The supported devices are grouped into 3 categories:

Amazon Fire phones and tablets: Shows the Burn phones and tablet support for your app. Come across the Tablet Device Specifications for more details. By default, device support for your uploaded APK is turned on for all Amazon Fire Telephone and Fire tablet devices, and for all non-Amazon Android devices.
Amazon Burn Goggle box devices: Shows the Fire TV device support for your app. For details on Burn TV device names, come across Fire TV naming conventions; for specifications, meet Device Specifications for Fire Idiot box.
Not-Amazon Android devices: Shows Android devices on which your app could exist 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 especially helpful if your app is simply available in the Amazon Appstore, not on Google Play). Within this not-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 past your app, click Edit device support and update the devices indicated. Toggle device support on (green) or off (grayness) as appropriate. Utilize the tabs at the top of the dialog to motion between categories.

For case, if you're uploading a streaming media app designed for Burn down TV devices, click Edit device back up on the Amazon Fire Boob tube devices row and select the appropriate device back up options on the Amazon Fire TV tab:

For boosted information about supported devices for your APK, encounter the following:

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

For non-Amazon devices, at the bottom of the Device Support dialog, there's an choice for All other Android devices. The Not-Amazon Android devices can be toggled on or off as a whole, or you can manually adjust device support. This setting allows your app to exist 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 you turn off "All other Android devices," you alter your compatibility strategy from using a deny listing to using an permit list for not-Amazon devices. In other words, your APK won't be compatible by default on those devices; instead, you'll demand to manually select which tertiary-party devices your APK will support.

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

Add together Multiple APKs for the Same App

When uploading multiple APKs, make sure each APK has the aforementioned package name in the manifest; nonetheless, each individual APK should have a unique versionCode in your Gradle build file.

When you add multiple APKs, because each APK tin can simply be bachelor for a single device, you have to remove support for devices from your first APK that you desire to be available for the boosted APKs. The following pace-by-stride instructions and screenshots will clarify this choice process.

To upload multiple APKs:

If you haven't already uploaded your first APK, upload information technology by dragging the APK into the APK Files box.
For the outset APK yous uploaded, side by side to "Supported Devices," click Edit and remove back up for devices that y'all program to target with your second APK.

For case, suppose you have ii APKs for your Burn down Television set app — "APK1" and "APK2". With APK1, you want to target all Fire Boob tube devices except Burn Tv (3^rd Gen). For APK1, click Edit next to "Supported Devices" in the APK File section. In the Device Support dialog box that appears, clear the checkbox next to "Fire Boob tube (3^rd Gen)." This will make Fire TV (3^rd Gen) bachelor for APK2 to target. If you don't remove the device support from the first APK, you won't be able to target information technology with the second APK.

In this scenario, we removed back up for Fire TV (iii^rd Gen) because we want to select it with our second APK

Note that if you're updating an existing APK, when y'all articulate the checkbox adjacent to some supported devices, you may see a "Reduced device support" warning. This warning lets you know that you're shrinking the number of supported devices for your app. Customers who previously installed your app on those devices (now unsupported by this APK) won't get the update. (Y'all can read more in Warning: Reduced device support.) Since y'all're uploading multiple APKs, yous can disregard this notice. After you upload another APK and target these devices removed from your first APK, the alert volition no longer be applicable.
(Optional) Give your APK a recognizable allonym to distinguish it from the next APK you upload.
Drag some other APK file into the APK Files box. Optionally, change the alias for the new APK you uploaded to distinguish it from the outset APK.

When you lot drag another APK into the APK Files tab, the devices supported by the start APK are unavailable for the second APK — because two APKs tin't be installed on the aforementioned device. Under the greyed-out devices, y'all should see the phrase "Targeted past another APK in the current version." ("Targeted" merely ways that you selected back up for the device with your app.) Call back this rule: Multiple APKs cannot exist installed on the aforementioned device. With the second APK, y'all can select support for devices not already selected by the first APK.

Continuing with our previous instance, suppose y'all upload "APK2" and desire Fire TV (three^rd Gen) to support this APK. You lot already cleared back up for this device with the previous APK, and then it should now be selectable with this second APK.

Burn Boob tube (3^rd Gen) tin can be selected because you didn't already select support for it with the previous APK. The other devices have a grey 10, significant they are unavailable to be supported by this APK considering they are already supported past 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.
When finished, click Relieve.

Y'all tin can add together more 2 APKs per app. Continue adding as many APKs as desired.

Troubleshooting Common Errors

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

Error: Duplicate package name

When uploading an APK, y'all see the following error:

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

First, check to make certain that you accept not uploaded this APK file on another Amazon programmer business relationship every bit either an app submission or Live App Test. If you haven't uploaded this same APK nether some other account, submit a support case reporting the issue and noting the package name. To submit a back up instance, sign in to the Developer Console, click the ? in the upper-right corner, and click Contact Us

Note that when using development environments such equally Unity or 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 APK 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 take uploaded your app for Alive App Testing, contact your evolution partner to confirm that they take non submitted your app's APK file on their business relationship. If they accept, inquire them to end the current Live App Exam. So contact us with the parcel name to resolve the issue.

Alarm: Reduced device support

When adjusting device support for an APK, y'all meet a alert that says the following:

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

This bulletin means that, with your newly uploaded APK, you have introduced new attributes in your manifest or build.gradle file that shrink the number of compatible devices. Most ordinarily, you may have incremented the API level, which reduces the number of devices that can back up the update. As such, the Appstore is alert you lot that some devices may not exist able to install this update.

For example, suppose you publish an APK with manifest attributes that require at minimum API level xix, and customers with a device supporting API level nineteen (but not back up for any level greater) install the app. Later, y'all 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 nineteen) installed. As a result, the customer will not come across that an update is bachelor.

Target device not available

When uploading a new APK, you lot run into a message that says a particular device is not supported for your APK. The message might exist every bit 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 help icon next to the device proper noun in the Device Support dialog box. See Adjust Device Support for your APK above for more details. The incompatibility could be 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 you're uploading multiple APKs, the device might already be supported past another APK. If so, when y'all motility your mouse over the unsupported device, information technology says:

Targeted by some other binary in the current version.

Multiple APKs cannot support the aforementioned device. You'll need to edit the device support for one APK and 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-pace details. See Multiple APKs for the Same Awarding Listing for a more than conceptual background.

Side by side Steps

Go to the next footstep: Step eight: Submit Your App and Check Status.

Last updated: Mar 15, 2022

turneyantim1984.blogspot.com

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