-
Notifications
You must be signed in to change notification settings - Fork 578
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
firebase-crashlytics-gradle:2.9.5 not working #4912
Comments
Same issue |
Hi @ber4444, thanks for reporting. While our engineers are taking a look into this. I tried creating a new project with NDK setup with the Firebase Crashlytics plugin version
I've tried testing these commands on both Android Studio version:
I've also tried testing this on AGP & Gradle plugin versions:
Not sure what I'm missing here. Could you help me reproduce this issue? |
We are using 8.1 alpha, please try with that |
Same problem with the 2.9.5 plugin (Android Studio Electric Eel | 2022.1.1 Patch 2) , call stack is below:
|
We are aware of this issue. The work around is to continue to use version 2.9.2 for now. We are doing some internal refactoring to make the Crashlytics Gradle plugin more stable. I will post an artifact here when it is ready, so you don't have to wait for another release. |
Hi folks, we build a preview fix for this issue. Feel free to try this out now instead of waiting for the next release. You can download and unzip the m2repository.zip and then add it to your build by doing something like:
(for kts use And then use the plugin by
|
With |
Android Studio Flamingo | 2022.2.1 FAILURE: Build failed with an exception.
|
Hi,@mrober,Same issue by use v2.9.6-alpha.The issue seems not be related to android studio version.I have tried to do it with android studio v2022.2.1 and v2022.1.1. AGP & Gradle plugin versions: |
I am having the same issue. That is why people are leaving android development. You spend hours in figuring out Gradle and libraries issues.. |
Hi folks, by same issue do you mean the original issue "Cannot invoke method map() on null object" or the NoClassDefFoundError issue mentioned a few comments up? I tried to reproduce the NoClassDefFoundError but cannot, even on a fresh app using all Android Studio defaults. The build tools is a fat jar that contains the httpclient, and I confirmed it is present in the artifact I posted. The only thing I can think of is maybe there is a conflict between it and other dependencies in your app? Would you be willing to send all your gradle build files to Firebase support and mention me mrober, so I can take a deeper look? |
With |
@mrober the original issue "Cannot invoke method map() on null object" |
Thanks @Zayankovsky and @rmmmmm41 I am looking into this now. I am still unable to reproduce it. And I am surprised by that issue since I did a small refactor in 2.9.6-alpha and InjectBuildIdsTask does not call |
@mrober this is the full error output I get when
|
Thanks for the stacktrace @Zayankovsky, the The disassembled bytecode you showed is a bit hard to read, so I am not sure what that does. |
@mrober I use |
@Zayankovsky that was it, thanks! Here is the proper artifact m2repository.zip. Sorry about that, I must have uploaded an earlier version of the artifact before. I double checked this one has the fix, please confirm this resolves the issue for you. Unfortunately this won't go out in the next release because I hadn't verified it in time, so it will be included in the next-next release. |
Thanks,it works for me. |
Works for me as well. |
Thanks everyone! This fix will go out in the next-next release in a few weeks. If any other problems pop up with this artifact feel free to reopen this issue. |
@mrober Hello, any ota about next release? |
This is released now in 2.9.6. |
[READ] Step 1: Are you in the right place?
Yes
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Build fails, current workaround is to downgrade to as far back as 2.9.2 due to separate bugs in previous versions
Relevant Code:
usage of the plugin:
The text was updated successfully, but these errors were encountered: