Android新手求助：遇NoSuchMethodError及RuntimeException启动失败

Hey there! Let's tackle your two Android errors step by step to get your activity running smoothly again.

1. Fixing java.lang.NoSuchMethodError: No static method getFont(...) #

This error almost always boils down to version mismatches or dependency conflicts with AppCompat (or AndroidX) libraries. The getFont() method was introduced in AppCompat 26.0.0, so if your setup is out of sync, it'll throw this error on older devices (or even newer ones if dependencies are mixed up).

Here's how to fix it:

• Align your library versions: Open your app's build.gradle file and make sure your appcompat dependency version matches your compileSdkVersion. For example, if you're using compileSdk 33, use the latest compatible AppCompat version:

  dependencies {
      implementation 'androidx.appcompat:appcompat:1.6.1' // Match compileSdk version
  }
  

• Avoid mixing Support and AndroidX libraries: If you've migrated to AndroidX, double-check that no old com.android.support: libraries are left in your dependencies. Use Android Studio's Refactor > Migrate to AndroidX tool if you haven't already.
• Check minSdkVersion: If your minSdk is below 26, ensure your AppCompat version supports it (most modern AppCompat versions do, but keeping versions aligned still helps).

2. Fixing java.lang.RuntimeException: Unable to start activity ComponentInfo #

This is a generic "activity failed to launch" error, and it's often a side effect of the first error. Once you fix the getFont() issue, this might disappear on its own. But if it persists, dig into the Caused by section of your LogCat—it'll tell you exactly what went wrong during initialization.

Common fixes here:

• Check your Activity's onCreate() logic: Make sure you're not trying to access UI elements before calling setContentView(), and that all findViewById() calls target valid IDs from your layout.
• Verify layout resources: Ensure your XML layout doesn't reference missing assets (like fonts, drawables, or strings) or use attributes that aren't compatible with your AppCompat setup (use app: prefix instead of android: for AppCompat-specific attributes like fontFamily).
• Clean and rebuild your project: Sometimes cached build files cause weird issues. Go to Build > Clean Project then Build > Rebuild Project to rule this out.

Quick Build.Gradle Sanity Check #

Make sure your core Android block looks something like this (adjust versions to match your project):

android {
    compileSdk 33

    defaultConfig {
        applicationId "com.your.app.package"
        minSdk 21
        targetSdk 33
        versionCode 1
        versionName "1.0"
    }

    buildFeatures {
        viewBinding true // Optional, but helps avoid findViewById errors
    }
}

If you still run into issues, share the full Caused by stack trace from your LogCat— that'll help narrow down the exact root cause even more!

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