after split APK which one should I choose?

cannot build selected target abi: x86, no suitable splits configured armeabi-v7a'', arm64-v8a
merge split apk
split apk packer
titanium backup split apk
gradle split
bundletool
configureapk
enableseparatebuildpercpuarchitecture

I split my apk application and I got multiple apk

now which one I will choose to import to my play store ?

You add all of them, Play Store chooses the right one for the user, depending on their device. Just be sure to use different version codes for every apk.

See official documentation for more information.

after split APK which one should I choose?, I split my apk application and I got multiple apk now which one I will choose to import to my play store ? You add all of them, Play Store chooses the right one for � If you publish your app to Google Play, you should build and upload an Android App Bundle.When you do so, Google Play automatically generates and serves optimized APKs for each user’s device configuration, so they download only the code and resources they need to run your app. Publishing multiple APKs is useful if you are not publishing to Google Play, but you must build, sign, and manage

you can let gradle auto configure your version code, then upload ALL of the apps to the play store.

google's example below will auto append 001, 002 or 003 depending on the variant ('armeabi-v7a':1, x86:2, x86_64:3).

do note that you will have to upload the play store from the smallest number to the biggest number.

see https://developer.android.com/studio/build/configure-apk-splits.html#configure-APK-versions

android {
  ...
  defaultConfig {
    ...
    versionCode 4
  }
  splits {
    ...
  }
}

// Map for the version code that gives each ABI a value.
ext.abiCodes = ['armeabi-v7a':1, x86:2, x86_64:3]

// For per-density APKs, create a similar map like this:
// ext.densityCodes = ['mdpi': 1, 'hdpi': 2, 'xhdpi': 3]

import com.android.build.OutputFile

// For each APK output variant, override versionCode with a combination of
// ext.abiCodes * 1000 + variant.versionCode. In this example, variant.versionCode
// is equal to defaultConfig.versionCode. If you configure product flavors that
// define their own versionCode, variant.versionCode uses that value instead.
android.applicationVariants.all { variant ->

  // Assigns a different version code for each output APK
  // other than the universal APK.
  variant.outputs.each { output ->

    // Stores the value of ext.abiCodes that is associated with the ABI for this variant.
    def baseAbiVersionCode =
            // Determines the ABI for this variant and returns the mapped value.
            project.ext.abiCodes.get(output.getFilter(OutputFile.ABI))

    // Because abiCodes.get() returns null for ABIs that are not mapped by ext.abiCodes,
    // the following code does not override the version code for universal APKs.
    // However, because we want universal APKs to have the lowest version code,
    // this outcome is desirable.
    if (baseAbiVersionCode != null) {

      // Assigns the new version code to versionCodeOverride, which changes the version code
      // for only the output APK, not for the variant itself. Skipping this step simply
      // causes Gradle to use the value of variant.versionCode for the APK.
      output.versionCodeOverride =
              baseAbiVersionCode * 1000 + variant.versionCode
    }
  }
}

For more examples of alternate version code schemes, see Assigning version codes (https://developer.android.com/google/play/publishing/multiple-apks.html#VersionCodes)

Build multiple APKs, Although you should build a single APK to support all your target devices To configure your build for multiple APKs, add a splits block to your The following Gradle DSL options are used to configure multiple APKs for screen densities: ABI column and choose the desired variant or ABI from the list field. Using the new Split mechanism, building a hdpi, and an mdpi version of the same app will share a lot of the tasks (like javac, dx, proguard). Additionally, it will be considered a single variant and the same test app will be used to test every multi-apk.

Multiple APK support, Multiple APK support is a feature on Google Play that allows you to publish If you publish your app to Google Play, you should build and upload an each APK uses filters to support a variation of the following device characteristics: Figure 1 shows two examples that split based on both the platform� Certain Android apps are split into several APK files and packed into a zipped folder. We’ll explain everything to you need to know to install this kind of file and how to do so If you’re dealing with Split APKs, their installation is quite different compared to ordinary apps as you’ll need to make use of an additional tool .

Depends on which device you want to target. Play store will tell you how much device you have left out after uploading an apk. Make sure you have version code different for each flavor if you want to upload multiple ones. For example,I have XXXn where n is the code for cpu architecture.

Reducing APK size by using ABI Filters and APK split, After running Analyze APK command and selecting APK file we can take If we would also configure splits by screen density then APK files for� The concept for using multiple APKs on Google Play is that you have just one entry in Google Play for your application, but different devices might download a different APK. Creating Multiple APKs Once you decide to publish multiple APKs, you probably need to create separate Android projects for each APK you intend to publish so that you can

I can't publish multiple release the problem is the release code or version

ext.abiCodes = ['x86_64':1,'x86':2,'armeabi':3,'armeabi-v7a':4,'arm64-v8a':5,'mips':6]

android {
    compileSdkVersion 27
    defaultConfig {
        applicationId "com.book.walid.resumephilosophie"
        minSdkVersion 15
        resConfigs "ar"
        targetSdkVersion 27
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }
    splits {
        abi{
            enable true
            reset()
            include 'x86_64','x86','armeabi','armeabi-v7a','arm64-v8a','mips'
            universalApk false
        }

    }
    android.applicationVariants.all { variant ->
        def baseAbiVersionCode =
                project.ext.abiCodes.get(com.android.build.OutputFile.ABI)
        if (baseAbiVersionCode != null) {

            output.versionCodeOverride =
                    baseAbiVersionCode * 1000 + variant.versionCode
        }
    }

    buildTypes {
        release {
            minifyEnabled true
            shrinkResources true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        }
    }

Is it possible to merge split APK apps?, I get it, you guys hate split APKs as much as I do. So why doesn't Raccoon simply merge them into a traditional APK? Is that even After all, the whole point behind App Bundles is to make scraping Play as difficult as possible. Make sure to pick the right one: only the one from the base module matters. Depends on which device you want to target. Play store will tell you how much device you have left out after uploading an apk. Make sure you have version code different for each flavor if you want to upload multiple ones. For example,I have XXXn where n is the code for cpu architecture.

Split-Apks Extract & Share. Have you ever tried to share an apk?, Using them you can share or extract apps/apks with your friends or family, the button to install the splits and choose all the splits, your app will be installed. After you build your Android App Bundle, you should test how� Download SplitCloud apk 5.8 for Android. स्ट्रीम संगीत और प्लेलिस्ट, इस दोहरे संगीत प्लेयर ऐप के साथ हेडफ़ोन साझा करें

Split APKs Installer (SAI), SAI is an app for installing and exporting split APKs - apps that consist of multiple APKs. SAI can install apps using standard Android API, using root access or� menu → Settings → Uncheck Delta updates. It says: “Full apk is downloaded every time” Well, I think “split APK” and “Delta updates” are not the same. And if I remember right delta updates had always been unchecked on my device device - but I still got the split APK message for some apps before changing to root update method.

FAQ, 10 If there are both nodpi and specific dpi APKs available, which one should I download? 13 How are you going to deal with split APKs/App Bundles/ Dynamic Delivery? If there is no exact match, pick the APK with a higher DPI than your device, After trying numerous system info apps, we are currently recommending� Tested pm myself on Pie. Let's suppose that our package is called com.example.apk: you'd install it with pm install com.example.apk.Next, to install the split parts, you need to issue pm install -p com.example com.example.split.apk, where -p com.example refers to the package name of the base package, and com.example.split.apk is your split package.

Comments
  • then I have to modify these codes : versionCode 1 versionName "1.0" for every one
  • @walidroid, you can let gradle auto-modify the version codes (see my answer)
  • @walidroid yes it's written in the documentation how.
  • I got this error : Could not get unknown property 'output' for object of type com.android.build.gradle.internal.api.ApplicationVariantImpl.