AdMob与Firebase异常及应用崩溃跳转至其他Activity问题求助

Hey there, let's tackle this AdMob/Firebase crash issue you're facing with the error unexpected number of IObjectWrapper declared fields: 3 and the unexpected Activity jump. Here are the most practical fixes that should resolve this:

This error usually pops up when there's a version mismatch between Google Play Services and Firebase libraries.

• Use the Firebase Bill of Materials (BOM) to auto-align all Firebase dependency versions, and ensure your AdMob library matches the compatible version:

  // In your module-level build.gradle
  implementation platform('com.google.firebase:firebase-bom:32.7.0') // Use latest stable version
  implementation 'com.google.firebase:firebase-analytics'
  implementation 'com.google.android.gms:play-services-ads:22.6.0' // Match version compatible with Firebase BOM
  

• Avoid mixing different versions of any Google Play Services or Firebase libraries—stick to a consistent version set.

Stale build cache often causes class/method mismatches like this:

• Run Build > Clean Project in Android Studio, then follow with Build > Rebuild Project.
• For a deeper clean, manually delete the build folder in your app module and the .gradle folder in your project root, then re-sync your Gradle files.

Conflicting duplicate libraries can trigger this field count error:

• Use Android Studio's Dependency Analyzer (go to File > Project Structure > Dependencies) to scan for duplicate play-services-base or IObjectWrapper related libraries.
• If duplicates are found, exclude the conflicting module, for example:

  implementation('com.google.android.gms:play-services-ads:22.6.0') {
      exclude group: 'com.google.android.gms', module: 'play-services-base'
  }
  

Incorrect obfuscation might be altering critical classes:

• Add these rules to your proguard-rules.pro to protect AdMob/Firebase core classes:

  -keep class com.google.android.gms.common.** { *; }
  -keep class com.google.android.gms.ads.** { *; }
  -keep class com.google.firebase.** { *; }
  

• To test, temporarily disable obfuscation and run the app—if the crash stops, your ProGuard rules were the issue.

For the unexpected Activity navigation after crash:

• Check your custom UncaughtExceptionHandler (if you have one) for any incorrect Activity launch code that might be triggering on crash.
• Pull the full crash stack from Logcat to pinpoint where the navigation is initiated—this will help you fix the faulty logic.
• Ensure all Activity launches use valid context and are only triggered in intended flows, not in unhandled exception callbacks.

Outdated build tools can clash with modern Google libraries:

• Update Android Studio to the latest stable version.
• Upgrade your Gradle plugin and Android Build Tools versions to match the recommended versions for your Firebase/AdMob libraries.

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