Android应用设minSDKVersion19，Marshmallow无法安装Nougat正常，如何解决？

Hey there! Let’s dig into why your app won’t install on Marshmallow (API 23) devices, even though it works fine on Nougat and newer. Since you’ve set minSDKVersion to 19, there are several common issues we can check step by step:

1. Verify Target & Compile SDK Versions #

First, open your module-level build.gradle file and check these critical values:

• compileSdkVersion: Ensure it’s at least 23 (Marshmallow’s API level). If it’s set to a much higher version (like 33+), double-check that you aren’t using APIs introduced after API 23 without adding compatibility checks or fallback logic.
• targetSdkVersion: If this is set to 30 or above, confirm you’re handling runtime permissions correctly (Marshmallow was the first version to require runtime permission requests for dangerous permissions). While this usually causes runtime crashes instead of installation failures, improper permission declarations can sometimes block installs.

2. Audit Your Manifest File #

Look for these potential red flags in your AndroidManifest.xml:

• Required Features: Check for <uses-feature> tags with android:required="true" that reference features not available on all Marshmallow devices. For example, if you’re forcing android.hardware.camera.autofocus, some older Marshmallow phones might lack this, blocking installation.
• Unsupported Permissions: If you’ve added permissions introduced after API 23 (like MANAGE_EXTERNAL_STORAGE from API 30) without specifying android:maxSdkVersion, this can cause conflicts on older OS versions. Add maxSdkVersion to limit such permissions to compatible versions.
• Install Location: Ensure android:installLocation isn’t set to internalOnly if the Marshmallow device’s internal storage is full. Switching to auto or preferExternal might help.

3. Check APK Signing Configuration #

Even though your app installs on Nougat, signature inconsistencies can behave differently on older Android versions:

• Enable both V1 and V2 signing schemes in your build.gradle (Marshmallow supports V2, but some early Marshmallow builds have issues with V2-only signing):

  android {
      ...
      signingConfigs {
          release {
              keyAlias 'your_key_alias'
              keyPassword 'your_key_password'
              storeFile file('your_keystore.jks')
              storePassword 'your_store_password'
              v1SigningEnabled true
              v2SigningEnabled true
          }
      }
      ...
  }
  

• Confirm you’re using the exact same keystore and credentials for the signed APK you’re testing.

4. Ensure ABI Compatibility #

If you’re building for specific CPU architectures, your Marshmallow device might not support the ABI you’ve targeted:

• In build.gradle, check the ndk.abiFilters setting and include all relevant architectures for older devices:

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

• If using App Bundles, make sure the generated APK includes the correct ABI for your Marshmallow test device.

5. Verify Unknown Sources Setting #

Marshmallow requires users to enable "Unknown Sources" to install apps outside the Google Play Store. Double-check this on your test device:

Go to Settings > Security > Unknown Sources and toggle the option on.

6. Get Detailed Installation Logs #

If none of the above fixes work, grab the installation log to pinpoint the exact error:

1. Connect your Marshmallow device to your computer.
2. Open Android Studio’s Logcat.
3. Filter logs by the PackageManager tag.
4. Attempt to install the APK again.

The log will show a specific error code (like INSTALL_FAILED_MISSING_FEATURE or INSTALL_FAILED_INVALID_APK) that will tell you exactly what’s blocking the installation.

If you share snippets of your manifest and build.gradle files, I can help narrow down the issue even faster!

内容的提问来源于stack exchange，提问作者Aditya Singh