so files in all supported architectures: lib/armeabi-v7a, lib/arm64-v8a, and lib/x86 lib/x86_64 for 32-bit and 64-bit architectures, respectively. Ensure that the third-party libraries ( AAR files) contain the respective.Build the 32-bit and 64-bit APKs with two different version codes, which are separated by at least 1000.įor example, 64-bit version code = 32-bit version code + 1000.To support both 64-bit and 32-bit architectures in Google Play store, you must make sure that you perform the following actions: NOTE: From August 1st 2019 onwards, all apps published on Google Play must support 64-bit architectures. NOTE: From Quantum Visualizer V9 onwards, 64-bit APK’s are generated, by default. so files (arm64-v8a and x86_64) are packed by default. If you do not select the Support 32-bit devices option, 64-bit libraries /. so files (armeabi-v7a and x86) are packed and the application leaves out 64-bit. Once you select this option, only 32-bit.

Support 32-bit Devices - Select this option to build an Android APK with 32-bit support.Support x86 Devices - Select this option to support any Android-x86 devices.Store Password - Use this option to enter the password for the store.Store File - Use this option to locate and configure the store file.Key Password - Use this option to enter the password for the key.Key Alias- Use this option to enter the alias of the key.Signing - Use this option to sign the android binary automatically during the build process.Select the Maximum SDK Version that needs to be supported for the application.NOTE: The Target SDK Version must be greater than or equal to the Minimum SDK Version. Select the Target SDK Version that needs to be supported for the application.For example, a device with 5.0 version of SDK cannot run an application built on 4.0. NOTE: The application must be built with a minimum version matching the device SDK version. Select the Minimum SDK Version that needs to be supported for the application.You can increase each version by one to indicate a newer version. This version number is not shown to users. This number is used to determine whether the application is a recent version. The following are a few examples of valid Android Package names: NOTE: The name you specify for Android Package must contain at least two segments.Ī segment is a valid Java package name.

Package Name: Package name is a unique name to identify a specific application.Minimum pixels can be 8 x 8 and maximum pixels can be 248 x 248.Ĭlick the Android sub-tab, and set the following properties: For Desktop, the icon dimension must be in multiples of 8.The logo you specify here will be renamed to icon.png while building the application on the iPhone platform.From the Application Logo, you must browse and select an image file for the logo.NOTE: For iOS applications, if the Name of the app has non-English characters, you must add the unicodeAppNameFlag: true key in the infoplist_configuration.json file. If no name is specified, the Application ID specified under Application Properties is used.

Enter a Name for the Native channel version of the application.

Click the General sub-tab, and set the following properties:.

In Quantum Visualizer, from the Project Explorer, click Project Settings.

To set Native app properties, follow these steps: These properties range from the logo image your app displays to the types of screens and SDKs the app supports, and how certificates are handled.įrom Quantum Visualizer V8 SP4, you can also enable certain Android features by manually adding the corresponding properties to the androidbuild.properties file. Native app properties are divided into two categories: those that are common to all platforms, and those that are platform-specific.

Storyboard quick apk