Flutter APK无法在Android 13安装，Android 14可正常运行求助

问题概述 #

开发的Flutter项目打包APK后，Android 14设备可正常安装运行，但Android 13设备仅提示“应用未安装”。设备存储空间充足，且已开启“未知来源应用安装”权限。相关配置文件如下：

app/build.gradle #

def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

android {
    compileSdkVersion 34

    sourceSets {
        main.java.srcDirs += 'src/main/kotlin'
    }

    lintOptions {
        disable 'InvalidPackage'
    }

    aaptOptions {
        cruncherEnabled = false
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId "com.example.vpn_app"
        minSdkVersion 16
        targetSdkVersion 34
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }
}

flutter {
    source '../..'
}

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'androidx.test:runner:1.1.1'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.1'
}

AndroidManifest.xml #

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.vpn_app">
    <!-- io.flutter.app.FlutterApplication is an android.app.Application that
         calls FlutterMain.startInitialization(this); in its onCreate method.
         In most cases you can leave this as-is, but you if you want to provide
         additional functionality it is fine to subclass or reimplement
         FlutterApplication and put your custom class here. -->
    <application
        android:name="${applicationName}"
        android:label="vpn_app"
        android:icon="@mipmap/ic_launcher">
        <activity
            android:name=".MainActivity"
            android:exported="true"
            android:launchMode="singleTop"
            android:theme="@style/LaunchTheme"
            android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
            android:hardwareAccelerated="true"
            android:windowSoftInputMode="adjustResize">
            <!-- Specify that the launch screen should continue being displayed -->
            <!-- until Flutter renders its first frame. -->
            <meta-data
                android:name="io.flutter.embedding.android.SplashScreenDrawable"
                android:resource="@drawable/launch_background" />
            <!-- Specifies an Android theme to apply to this Activity as soon as
                 the Android process has started. This theme is visible to the user
                 while the Flutter UI initializes. After that, this theme continues
                 to determine the Window background behind the Flutter UI. -->
            <meta-data
              android:name="io.flutter.embedding.android.NormalTheme"
              android:resource="@style/NormalTheme"
              />
            <!-- Displays an Android View that continues showing the launch screen
                 Drawable until Flutter paints its first frame, then this splash
                 screen fades out. A splash screen is useful to avoid any visual
                 gap between the end of Android's launch screen and the painting of
                 Flutter's first frame. -->
            <intent-filter>
                <action android:name="android.intent.action.MAIN"/>
                <category android:name="android.intent.category.LAUNCHER"/>
            </intent-filter>
        </activity>
        <!-- Don't delete the meta-data below.
             This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
        <meta-data
            android:name="flutterEmbedding"
            android:value="2" />
    </application>
</manifest>

排查与解决方案 #

1. 修复APK签名配置 #

当前release版本使用debug签名，部分Android 13设备对签名验证逻辑更严格，建议改用正式签名打包：

• 生成正式签名密钥：执行命令 keytool -genkey -v -keystore your-release-key.jks -keyalg RSA -keysize 2048 -validity 10000 -alias your-alias
• 在app/build.gradle中配置签名信息：

android {
    // ...其他配置
    signingConfigs {
        release {
            storeFile file('your-release-key.jks')
            storePassword 'your-keystore-password'
            keyAlias 'your-alias'
            keyPassword 'your-key-password'
        }
    }
    buildTypes {
        release {
            signingConfig signingConfigs.release
            // ...其他配置
        }
    }
}

• 重新执行 flutter build apk --release 生成正式签名APK后测试。

2. 确保APK支持多架构 #

默认情况下Flutter可能只打包当前开发机器对应的架构，导致部分Android 13设备（如arm32架构）无法兼容：

• 修改app/build.gradle的defaultConfig，添加ndk配置：

defaultConfig {
    // ...其他配置
    ndk {
        abiFilters 'armeabi-v7a', 'arm64-v8a', 'x86', 'x86_64'
    }
}

• 或直接用命令打包全架构APK：flutter build apk --release --split-per-abi，测试对应架构的APK。

3. 检查targetSdkVersion兼容性 #

targetSdkVersion设为34可能触发Android 13不兼容的系统特性，可临时降级测试：

• 修改app/build.gradle的defaultConfig：

defaultConfig {
    // ...其他配置
    targetSdkVersion 33
}

• 重新打包测试，若能安装再逐步排查targetSdk34带来的权限或配置变更问题。

4. 通过adb查看详细安装错误 #

直接用设备提示无法定位问题，可通过adb命令获取具体失败原因：

• 连接设备后执行 adb install your-app.apk，终端会输出详细错误信息（如签名错误、架构不兼容等），根据提示修复。

5. 清除设备残留应用数据 #

部分Android 13设备可能存在旧版本应用的残留数据，导致新安装失败：

• 在设备应用管理中搜索同名/同包名应用，彻底卸载后重新安装。

内容的提问来源于stack exchange，提问作者Hossein Shahbodaghkhan