-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[BUG]: Crash in FIRInstanceIDAuthKeyChain.m line 79 -[FIRInstanceIDAuthKeychain itemsMatchingService:account:] #4205
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 comment has been minimized.
This comment has been minimized.
Maybe related to #4172 ? |
@skuske can you share the full stack trace, specifically the error message on top saying why it crash. |
@chliangGoogle
Stack trace 2:
Stack trace 3:
|
I have encountered the same problem |
@skuske @Decsunshine Can any of you share the full stack trace, It seems to related to remote config and performance, would be great to see the all the threads interaction during crash. |
@chliangGoogle Sure, here are the other stack traces: 4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
Hope that helps... :o) |
@Decsunshine can you also share the stack trace of ALL the threads? |
@chliangGoogle stack traces
|
@Decsunshine @skuske Can you also share the crash error that normally showing at the top? |
@chliangGoogle Sure, here it is:
Hope that helps. :o) |
@skuske This seems like it's crashing on a remote config serial queue. (com.google.GoogleConfigService.FIRRemoteConfig is its id). I wonder if this is two different issues, can you file a different one on remote config case and assign to @dmandar. |
Seems like it happens with remote config trigger IID call that it's crashing on remote config thread. Will take a look at. Thanks! |
Some more stack trace
|
@skuske Can you share with us the code on how you call remote config? |
@chliangGoogle Sure, as far as I can tell I do it exactly as per the instructions (https://firebase.google.com/docs/remote-config/use-config-ios?authuser=0): However, it seems that the issue disappeared with one of the newer releases of the SDK as I haven't seen this issue for a few weeks now.
|
Thanks for the update @skuske. I'll set this issue to auto-close after a week or so if the issue doesn't reappear. If it does or if it regresses in the future, please leave a comment and we'll re-open the issue. |
Will do. Thanks! 🙂 |
Hey @skuske. We need more information to resolve this issue but there hasn't been an update in 7 days. I'm marking the issue as stale and if there are no new updates in the next 3 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. @skuske 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?
Yes, I think so... :o)
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Crash reported by Crashlytics:
iOS 13.2.0 (17B84)
iPad Pro (12.9-inch, 2nd generation)
Stack Trace 1:
Steps to reproduce:
We cannot reproduce the issue, and it seems to be very rare.
Relevant Code:
Internal firebase crash, not sure if any of our code is directly related.
The text was updated successfully, but these errors were encountered: