添加库后，此版本仍不符合 Google Play 64 位要求错误

Question

I am uploading a video editor app on play store that has libraries with some native code. So I made it compatible for 64bit by adding this to gradle.

ndk.abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'

Adding it still problem is not solved . When I upload on playstore it still gives 64bit error. This is my gradle

apply plugin: 'com.android.application'

android {
    compileSdkVersion 28
    defaultConfig {
        applicationId "com.maam.videoeditor"
        minSdkVersion 17
        targetSdkVersion 28
        versionCode 5
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
        ndk.abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation 'com.android.support:appcompat-v7:28.0.0'
    implementation "com.android.support:customtabs:28.0.0"
    implementation 'com.android.support:design:28.0.0'
    implementation 'com.android.support:cardview-v7:28.0.0'

    implementation 'com.writingminds:FFmpegAndroid:0.3.2'

}

I have added 64bit line in gradle but on uploading 64bit not compliant error shows. Kindly guide on solving this problem.

Answer 1

@Osama: First of all, please check if your apk file have library in 64 bit. There are many way to do this: - Use Analyze Apk function of Android Studio (for more detail, please refer: https://developer.android.com/distribute/best-practices/develop/64-bit ) - Archive your apk file and check inside that folder. If your app doesn't has folder "arm64-v8a" it mean your app still not versioned up to 64 bit.

About your requirement, if you want your app is support 64 bit architecture, you must also version up your native library (.so file) to 64 bit.

About your code:

ndk.abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'"

I don't recommend you add this unless you use AppBundle new feature of Android Studio. Because when you use this, there will be 4 new apk file created for each architecture. And if you upload the file of arm64-v8a architecture, the error will disappear but it will announce you that your apk is support less device than previous release because it cannot support 32 bit device.

There are 2 possible solution for this problem:

1. Put all library file to your apk file, it will make your app bigger but it will allow your app to support every device.

2. Apply AppBundle for your project. For more detail about this, please check this link: https://android.jlelse.eu/a-practical-guide-to-android-app-bundle-for-beginners-7e8d93831828

Answer 2

android {    
    compileSdkVersion 29    
    defaultConfig {    
        -----    
        -----    
        ndk.abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'    
        ndk {    
            abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'    
        }    
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"    
    }    

    packagingOptions {    
            exclude 'lib/armeabi-v7a/libvudroid.so'    
            exclude 'lib/x86/libvudroid.so'    
            exclude 'lib/arm64-v8a/libvudroid.so'    
        }    

Answer 3

Google has released Flutter 1.7.8+hotfix.3 in stable channel, which makes easy to build app for release.

Now you have two options to build :

1. App bundle (preferred)
2. APK

Generating App Bundle

Run flutter build appbundle

This will create <app dir>/build/app/outputs/bundle/release/app.aab

T app bundle contains your Dart code and the Flutter runtime compiled for armeabi-v7a (32-bit) and arm64-v8a (64-bit).

Now you can upload this app bundle to google play.

Build an APK

flutter build apk --split-per-abi

This command results in two APK files:

<app dir>/build/app/outputs/apk/release/app-armeabi-v7a-release.apk
<app dir>/build/app/outputs/apk/release/app-arm64-v8a-release.apk

Removing the --split-per-abi flag results in a fat APK that contains your code compiled for all the target ABIs. Such APKs are larger in size than their split counterparts, causing the user to download native binaries that are not applicable to their device's architecture.

If you haven't upgraded to flutter 1.7 Below solution should still work.

You need to build two apk and upload it together. one for 32 and another for 64 bit.

This is what worked for me i am on flutter v1.5.4-hotfix.2

First run flutter build apk --release and upload the apk file

Then increase the version and build number in pubspec.yml file and run

flutter build apk --release --target-platform=android-arm64

Upload this new apk and start rollout.

Good luck

Answer 4

从我的情况来看，谷歌支持团队的回答是，这是由于上传了较旧的（旧版）版本构建（不符合 64 位要求），在上传新版本时将其包含在“上一个版本”部分应用。

Answer 5

You need to add the following to your android/app/build.gradle file:

android {    
    defaultConfig {
        ....
        ....
        ndk {
            abiFilters "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
        }
    }
}

add the following to your android/build.gradle file:

subprojects {
    afterEvaluate {project ->
        if (project.hasProperty("android")) {
            android {
                .....
                .....

                packagingOptions {
                    pickFirst 'lib/x86/libc++_shared.so'
                    pickFirst 'lib/arm64-v8a/libc++_shared.so'
                    pickFirst 'lib/x86_64/libc++_shared.so'
                    pickFirst 'lib/armeabi-v7a/libc++_shared.so'
                }
            }
        }
    }
}

This is to include the 64-bit architecture. If not this, then you might need to create app bundle and then upload

Answer 6

If you upload your apk on alpha version and this error will be show, so please check if any exiting apk is live or not if not live so please remove your old apk and upload your new apk.

I think your problem is solve.

Answer 7

我遇到了同样的情况...我的应用程序既不是游戏也不是跨平台应用程序...我遇到过这种情况...解决方案很简单...我的一个应用程序依赖（由gradle实现的库）正在使用ndk ...我删除它后，问题就消失了。