crashlytics :Please verify the AAR which contains the com/google/firebase/crashlytics/internal/common/DataCollectionArbiter class is included in your app

[Zhangyu754178]

Please fill in the following fields:

Unity editor version:
Firebase Unity SDK version: 6.15.2
Source you installed the SDK (.unitypackage or Unity Package Manager):FirebaseCrashlytics.unitypackage
Firebase plugins in use (Auth, Database, etc.):Catch Crash
Additional SDKs you are using (Facebook, AdMob, etc.):
Platform you are using the Unity editor on (Mac, Windows, or Linux): Mac
Platform you are targeting (iOS, Android, and/or desktop): Android
Scripting Runtime (Mono, and/or IL2CPP):IL2CPP

Please describe the issue here:

2020-08-19 14:27:25.588 25005-25377/onnect.connect.pair.matching.line.puzzle.match3d.tilemaster W/System.err: java.lang.NoSuchMethodError: no non-static method "Lcom/google/firebase/crashlytics/internal/common/DataCollectionArbiter;.setCrashlyticsDataCollectionEnabled(Z)V"
2020-08-19 14:27:25.588 25005-25377/onnect.connect.pair.matching.line.puzzle.match3d.tilemaster E/firebase: method_ids[i] || (method.optional == kMethodOptional)
2020-08-19 14:27:25.589 25005-25377/onnect.connect.pair.matching.line.puzzle.match3d.tilemaster E/firebase: Unable to find Method com/google/firebase/crashlytics/internal/common/DataCollectionArbiter.setCrashlyticsDataCollectionEnabled (signature '(Z)V', instance). Please verify the AAR which contains the com/google/firebase/crashlytics/internal/common/DataCollectionArbiter class is included in your app.

Please answer the following, if applicable:

Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
Yes
What's the issue repro rate? (eg 100%, 1/5 etc)

[napbla]

I were also having this problem.
It is caused by the latest version of 'com.google.firebase.firebase-crashlytics-17.2.1' where they change the method name while the Unity wrapper 'com.google.firebase.firebase-crashlytics-unity-6.15.2' is not updated yet. Ref: (https://firebase.google.com/support/release-notes/android#crashlytics_v17-2-1)

Android resolver somehow automatically change the version in CrashlyticsDependencies.xml to the latest version which is troublesome. (I have check all *Dependencies.xml files and not a single file use .+ )

If you export to Android project, you can temporarily solve this by changing 'com.google.firebase.firebase-crashlytics-17.2.1' to 'com.google.firebase.firebase-crashlytics-17.1.1' in your Android project manifest and manually download version 17.1.1 aar from Maven: (https://mvnrepository.com/artifact/com.google.firebase/firebase-crashlytics/17.1.1)
Then put it in the Android project's "libs" folder.

If you export to apk or aab, go to Assets/Plugins/Android to find and replace the aar. Do not run Android Resolver again. You may have to change these file to the correct version too: ProjectSettings/AndroidResolverDependencies.xml and CrashlyticsDependencies.xml

UPDATE: You can simply solve this by downloading the old version and RENAME it to 17.2.1 then copy into Assets\Plugins\Android folder overwrite the real one.

[ronrejwan]

Can confirm this is happening for us as well.
Thanks @napbla; you saved me hours.

[cynthiajoan]

Hi all, first thanks @napbla pointing out a manual modification to get unblocked.

I tried to repro the issue locally, and find out unity sdk 6.15.2 is pointing to com.google.firebase.firebase-crashlytics-17.0.0 in the CrashlyticsDependency.xml, and android resolver should only read from that info instead of modify that file. We'd like to understand if there's other 3rd party libraries used, and if can provide some environment for us to repro the issue, that will be really appreciated.

[mgrogin]

Hi all, first thanks @napbla pointing out a manual modification to get unblocked.

I tried to repro the issue locally, and find out unity sdk 6.15.2 is pointing to com.google.firebase.firebase-crashlytics-17.0.0 in the CrashlyticsDependency.xml, and android resolver should only read from that info instead of modify that file. We'd like to understand if there's other 3rd party libraries used, and if can provide some environment for us to repro the issue, that will be really appreciated.

@cynthiajoan For me it looks like the ironsource admob adapter changes the version when resolving Android dependencies:
Task :process_com.ironsource.adapters.admobadapter-4.3.12.aarWARNING: Some conflicting dependencies were found. The following dependency versions were modified: ... ... com.google.firebase:firebase-analytics:17.4.1 --> com.google.firebase:firebase-analytics:+ com.google.firebase:firebase-auth:19.3.1 --> com.google.firebase:firebase-auth:+ com.google.firebase:firebase-common:19.3.0 --> com.google.firebase:firebase-common:+ com.google.firebase:firebase-config:19.1.4 --> com.google.firebase:firebase-config:+ com.google.firebase:firebase-crashlytics:17.0.0 --> com.google.firebase:firebase-crashlytics:+ com.google.firebase:firebase-database:19.3.0 --> com.google.firebase:firebase-database:+ com.google.firebase:firebase-messaging:20.1.7 --> com.google.firebase:firebase-messaging:+

It's probably related to the ISAdMobAdapterDependency: com.google.android.gms:play-services-ads:19.3.0

[pigerj]

@cynthiajoan for me this case happens when using firebase analytics,remote config,crashlytics + Facebook Audience Network https://developers.facebook.com/docs/audience-network/guides/adding-sdk/unity/

[napbla]

Hi all, first thanks @napbla pointing out a manual modification to get unblocked.

I tried to repro the issue locally, and find out unity sdk 6.15.2 is pointing to com.google.firebase.firebase-crashlytics-17.0.0 in the CrashlyticsDependency.xml, and android resolver should only read from that info instead of modify that file. We'd like to understand if there's other 3rd party libraries used, and if can provide some environment for us to repro the issue, that will be really appreciated.

Android resolver try to resolve using 17.0.0 if it does not work it will try 17.0.+ and so on 17.+
That's why it ends up in 17.2.1.
Sorry I did not have time to investigate the long verbose log to see which one did cause the problem.

Here are the lists of all 3rd party plugins that our project uses:

• Firebase Analytics 6.15.2
• Firebase Auth 6.15.2
• Firebase Crashlytics 6.15.2
• Firebase InstanceId 6.15.2
• Firebase Remote Config 6.15.2
• Google Admob Mediation Plugins For Vungle
• Google Admob Mediation Plugins For Unity Ads
• Google Admob Mediation Plugins For AppLovin
• Google Admob Mediation Plugins For Facebook Ads

If you need more information just ask me. Thank you for your help.

[google-oss-bot]

Hey @Zhangyu754178. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[mgrogin]

Hey @Zhangyu754178. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

What other information do you need?
Please see my comment where I write what causes the problem for me #758 (comment)