Can I Upload a Document in Roar App

Step 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, point which devices your APKs support, and more. For more conceptual topics related to APKs, meet the following:

Preparing the APK File for Your App: Provides information near preparing your APK and the code wrapper that Amazon uses with your APK, too every bit APK size limitations and other details.
Device Filtering and Compatibility: Explains how attributes in your manifest determine 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 Document Hashes
Update an Existing APK
Suit Device Support for Your APK
Add together Multiple APKs for the Same App
Troubleshooting Common Errors
- Error: Duplicate package name
- Warning: Reduced device support
- Target device not available
- Targeted by another binary in the current version
Next Steps

APK Files Fields

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

APK Files tab fields
Field	Description
Apply Amazon DRM?	For each app that yous submit to Amazon (a single app might comprise multiple APKs), you can choose either to apply DRM or brand your app available without any rights management constraints. DRM (digital rights management) protects your app from unauthorized utilize. The DRM setting applies to all of your app's APKs. Without DRM, your app tin can be used without restrictions past any user. If you lot cull to apply DRM to one of your apps, you must utilise the DRM system provided by Amazon through the Programmer Portal. Notation 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, yous'll need to replace the previous APKs equally well and then they can receive the updated DRM settings. Otherwise, your previous APKs volition retain the same DRM settings as before, regardless of your choice here. Encounter About DRM for more than information.
APK File	Upload your Android APK files (drop ane file at a time into the box). If didn't employ Android Studio to build your signed APK, you might need to zipalign your file. When you add an APK file, you can meet its details by clicking the information icon . These details include the version lawmaking, version name, file size, packet name, minimum SDK version, features, libraries, permissions, localizations, supported screens, compatible screens, OpenGL details, and native platforms. For example: These details make up one's mind what devices are supported by your APK (filtering is explained in Device Filtering and Compatibility). After you lot upload an APK, the APK receives an alias named later the API level (for example, "apilevel22"). You lot can rename the alias as desired. The custom alias is used internally and not be seen by customers. Come across Preparing the APK File for Your App and Updating a Published App for more than details related to APK files.
Language Support	Select at least one language supported past your APK. Your option here appears in a "Supported Languages" department in the device app details page in the Appstore to permit users know which language is bachelor in the app. (The "Supported Languages" department appears merely on the device's brandish of Appstore apps, not on the Amazon Appstore website.) The Language Support selection here doesn't influence whether your app becomes bachelor in localized Appstore marketplaces. Any localization interfaces in your APK must be handled past your APK itself, not through settings in the Appstore submission process. Yet, if you do have a localized APK, you lot can add localized descriptions and image assets. The descriptions, image avails, and language support option selected here all inform your app details folio in the Amazon Appstore. See Distribute Your App Internationally for more than 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-discover features, include directions hither for finding those features. Also, if y'all need to resubmit your app based on feedback from Amazon, yous can use this field to respond to the test written 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 squad to use. If Amazon cannot successfully launch your app during testing, the app will be rejected.
Consign Compliance	Asks you to certify that your app is compliant in all countries in which you've called to make it available. You 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. Only used in tablet and phone apps if you accept the Google Maps API implemented.

Public Key and PEM File

In the upper-right surface area 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 yous generate the public key from the Developer Console, Amazon generates a corresponding private key. These public and private keys form a fundamental 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 lot must add the PEM file to your projection. To configure your app with the public key:

Click Public Key.
In the Public Key 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 projection 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 ordinarily in app/src/main/assets. If your app doesn't take an assets folder, you lot must create one. Then drag your PEM file into information technology.
Unity project instructions
1. In the Assets binder of your project, create a new folder named StreamingAssets.
2. Paste the PEM file in your Assets/StreamingAssets binder.

For more details, run into Configure Appstore SDK with your public cardinal or Configure Unity App with Public Cardinal.

Appstore Certificate Hashes

Document data, which includes the SHA-1, MD5, and SHA-256 hashes, is bachelor from a link in the upper-right expanse of the tab. As part of the ingestion procedure, Amazon removes your developer signature and applies an Amazon signature. This signature is unique to you lot, does not change, and is the same for all apps in your account. For more details, run into Amazon App Signatures.

Update an Existing APK

If you're updating an existing APK, see Updating a Published App. When you make the update, yous have the selection of replacing an existing APK and retaining the same Device Support selections, or removing the previous APK and re-selecting your Device Back up details.

Arrange 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 side by side to the number of supported devices. In the Device Support overlay, devices with an 'X' side by side to their name are unsupported. Unsupported devices are determined by the attributes in your manifest and the countries you targeted in Step 3: Add Availability & Pricing.

To empathise why a device isn't supported by your APK, move your mouse over the help icon next to the device name in the Device Support dialog box, as shown in the following image.

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

Amazon Fire phones and tablets: Shows the Fire phones and tablet back up for your app. See the Tablet Device Specifications for more than details. By default, device back up for your uploaded APK is turned on for all Amazon Burn down Phone and Burn down tablet devices, and for all not-Amazon Android devices.
Amazon Fire Television devices: Shows the Fire Tv device support for your app. For details on Fire TV device names, see Burn down TV naming conventions; for specifications, see Device Specifications for Burn down TV.
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 boosted distribution avenues for your app (and is especially helpful if your app is only available in the Amazon Appstore, not on Google Play). Inside 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 arrange which devices are supported past your app, click Edit device support and update the devices indicated. Toggle device back up on (green) or off (grey) as appropriate. Apply the tabs at the top of the dialog to move between categories.

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

For additional information about supported devices for your APK, see the post-obit:

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

For non-Amazon devices, at the lesser of the Device Back up dialog, there's an option for All other Android devices. The Non-Amazon Android devices can be toggled on or off as a whole, or you can manually arrange device back up. 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's compatibility.

If you turn off "All other Android devices," you change 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'll need to manually select which tertiary-party devices your APK will support.

To add an additional APK for the same app, see the next department, Add Multiple APKs for the Aforementioned App.

Add Multiple APKs for the Aforementioned App

When uploading multiple APKs, make sure each APK has the same bundle proper noun in the manifest; notwithstanding, each individual APK should have a unique versionCode in your Gradle build file.

When you lot add together multiple APKs, because each APK tin can only be available for a single device, you have to remove support for devices from your first APK that you desire to be available for the additional APKs. The following step-by-step instructions and screenshots will clarify this selection process.

To upload multiple APKs:

If you oasis't already uploaded your first APK, upload it by dragging the APK into the APK Files box.
For the get-go APK you uploaded, next to "Supported Devices," click Edit and remove support for devices that yous programme to target with your 2d APK.

For instance, suppose you have ii APKs for your Fire Television receiver app — "APK1" and "APK2". With APK1, you want to target all Fire Goggle box devices except Burn down Boob tube (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 TV (three^rd Gen)." This volition make Fire Idiot box (three^rd Gen) available for APK2 to target. If you don't remove the device support from the beginning APK, you lot won't be able to target information technology with the second APK.

In this scenario, nosotros removed support for Burn Goggle box (3^rd Gen) because we desire to select it with our second APK

Note that if y'all're updating an existing APK, when you clear the checkbox adjacent to some supported devices, you lot may see a "Reduced device back up" warning. This alert lets you lot know that you lot'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. (Yous can read more in Warning: Reduced device support.) Since you're uploading multiple APKs, you can condone this notice. After you upload another APK and target these devices removed from your first APK, the alarm will no longer be applicable.
(Optional) Requite your APK a recognizable allonym to distinguish it from the adjacent APK you upload.
Drag some other APK file into the APK Files box. Optionally, change the alias for the new APK yous uploaded to distinguish it from the first APK.

When you elevate another APK into the APK Files tab, the devices supported by the first APK are unavailable for the second APK — considering two APKs can't be installed on the aforementioned device. Under the greyed-out devices, you lot should encounter the phrase "Targeted by another APK in the electric current version." ("Targeted" only means that y'all selected support for the device with your app.) Retrieve this dominion: Multiple APKs cannot be installed on the same device. With the second APK, you can select back up for devices non already selected past the start APK.

Continuing with our previous case, suppose yous upload "APK2" and want Fire Television set (3^rd Gen) to support this APK. Yous already cleared support for this device with the previous APK, so it should now be selectable with this 2d APK.

Fire Television (3^rd Gen) can exist selected considering yous didn't already select support for it with the previous APK. The other devices have a gray X, pregnant they are unavailable to be supported by this APK because 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 Save.

You can add more than two APKs per app. Continue adding as many APKs as desired.

Troubleshooting Common Errors

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

Error: Duplicate parcel proper noun

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

"Failed to upload APK. The bundle name of the uploaded APK, com.amazon.android.yourapp, is already in utilise past an app endemic by a dissimilar developer. Please contact us for more information.

Kickoff, check to make sure that you take non uploaded this APK file on another Amazon programmer account equally either an app submission or Alive App Test. If you oasis't uploaded this same APK under some other business relationship, submit a support case reporting the issue and noting the package name. To submit a support case, sign in to the Programmer Panel, 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, it's possible that your app's bundle name will have a placeholder value that should be changed prior to submission. The packet name of your APK file must exist unique to the app you lot 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 Alive App Testing, contact your development partner to ostend that they have not submitted your app's APK file on their business relationship. If they have, inquire them to end the electric current Live App Test. So contact us with the bundle proper name to resolve the issue.

Warning: Reduced device back up

When adjusting device support for an APK, you see a alert that says the following:

Device support has been reduced from the previous version. Some existing customers volition non exist 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 APK, y'all have introduced new attributes in your manifest or build.gradle file that compress the number of compatible devices. Well-nigh commonly, you may have incremented the API level, which reduces the number of devices that can back up the update. As such, the Appstore is warning you that some devices may not be able to install this update.

For example, suppose you lot publish an APK with manifest attributes that require at minimum API level nineteen, and customers with a device supporting API level 19 (but not back up for whatsoever 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 exist incompatible with the previous version of the app the customer (with API level nineteen) installed. As a result, the customer volition not see that an update is available.

Target device not bachelor

When uploading a new APK, you meet a message that says a particular device is not supported for your APK. The message might exist as follows:

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

To meet the reason the device isn't supported, move your mouse over the help icon adjacent to the device name in the Device Support dialog box. See Conform 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 even other factors about your app such equally 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 yous move your mouse over the unsupported device, it says:

Targeted by another binary in the current version.

Multiple APKs cannot back up the same device. You'll need to edit the device back up for one APK and so that you can select back up for the device with the other APK. See Add Multiple APKs for the Same App for step-by-stride details. See Multiple APKs for the Same Awarding Listing for a more conceptual groundwork.

Next Steps

Go to the adjacent pace: Step 8: Submit Your App and Check Status.

Last updated: Mar 15, 2022

hildebrandfirig1972.blogspot.com

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