-
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
Crashlytics flaky de-obfuscation #4171
Comments
Thanks for reporting, @francescobonni. Just to ask some details that might be needed which was also asked from #3392:
|
@argzdev This is our debugging output. I runned the command both in ci and locally with the same result.
|
Hey @francescobonni. 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! |
Hey @argzdev, I shared under result the debugging result of gradle on my original post but @battagliandrea (my colleague) shared it again in a better way. In the meanwhile we triggered the CI with Gradle cache remote node disabled and purged, nothing changed. |
Thanks for the extra details, @francescobonni & @battagliandrea. This is odd since you're able to see the de-obfuscated logs in Google Play Console. I think this might be an issue on the project mapping or incorrect config file, but I'm not sure since this requires taking a look in your project details with the mapping file. That said, since this requires sharing PII it would be better to reach out to our Firebase support and reference them this issue, they'll be able to assist you better since they have more visibility on your project details. I'll close this issue for now. Feel free to comment back here if you feel this is a mistake or there's additional information that you think might help with the investigation. Thanks! |
@argzdev, I'd like to let you know that we've found a solution to our problem. We used the publishVariantName command (in the same pipeline) to publish on store, and the upload mapping was not called. |
Environment
Describe the problem
Half of our crashes on Firebase Crashlytics are obfuscated.
Screenshot Samples:
We've been afflicted by the problem since November/December 2021.
Steps and actions made:
> ./gradlew app:assembleRelease --debug | grep "\[com.google.firebase.crashlytics\]"
Result:
The problem looks similar to #3392 that was closed for inactivity.
Please let me know what other information you may need. Thank you!
The text was updated successfully, but these errors were encountered: