-
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
Crash in datatransport com.google.android.datatransport.runtime.logging.Logging #3716
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Glad it's not just me! Had to immediately roll back to 29.3.1. Thanks for raising. |
Thanks for reporting, @gevorg-kopalyan, @darrentaft. I'll notify our engineers and see what we can do here. |
I am facing the same issue. I know this issue has been fixed in the source code but how can I as a Unity game developer using Firebase-SDK fix this issue? Has there been any new release that I can use? Either for Android or Unity. |
Hi @AliA74, we expect this fix to be in a release that is targeted for next week. You can keep an eye on our release notes for bug fixes and features. As for Firebase SDK for the Unity platform, afaik it should be available once it's been released for Android. |
How you guy's resolve this Crash |
I used ProGuard to remove isLoggable calls. Add something similar to your proguard file:
|
the fix for this has been released as part of BOM 30.0.2 https://firebase.google.com/support/release-notes/android#bom_v30-0-2 |
[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:
Getting crashes in google play console but not in Firebase Crashlytics
In com.google.android.datatransport:transport-runtime Library which firebase datatrasport library is using has a new Log.isLoggable() check which doesn't check for a tag limit of 23 characters and can produce crash.
Here is the pull request that added new Log.isLoggable check
The text was updated successfully, but these errors were encountered: