Execution failed for task ':app:generateCrashlyticsSymbolFileRelease'. > java.lang.NullPointerException (no error message) #1396
Assignees
Labels
Comments
|
Hi @vokilam ! Thanks for the report. Sorry for the delay in response here - can you let me know which version of the NDK tools you're using to build this project so I can make sure my environment is the same as yours when trying to reproduce this? |
|
Also, are you building on Mac, Windows, or Linux? |
Default NDK: v20.0.5594570
Mac |
|
Great, thanks. I'll let you know what I find. |
|
Hi @vokilam! Thanks for the reproduction case! I was able to find and fix the issue causing this NPE, and the fix will be available in the next release of the Crashlytics Gradle plugin. |
|
@mrwillis21, thanks for Your support! But can we do something for now to upload symbols to avoid this error (maybe some additional settings or code)? Or we need use the old Fabric NDK plugin till next Firebase Crashlytics NDK release? Thanks. And the next version, in which it will be resolved, meant to be 2.0.1? I tested this on 2.0.0 (Crashlytics NDK - 17.0.0) release version and problem still there. |
|
Hi everyone - Circling back to let you know the Firebase Crashlytics Gradle plugin version 2.1.0 has been released with the fix for this issue. Please try it out and let me know how it goes! https://firebase.google.com/support/release-notes/android#crashlytics_gradle_plugin_v2-1-0 |
|
I just tried this with the updated Gradle plugin but unfortunately essentially the same result (see below). I’m using the following plugin versions:
Please let me know if I can provide any further info. |
|
Thanks for letting me know, @triplef. That's definitely unexpected. I suspect a separate issue from the one posted by @vokilam, unfortunately. I'm going to take a look and see if I can determine what the cause is based on your stack trace, but would you mind reaching out to the Firebase support team -- https://firebase.google.com/support/troubleshooter/contact -- so we can better coordinate on getting more information about your particular build? Please link to this issue so the support team can see the conversation. Thanks so much! |
|
I can confirm the issue revealed by @vokilam's test project is fixed, but if anyone else is still having issues, please let me know. |
|
Thanks @mrwillis21. I guess this means that my original issue #1357 is not a full duplicate of this after all. I already reached out to the support team (case 00044423). |
|
Great, thanks @triplef. I'll continue tracking this issue here, and I'll follow up with our support team on your case to see if we can disambiguate the issues. |
|
Hi @vokilam and @personshelldon! I'm going to close this issue given the release of Crashlytics Gradle plugin 2.1.0, but feel free to reopen if you continue to have problems. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
My goal is to configure readable stack traces of native crashes in firebase console.
I started with a simple hello-jni project in order to minimize real project environment issues.
Currenlty, I am able to see native crashes in firebase console in a following format:
After that I tried to execute following in order to upload native symbols
assembleReleaseis successfull, howeverapp:uploadCrashlyticsSymbolFileReleasefailed with the following error (--stacktrace)Please, help me understand the problem. Refer to sample project to reproduce the issue.
The text was updated successfully, but these errors were encountered: