-
Notifications
You must be signed in to change notification settings - Fork 441
[Bug] #1169
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. |
I've read both issues but I didn't see any clear solution to this problem. Am i missing something? |
The only solution so far seems to be removing multiple calls of CheckAndFixDependencies, if you have more of them, but if not then we need to wait for a fix. |
Hi @PedjaSOZAP, It's possible that you're calling the If it doesn't, it would be great if you could provide a minimal, reproducible example of your project so that we can identify what's causing this behavior. You may also try our quickstart to verify the issue persists there as well. |
CheckAndFixDependenciesAsync() is called only once, at when Firebase actually gets initialized. Issue with this that we were unable to reproduce the bug in our test environment, it only happened on the live version of the project. |
I'm also hitting this crash — I also cannot repro in a minimal example, and I can confirm that I too am not calling |
Thanks for the additional information, @PedjaSOZAP and @aroman. It's unusual for the crash to appear in just one version of your project. Could you provide a minimal, reproducible example of your implementation so that we can analyze this behavior? |
This bug is a dupe of #1170 |
Your callstack fit this profile #1160 (comment) Please try to upgrade to the latest and see if this fixes your issue. |
Here is the minimum reproducible code https://github.com/AjayC-Bsw/FirebaseCrashRepro Tested with both mono / IL2CPP. Steps to reproduce -
Application crashes when open, on some devices first time on some devices when come again after clearing data , Repeat these steps 5-6 times crash occurs. I have tested those steps for our production application and able to repro. This sample does have only firebase analytics , messaging . Crash Logs with MONO is different -
|
I've tried updating to latest version of firebase (8.6.1) and issue is still there, it now makes more than 50% of our crashes on crashlytics |
We haven't been able to completely reproduce the problem on our end, but we just released 8.6.2, which contains a potential fix for the issue. |
Hey @PedjaSOZAP, could you confirm if the issue persists using version 8.6.2 of the SDK? |
I can confirm we are not getting this issue after updating to 8.6.2 |
Hi, I downgraded plugin back to 8.1.0, and I can confirm that we didn't get any issues with that version of the plugin, but I will try on the next update updating firebase to latest version, and I will let you know how that goes. Issue was that we couldn't get the issue in our testing environment |
Thanks for letting us know, @PedjaSOZAP. In the event that you encounter an issue with the latest SDK, let us know by leaving a comment so that we can reopen this ticket and continue our investigation. With that, I'll be closing this for now. |
[REQUIRED] Please fill in the following fields:
[REQUIRED] Please describe the issue here:
Hello, in crashlytics window we started to see the crashes pthread_mutex_lock that may be related to firebase and are causing issues to number of users. Please double check the attached files below. Thank you
Steps to reproduce:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
Unfortunately we don't have any more information than ones that you can see in files attached below
What happened? How can we make the problem occur?
Unfortunately we don't have any more information than ones that you can see in files attached below
If you have a downloadable sample project that reproduces the bug you're reporting, you will
Unfortunately we don't have any more information than ones that you can see in files attached below
Relevant Code:
pthread_mutex_lock line 4.txt
pthread_mutex_lock line 2.txt
pthread_mutex_lock line 8.txt
pthread_mutex_lock.txt
The text was updated successfully, but these errors were encountered: