-
Notifications
You must be signed in to change notification settings - Fork 616
zzee.java line 1 com.google.android.gms.internal.measurement.zzee.zzg #4438
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
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Thanks for reporting, @mohanK22. Any code snippets you can share that's related to Firebase Analytics? It might give us a hint to what's causing the issue. |
we are initializing the Firebase in the application class on the
For Firebase Analytics, we have created a common class.
|
Thanks for the code snippet, @mohanK22. From what I can tell with your code snippet it shouldn't cause any issues. While I investigate this, may I ask if you also observed this issue on a previous version of Analytics? |
This ANR started causing issues from the analytics version "21.1.0". so we updated the library version "21.2.0". Now it is also causing in the latest build. fyi -- Earlier we were using "20.1.2" which was completely working fine with no ANR and no crash. |
Thanks for the extra details, @mohanK22. Checking our release notes, I noticed that there are 2 changes before your ANR started.
Are you using any of the following deprecated ecommerce constants? If not, then most likely the changes for The following constants were removed from FirebaseAnalytics.Event:
The following constants were removed from FirebaseAnalytics.Param:
|
Hey @mohanK22. 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! |
Hi @argzdev, |
Then the issue might be with |
Hi @mohanK22, sorry for the long wait. May I know which Firebase Crashlytics version are you using? Upon our investigation, it seems that the issue might be related to #4345. This is currently being worked out, so let's leave this issue open for now and see if this gets resolved once the fix for Crashlytics is out. |
Hey @mohanK22. Just bumping this thread, it seems that there has been updates with out libraries for sometime now. Can you try using our latest version and see if it helps? |
Hey @mohanK22. 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! |
Since there haven't been any recent updates here, I am going to close this issue. @mohanK22 if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this. |
[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs in the code in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:
with the firebase tag.
google group.
of the above categories, reach out to the personalized
Firebase support channel.
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Hi,
we are getting the root blocking ANR issue on the release build, reported on the Firebase Crashlytics Dashboard.
Steps to reproduce: -- unable to reproduce the issue.
Please find the below logs and other details.
The text was updated successfully, but these errors were encountered: