[Bug] Duplicate class com.google.android.gms.internal.firebase_messaging.zza found in modules jetified-firebase-iid-20.0.1-runtime.jar (com.google.firebase:firebase-iid:20.0.1) and jetified-firebase-messaging-22.0.0-runtime.jar (com.google.firebase:firebase-messaging:22.0.0)

[mikeypdev]

[REQUIRED] Please fill in the following fields:

• Unity editor version: 2020.3.6f1
• Firebase Unity SDK version: 8.0.0
• Source you installed the SDK: Unity Package Manager
• Problematic Firebase Component: InstanceID
• Other Firebase Components in use: Analytics, Auth, Crashlytics, Database, DynamicLinks, Functions, Messagin, RemoteConfig, Storage
• Additional SDKs you are using: Unity IAP
• Platform you are using the Unity editor on: Mac
• Platform you are targeting: Android, iOS
• Scripting Runtime: IL2CPP

[REQUIRED] Please describe the issue here:

Firebase Instance ID is deprecated, and I was not using it, so I removed the Instance ID SDK from my project when updating to SDK 8.0.0. In SDK 7.2.0, Instance ID implemented firebase-iid:21.1.0 on Android, as seen in mainTemplate.gradle. After removing Instance ID, and upgrading all other Firebase components to 8.0.0, there are no references to firebase-iid in mainTemplate.gradle or AndroidResolverDependecies.xml, as expected.

However, when building to Android, the gradle build fails with the following error:
Duplicate class com.google.android.gms.internal.firebase_messaging.zza found in modules jetified-firebase-iid-20.0.1-runtime.jar (com.google.firebase:firebase-iid:20.0.1) and jetified-firebase-messaging-22.0.0-runtime.jar (com.google.firebase:firebase-messaging:22.0.0)
I do not know where the reference to firebase-iid:20.0.1 is coming from.

As a workaround, I am able to solve the build error by manually adding a reference to firebase-iid:21.1.0 to my mainTemplate.gradle file:
implementation 'com.google.firebase:firebase-iid:21.1.0'

This is reproducible 100% of the time in my project, on two different development systems. I have not yet had the bandwidth to repro in any Quickstart example.

[paulinon]

Hi @mikeypdev,

This seems like a bug related to the dependencies. Could you provide the complete steps you've taken before facing this issue so that we can confirm this?

[mikeypdev]

Before updating to 8.0.0, I updated from 7.1.0 to 7.2.0 (this was 2 months ago). In the process of updating from 7.1.0 to 7.2.0, I removed the deprecated Google Game Package Registry from UPM, and migrated to local tgz files. I did the upgrade entirely outside of Unity, by manually adding a project-level GooglePackages folder containing the Firebase 7.2.0 and EDM tgz files and then updating Packages/manifest.json to remove the scopedRegistries entry for Google Game Package Repository, and update each Firebase SDK entry to point to the new local tgz files.

I seem to recall trying to remove the InstanceID SDK at the time, and getting some errors. I'm afraid I don't remember the issue, as I decided it was easier to leave the SDK in place. I was able to move forward without further issues.

In the process of updating from 7.2.0 to 8.0.0, I replaced the Firebase and EDM tgz files and manually updated Packages/manifest.json. I then encountered the Instance ID conflict when building for Android. I did not see any conflict or errors for Desktop or iOS builds. At this point, I was not using a custom gradle file for Android builds, so I enabled it in my project settings and EDM settings, did the upgrade from 7.2.0 to 8.0.0 again, and was then able to implement the workaround I noted above.

[paulinon]

Hi @mikeypdev,

Could you try going to Assets > External Dependency Manager > Android Resolver > Force Resolve and see if the issue persists?

[visioncored]

I am also facing this issue after updating from 7.2.0 to 8.1.0.

Tried doing Force Resolve via Assets > External Dependency Manager > Android Resolver > Force Resolve, but the issue still persists. I realised there is a change in Android Resolver Dependencies xml file.

I had attached the two dependencies files, not sure if it helps.

AndroidResolverDependenciesOld.txt

AndroidResolverDependenciesNew.txt

[thsbrown]

Also facing this issue. Also, @paulinon tried Force resolving with no fix. Seems like another case of dependency hell with firebase & unity 😭 .

Strange thing as far as my project is concerned is that I'm not using InstanceId anywhere in my project 🤔 .

[mikeypdev]

@paulinon I can confirm that Force Resolve does not fix the issue for me. The workaround that I noted above is still required.