FCM推送通知在KitKat版本无法正常工作

Hey there, I’ve dealt with this exact FCM crash issue on pre-Lollipop devices before—let’s break down the most likely fixes step by step:

1. Fix Firebase Messaging Dependency Version #

Google raised the minimum API level for newer Firebase Messaging versions. For KitKat (API 19) and below, you’ll need to use a version that supports older devices. The latest version compatible with API 16+ is 20.3.0 (versions 21.0.0+ require API 21). Update your app-level build.gradle:

dependencies {
    // Replace with this compatible version
    implementation 'com.google.firebase:firebase-messaging:20.3.0'
}

2. Check Google Play Services Availability #

FCM relies on Google Play Services (GMS), which might be missing or outdated on older devices. Add a check early in your app to avoid crashes:

import com.google.android.gms.common.GoogleApiAvailability;

// Call this in your Activity or Application onCreate
private void checkPlayServices() {
    GoogleApiAvailability apiAvailability = GoogleApiAvailability.getInstance();
    int resultCode = apiAvailability.isGooglePlayServicesAvailable(this);
    if (resultCode != com.google.android.gms.common.ConnectionResult.SUCCESS) {
        if (apiAvailability.isUserResolvableError(resultCode)) {
            // Show dialog to update GMS
            apiAvailability.getErrorDialog(this, resultCode, 9000).show();
        } else {
            Log.d("FCMCheck", "This device doesn't support Google Play Services—FCM won't work.");
        }
    }
}

3. Verify Manifest Permissions & Service Registration #

Pre-Lollipop devices require specific permissions and correct service declarations. Double-check your AndroidManifest.xml:

<!-- Required permissions -->
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="com.google.android.c2dm.permission.RECEIVE" />

<!-- Custom C2D permission (match your app's package name) -->
<permission
    android:name="your.app.package.permission.C2D_MESSAGE"
    android:protectionLevel="signature" />
<uses-permission android:name="your.app.package.permission.C2D_MESSAGE" />

<!-- Register your Firebase Messaging Service -->
<service
    android:name=".MyFirebaseMessagingService"
    android:exported="false">
    <intent-filter>
        <action android:name="com.google.firebase.MESSAGING_EVENT" />
    </intent-filter>
</service>

4. Capture Crash Logs Properly #

If your app’s logcat isn’t showing the crash, it might be happening in a system or GMS process. Try these steps:

• Run adb logcat *:E in your terminal to filter all error-level logs (including system processes).
• Add a global exception handler in your Application class to catch uncaught exceptions:

public class MyApp extends Application {
    @Override
    public void onCreate() {
        super.onCreate();
        Thread.setDefaultUncaughtExceptionHandler((thread, throwable) -> {
            Log.e("FCMCrash", "Uncaught exception", throwable);
            // Optional: Write the stack trace to a file for later analysis
        });
    }
}

5. Adjust ProGuard Rules (If Enabled) #

If you’re using ProGuard, it might be obfuscating FCM-related classes. Add these rules to proguard-rules.pro:

-keep class com.google.firebase.** { *; }
-keep class com.google.android.gms.** { *; }
-keepclassmembers class * extends com.google.firebase.messaging.FirebaseMessagingService {
    public void onMessageReceived(com.google.firebase.messaging.RemoteMessage);
}

Start with these steps—most likely the dependency version or missing GMS check is causing the crash. Let me know if you find the root cause!

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