Let’s break down what this error actually means, why it’s usually harmless, and when you should actually worry about it. At its core, this log message comes from Dynamite Module Loading – Google’s internal system for dynamically loading code from the Google Play Services APK into your app at runtime.

When you see:

-keep class com.google.android.gms.** *; -dontwarn com.google.android.gms.** If you only included play-services-base but need play-services-auth or play-services-location , some modules won’t load.

adb logcat | grep -v "local module descriptor class" Or, in Android Studio Logcat, add this exclusion:

Add the standard Google Play Services ProGuard rules (usually automatic with com.google.gms:google-services plugin, but check manually):

The “local module descriptor class not found” message is Google’s way of saying “We didn’t bundle this module locally, but we’ll fetch it from the system.” That’s intentional and by design.