Android Studio 3.1构建失败：同包类签名信息不匹配求助

Hey there! I’ve run into similar dependency signature conflicts with LibGDX before, so let’s work through this together. Even though you didn’t explicitly add BouncyCastle, it’s almost certainly being pulled in indirectly by one of LibGDX’s core dependencies or extensions—and mismatched versions from different sources are causing that signature mismatch error.

Step 1: Track down where BouncyCastle is coming from #

First, let’s identify which dependencies are bringing in BouncyCastle. Run this command in your project root directory:

• On macOS/Linux: ./gradlew dependencies
• On Windows: gradlew.bat dependencies

Search the output for "bouncycastle"—you’ll see which modules (like gdx-backend-android or an extension) are pulling it in, and what versions they’re using. This helps confirm if multiple versions are clashing.

Step 2: Force a single, consistent BouncyCastle version #

Once you know the versions involved, force Gradle to use one stable version across all dependencies. Add this to your root project’s build.gradle file, inside the allprojects block:

allprojects {
    repositories {
        // Keep your existing repo config here (mavenCentral, etc.)
    }
    configurations.all {
        // Pick a recent, stable version—1.68 or 1.70 work well with older LibGDX versions
        resolutionStrategy.force 'org.bouncycastle:bcprov-jdk15on:1.68'
    }
}

Step 3: Clear build caches (often fixes weird signature issues) #

Old cached build files can cause unexpected conflicts. Let’s wipe them clean:

• Go to File > Invalidate Caches... in Android Studio, check "Invalidate and Restart" and confirm.
• Manually delete the .gradle folder in your project root, plus the build folder inside each module (android, core, etc.).
• After restarting, run a fresh Build > Clean Project followed by Build > Rebuild Project.

Step 4: Double-check signing configurations (just in case) #

Even if you didn’t set up custom signing, sometimes default configs can glitch. Head to File > Project Structure > Modules > [your Android module] > Signing Configs. Make sure the release config isn’t pointing to an invalid or mismatched keystore—you can temporarily set it to use the debug signing config to test if that resolves the issue.

Step 5: Update Gradle/Android Studio (if possible) #

Android Studio 3.1 is pretty outdated, and its bundled Gradle version might have dependency resolution bugs. If you can, upgrade Gradle to 4.10.1 (the latest compatible with AS 3.1) or consider updating Android Studio to a newer stable version—this often eliminates obscure build issues.

If none of these steps work, share the snippet from your dependencies output that shows BouncyCastle references, and we can dig deeper!

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