-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NoSuchMethodError FirebaseCrashlyticsNdk class is included in your app. #1177
Comments
Same here, but Unity 2020.3.22:
|
Same Problem with Unity 2019.4.30 Unable to find Method com/google/firebase/crashlytics/ndk/FirebaseCrashlyticsNdk.getInstance (signature '()Lcom/google/firebase/crashlytics/ndk/FirebaseCrashlyticsNdk;', static). Please verify the AAR which contains the com/google/firebase/crashlytics/ndk/FirebaseCrashlyticsNdk class is included in your app. method_ids[i] || (method.optional == kMethodOptional) |
Thanks for reporting this, @keepup. May I know how this issue could be replicated so that we can identify what's causing this? Could you also confirm if your implementation is using the IL2CPP scripting backend? |
Hi @keepup & @AjayC-Bsw, it looks like the version of Crashlytics for Android didn't get updated with this release of our Unity SDK. The following workaround should resolve the problem: Open This will cause the dependency resolver to download the correct version of the Crashlytics Android SDK, which includes the missing method identified in the error message. Subsequent builds should work as expected. Our next release will include the correct dependency version, so this workaround will not be required in the future. |
The workaround seems to work nicely. I still have to check the actual crash reporting functionality after this upgrade, but this brings me a lot closer. Thanks a lot @mrichards
|
We've just released a new version, 8.6.1, which has the correct |
[REQUIRED] Please fill in the following fields:
[REQUIRED] Please describe the question here:
This is logs:
The text was updated successfully, but these errors were encountered: