使用Product Flavors启动Activity时提示“应用未安装”，求建议

Hey there, let's work through this frustrating "Application not installed" issue you're facing when launching an Activity with Product Flavors. Based on the Gradle config you shared, here are actionable checks and fixes to try:

1. Ensure Unique Application IDs for Each Flavor #

Your defaultConfig sets a base applicationId, but if your Product Flavors don't define unique identifiers, different flavor variants might clash with each other (or the base app). Update your productFlavors block to give each flavor a distinct application ID:

productFlavors {
    demo {
        applicationIdSuffix ".demo" // Adds a suffix to the base ID
        // OR directly set a unique ID: applicationId "com.company.appname.demo"
    }
    full {
        applicationIdSuffix ".full"
    }
}

This ensures the system can distinguish between different flavor APKs, preventing installation/launch conflicts.

2. Verify You're Launching the Correct Build Variant #

It's easy to accidentally select the wrong variant in Android Studio. Head to the Build Variants panel (View > Tool Windows > Build Variants) and confirm you've selected the specific flavor + build type you want to test (e.g., demoDebug or fullRelease). Rebuild and reinstall after making the change.

3. Clean & Rebuild Your Project #

Cached build artifacts often cause weird installation issues. Run these steps to wipe old files and start fresh:

• Click Build > Clean Project in Android Studio
• Follow with Build > Rebuild Project
• Alternatively, use the command line:

  ./gradlew clean assemble<Flavor><BuildType>
  

  Replace <Flavor> and <BuildType> with your target variant (e.g., ./gradlew clean assembleDemoDebug).

4. Uninstall Conflicting Old App Versions on the Device #

If you previously installed the base app (without flavors) or a different flavor variant, the same base package name might block the new installation. Go to your device's Settings > Apps, find all instances of com.company.appname, uninstall them, then try reinstalling your target flavor APK.

5. Dig Into Installation Logs for Details #

The generic "Application not installed" message hides the real issue. Use ADB to get detailed logs:

adb logcat | grep -i "install"

Or filter the Logcat panel in Android Studio for "install" to find specific errors—common culprits include signature mismatches, missing permissions, or SDK version incompatibilities.

6. Check Signing Config Consistency #

Your release build type uses signingConfigs.debug, but if your flavors have conflicting signing setups, or you're trying to install a build with a different signature than a previously installed version, this will fail. Ensure all variants you test use consistent signing configs, or fully uninstall old versions before installing a build with a new signature.

If none of these steps resolve the issue, sharing the full productFlavors block from your Gradle config would help pinpoint the exact problem.

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