Google Mobile Ads SDK初始化错误导致应用启动崩溃求助

Hey there, let's work through this crash issue together!

First, let's zero in on the core problem from your crash log:

The Google Mobile Ads SDK was initialized incorrectly. AdMob publishers should follow the instructions here... to add a valid App ID inside the AndroidManifest.

Even though you never added ad-related code or the required <meta-data> tag, it’s clear one of your app’s dependencies is indirectly pulling in the Google Mobile Ads SDK. Starting from version 17.0.0 of this SDK, Google enforces that the APP ID is present in the manifest—even if you don’t plan to display ads. Missing this tag triggers the fatal crash you’re seeing.

Here are actionable steps to fix this: #

1. Find which dependency is bringing in the ads SDK

Run this Gradle command in your project root to generate a full dependency tree:

./gradlew app:dependencies

Or in Android Studio, go to View > Tool Windows > Gradle, expand your app module, and run Tasks > android > androidDependencies. Search the output for play-services-ads or play-services-ads-lite—this will reveal which third-party library is adding the ads SDK to your project.

2. Exclude the ads SDK from the problematic dependency

Once you’ve identified the culprit, add an exclusion rule in your app-level build.gradle to remove the unwanted ads dependency. For example:

implementation('com.example.third-party-library:1.2.3') {
    exclude group: 'com.google.android.gms', module: 'play-services-ads-lite'
    exclude group: 'com.google.android.gms', module: 'play-services-ads'
}

This will prevent the ads SDK from being included in your app, eliminating the need for the manifest tag entirely.

3. If exclusion isn’t possible, add the test APP ID to your manifest

If the third-party library requires the ads SDK to function, you can add Google’s official test APP ID to your AndroidManifest.xml (inside the <application> tag). This satisfies the SDK’s initialization requirement without serving real ads:

<meta-data
    android:name="com.google.android.gms.ads.APPLICATION_ID"
    android:value="ca-app-pub-3940256099942544~3347511713"/>

This test ID is safe for development and won’t trigger any ad-related behavior.

4. Clean and rebuild your project

After making either change, go to Build > Clean Project in Android Studio, then rebuild your app. It should launch without crashing now.

If you struggle to pinpoint the problematic dependency, feel free to share a snippet of your dependency tree—I can help narrow it down further!

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