Bazaar’s new feature for developers is uploading multiple packages with different configurations in a single release. This feature allows users to automatically receive the compatible application version based on their CPU architecture and SDK version.

Supporting a wide range of devices with diverse CPU architecture in a single package is not optimal in terms of package size. With the latest feature, you provide smaller and more compatible packages for users’ various devices.

To upload several packages in one release, complete the following:
  • All package names and signatures of an application should be the same.
  • The CPU and SDK versions of all packages in a single release should vary and it is not permitted to upload two packages for one type of CPU with the same SDK version.
  • CPUs that are supported in a single release by Bazaar:
    • armeabi-v7a
    • arm64-v8a
    • All
  • The armeabi-v7a package is available on all devices with an arm64-v8a CPU architecture. Therefore, if there is no specified package for arm64-v8a, the package armeabi-v7a will be presented to all devices.
  • A package with the “All” CPU architecture type is equivalent to the armeabi-v7a package. So in each release for every SDK version, it is not permitted to upload two packages of armeabi-v7a and “All” simultaneously.
  • There is a possibility that all CPUs are not covered in a release.
  • At least one package should be uploaded to submit a release request.
  • Each package should have a unique version code that differs from other packages.
  • The version code of the packages with the same architecture must always be increased in relation to the package version code of the same architecture of the previous release. Also,uploading packages with the same version codes in one release are not permitted.
  • The package’s version code with a higher SDK for one type of CPU must be bigger than all of the packages with a lower SDK version in the same CPU. Increasing the number of packages in an SDK version depends on the type of CPU architecture. Therefore, the version code of arm64-v8a package should always be bigger than the armeabi-v7a package’s version code and the version code of armeabi-v7a package must be bigger than “All” package’s version code.
  • Based on Bazaar instructions on the release, among the packages compatible with the user's device, the package with the highest version code is automatically delivered to that device.For instance, the order of packages’ version codes based on the SDK version and CPU architecture in three releases, should be as follow:

First Release:

SDK versionarm64-v8aarmeabi-v7aAll

Second Release:

SDK versionarm64-v8aarmeabi-v7aAll

Third Release:

SDK versionarm64-v8aarmeabi-v7aAll
  • In the previous example, the package with version code 17 will only be received in arm64-v8a devices with sdk version 9 and lower; And arm64-v8a devices with sdk version 10 and upper will receive the package with version code 20.
  • Note that users will always receive the most compatible package with the highest version code while updating. 
  • version code of 17 will only be received in the arm64-v8a devices with the sdk version of 9 and lower. And All the packages of a single release are evaluated separately by Bazaar Review Team and acceptance or rejection of each package is possible.
  • After evaluating every package by Bazaar Review Team, If the release consists of at least one approved package, it will be published with the only approved package. (The unapproved packages will not be released.)
  • There can be up to one open release at a time. Open release means that no request has been submitted for that release.
  • After submitting a release request, it is possible to cancel the review request or disable the release. After canceling the review request, you can resubmit the request for the same release. Last but not least, canceling a release is unreturnable and after that, you need to upload the packages with new version codes to review.
Was this content helpful?
Write your comment here...

If you have any comment on this content or any idea to make it better, use this form to send us your comment.

Publish Date: 1400-04-10 19:48

Latest Update: 1400-04-11 14:47