-
Notifications
You must be signed in to change notification settings - Fork 441
ANR's in Google Play Developer Console still #614
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
This issue does not seem to follow the issue template. Make sure you provide all the required information. |
Hi @Temka193 Unfortunately, this likely seems like it has been a long running in the underlying Android SDK, firebase/quickstart-android#594. I see there have been some improvements that would have gone in since Unity version 6.7.0 that you mentioned you were using before in the prior bug, so it is possible that upgrading to the latest version of the Unity SDK might help resolve some of these issues. |
As you can see, Unity 2019.2 combined with Firebase 6.10.0 did not fix the problem |
Unfortunately I don't think this bug was fixed in Android level (see the issue is still opened in quickstart-android). I have pinged Firebase Android team. Will update if they have any news. |
So, any news about this? We are also struggling with such problem. |
Seems like a new issue was opened on Android repo It does not seem to be fixed in Android level unfortunately. |
Hey folks, This seems to be related to #543 and #877. Could you verify if this is still happening with '7.1.0`? More information here #939 (comment) |
For issue management sake, I will close this one. Please comment on #939 if you are still experiencing ANR related to RegistrationIntentService or MessagingUnityPlayerActivity in the latest Firebase SDK Also, please let us know your Android version and the stacktrace. |
The problem is described in this issue:
#564 (comment)
I answer the question:
I updated Unity to version 2019.2, but the problem with ANR still remained.

The only thing I can give you is the logs from the Google Play Console.
The text was updated successfully, but these errors were encountered: