Android Build Tools only creates x86_64, no matter what. APK runs via adb but shows incompatibility in the Play Store

Question

So this is happening. No matter what I try to do in build.gradle, all the APKs exit with the native_code = 'x86_64' flag, so when I deploy the application to the repository, the result has + 15K simple devices and only 19 compatible ones. At first I thought that, somehow, with the NDK installed there was a reason, or my modified build script. But this still happens when I look at the APK Signature Creation Wizard. The splits block was also initially absent and did not help. The strangest thing is that when I install console push, IT WORKS!

I also tried switching to the recommended JRE, as well as several APK naming strategies regarding file creation, such as moving output to different directories or not using the file constructor.

My build.gradle looks like this:

 defaultConfig { applicationId "com.chiskosystems.brokr" versionCode versionNumber versionName "${versionMajor}.${versionMinor}.${versionPatch} (${versionBuild}) Release" minSdkVersion 16 targetSdkVersion 25 testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner" multiDexEnabled true jackOptions { enabled false } vectorDrawables { useSupportLibrary true } } splits { abi { enable true reset() include 'armeabi', 'armeabi-v7a', 'arm64-v8a' } } project.ext.versionCodes = ['armeabi': 1, 'armeabi-v7a': 2, 'arm64-v8a': 3] applicationVariants.all { variant -> variant.outputs.each { output -> def fileNaming = "apk/brokr" def outputFile = output.outputFile output.versionCodeOverride = project.ext.versionCodes.get(output.getFilter( com.android.build.OutputFile.ABI), 0) * 10000000 + android.defaultConfig.versionCode } } signingConfigs { release { try { storeFile file('../mystore.jks') keyAlias 'release' storePassword KEYSTORE_PASSWORD keyPassword KEY_PASSWORD } catch (ex) { throw new InvalidUserDataException("You should define KEYSTORE_PASSWORD and KEY_PASSWORD in gradle.properties.") } } } dataBinding { enabled true } dexOptions { javaMaxHeapSize "3g" preDexLibraries false } buildTypes { release { minifyEnabled false proguardFile 'path/proguard-project.pro' ... buildConfigField "String", 'SERVER', '"https://myfirebaseserver.com"' debuggable false signingConfig signingConfigs.release } debug { minifyEnabled false applicationIdSuffix ".debug" versionNameSuffix "-debug" buildConfigField "String", 'SERVER', '"https://myfirebaseserver.com"' } } compileOptions { sourceCompatibility JavaVersion.VERSION_1_8 targetCompatibility JavaVersion.VERSION_1_8 } productFlavors { sandbox { buildConfigField "String", 'PAYPAL_ENV', '"PayPalConfiguration.ENVIRONMENT_NO_NETWORK"' } full { buildConfigField "String", 'PAYPAL_ENV', '"PayPalConfiguration.ENVIRONMENT_PRODUCTION"' signingConfig signingConfigs.release targetSdkVersion 25 } } 

It happens in both Win and Unix systems. I spent the whole day without changing the script, and now I am helpless.

Any ideas on what's going on? Thank you very much!

Answer 1

The reason was the addiction:

 compile 'com.lambdaworks:scrypt:1.4.0' 

apparently automatically captures my laptop architecture and captures this flag there.