IssueTracker

apparently the issue is that newer glide versions will generate a com.bumptech.glide.GeneratedAppGlideModuleImpl class with context inside constructor

and google maps 3 will try to instantiate without passing the constructor -> hence the reflection exception. not sure how to fix that from the outside though, it would help if we knew the actual glide version they're using

here the glide generated class glide:

com.github.bumptech.glide:glide:4.11.0 com.github.bumptech.glide:compiler:4.11.0

@SuppressWarnings("deprecation")
final class GeneratedAppGlideModuleImpl extends GeneratedAppGlideModule {
  private final AppGlideModule appGlideModule;

  public GeneratedAppGlideModuleImpl(Context context) {
    appGlideModule = new AppGlideModule();
    if (Log.isLoggable("Glide", Log.DEBUG)) {
      Log.d("Glide", "Discovered AppGlideModule from annotation: com.europapark.services.glide.AppGlideModule");
      Log.d("Glide", "Discovered LibraryGlideModule from annotation: com.bumptech.glide.integration.okhttp3.OkHttpLibraryGlideModule");
      Log.d("Glide", "Discovered LibraryGlideModule from annotation: net.kibotu.mediagallery.internal.progress.GlideConfiguration");
    }
  }

  @Override
  public void applyOptions(@NonNull Context context, @NonNull GlideBuilder builder) {
    appGlideModule.applyOptions(context, builder);
  }

  @Override
  public void registerComponents(@NonNull Context context, @NonNull Glide glide,
      @NonNull Registry registry) {
    new OkHttpLibraryGlideModule().registerComponents(context, glide, registry);
    new GlideConfiguration().registerComponents(context, glide, registry);
    appGlideModule.registerComponents(context, glide, registry);
  }

  @Override
  public boolean isManifestParsingEnabled() {
    return appGlideModule.isManifestParsingEnabled();
  }

  @Override
  @NonNull
  public Set<Class<?>> getExcludedModuleClasses() {
    return Collections.emptySet();
  }

  @Override
  @NonNull
  GeneratedRequestManagerFactory getRequestManagerFactory() {
    return new GeneratedRequestManagerFactory();
  }
}

and here the call within the gmaps 3 library

private static com.google.android.libraries.maps.c.zza zzb() {
       com.google.android.libraries.maps.c.zza var0 = null;

       try {
           var0 = (com.google.android.libraries.maps.c.zza)Class.forName("com.bumptech.glide.GeneratedAppGlideModuleImpl").getDeclaredConstructor().newInstance();
       } catch (ClassNotFoundException var2) {
           if (Log.isLoggable("Glide", 5)) {
               Log.w("Glide", "Failed to find GeneratedAppGlideModule. You should include an annotationProcessor compile dependency on com.github.bumptech.glide:compiler in your application and a @GlideModule annotated AppGlideModule implementation or LibraryGlideModules will be silently ignored");
           }
       } catch (IllegalAccessException | NoSuchMethodException | InvocationTargetException | InstantiationException var3) {
           throw new IllegalStateException("GeneratedAppGlideModuleImpl is implemented incorrectly. If you've manually implemented this class, remove your implementation. The Annotation processor will generate a correct implementation.", var3);
       }

       return var0;
   }

This is still happening with glide 4.11.0

We tried understanding the issue, it seems that a glide module is generated through reflection:

Some thing like this

try {
            var0 = (com.google.android.libraries.maps.c.zza)Class.forName("com.bumptech.glide.GeneratedAppGlideModuleImpl").getDeclaredConstructor().newInstance();
        } catch (ClassNotFoundException var2) {
            if (Log.isLoggable("Glide", 5)) {
                Log.w("Glide", "Failed to find GeneratedAppGlideModule. You should include an annotationProcessor compile dependency on com.github.bumptech.glide:compiler in your application and a @GlideModule annotated AppGlideModule implementation or LibraryGlideModules will be silently ignored");
            }
        } catch (IllegalAccessException | NoSuchMethodException | InvocationTargetException | InstantiationException var3) {
            throw new IllegalStateException("GeneratedAppGlideModuleImpl is implemented incorrectly. If you've manually implemented this class, remove your implementation. The Annotation processor will generate a correct implementation.", var3);
        }  

Glide has a constructor of this method with context, but google tries to create an instance of this class without any parameters, that is why an exception is occurred.

Someone can think of a workaround or time till this is fixed?

The actual problem here is that Glide generates GeneratedAppGlideModuleImpl as package-private and when maps tries to use its own obfuscated, repackaged version of Glide to read it it blows up because its accessing it from a different package. If you look at the original issue the root cause is an IllegalAccessException.

The real question is: why not just depend on Glide?

The Maps SDK 3.1.0-beta is not able to access to the constructor of GeneratedAppGlideModuleImpl, if you call the reflection method isAccessible() you will get false So you need to fix it into Maps SDK. I have done some tests and you should be able to write some code like:

@Nullable
    private static com.google.android.libraries.maps.c.zza zzc(Context var0) {
        com.google.android.libraries.maps.c.zza var1 = null;

        try {
            Constructor<?> constructor = Class.forName("com.bumptech.glide.GeneratedAppGlideModuleImpl").getDeclaredConstructor(Context.class);
            constructor.setAccessible(true);
            var1 = constructor.newInstance(var0.getApplicationContext());
        } catch (ClassNotFoundException var3) {
            if (Log.isLoggable("Glide", 5)) {
                Log.w("Glide", "Failed to find GeneratedAppGlideModule. You should include an annotationProcessor compile dependency on com.github.bumptech.glide:compiler in your application and a @GlideModule annotated AppGlideModule implementation or LibraryGlideModules will be silently ignored");
            }
        } catch (IllegalAccessException | NoSuchMethodException | InvocationTargetException | InstantiationException var4) {
            throw new IllegalStateException("GeneratedAppGlideModuleImpl is implemented incorrectly. If you've manually implemented this class, remove your implementation. The Annotation processor will generate a correct implementation.", var4);
        }

        return var1;
    }

Only now I decide to checkout google maps v3 since I want to use it in Compose.... but this is great.... (together the use of the support lib)

I just integrated and was trying out maps v3 since I was facing OOM issues in v2 and ended up with this issue. Almost every developer I know uses Glide. If this issue is not fixed, will have to abandon the upgrade to v3. Team, please prioritise this and fix it. Thanks.

Thanks for patiently waiting.

Maps SDK for Android Beta version is now deprecated and will be fully decommissioned in late 2022. For more information, you can check our documentation here: https://developers.google.com/maps/documentation/android-sdk/releases#2021-08-18

Google has released a new client library for Maps SDK for Android, version 18.0.0 that we suggest that you try. You can also migrate your Beta SDK version to the latest version by using our migration tool here: https://github.com/googlemaps/android-v3-migration

If you have any issues using the latest version of the SDK, please let us know by either:

• Creating a new issue in https://issuetracker.google.com/issues/new?component=1124440&template=1632899&pli=1
• Creating a support case in the Google Cloud Console https://developers.google.com/maps/support/#creating-a-support-case