-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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 EXC_BAD_ACCESS KERN_INVALID_ADDRESS [FIRInstanceIDKeyPairStore updateKeyRef:withTag:handler:] #2731
Comments
Tagging Analytics as well as InstanceID since it may be related to |
Edited the description with some new data about the crash that might be helpful pinning down the cause:
|
Yesterday I submitted my app and I got exactly the same problem:
EDIT: |
I meet this problem too.use the firebase/core sdk version 5.20.1 |
Same issue... Version 5.20.2 |
@georgbachmann Can you share the stack trace since you have the latest version? That helps us identify the issue. |
There's not much to see though... But here you go:
|
Same here OS Version: 12.1.4 (16D57)Device: iPhone 7#0. Crashed: com.apple.main-thread -- #0. Crashed: com.apple.main-thread #1. Thread #2. Thread #3. Thread #4. com.apple.uikit.eventfetch-thread #5. Thread #6. Thread #7. Thread |
@maksymmalyhin Would you mind taking a look at? If you don't have time, you can assign back to me. |
@maksymmalyhin @chliangGoogle This issue is still happening in my app with following logs
Following is part of podfile.lock file we used on latest file.
Please note that we started getting these crashes after enabling Firebase Performance SDK in the app, and our crash rate has taken a huge hit because of this crash :-( |
@surajthomask we released a fix for the crash in Firebase 6.1.0 (FirebaseInstanceID 4.1.0). Would it be possible for you to update Firebase SDK? |
@maksymmalyhin I updated all dependencies through cocoapods 5 days back (on May 19th) after reading that a fix has been merged before 17 days (on May 7th). Apparently it got released 3 days back only as part of M48. Was not exactly familiar with the milestone concept in here. So, will update the dependencies in the app again. I do really appreciate the quick response. Thank you :-) |
[READ] Step 1: Are you in the right place?
Yes
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
stack trace:
Also I've seen a lot of crash and error reports in Firebase Crashlytics that are missing data in the "logs" tab.
Steps to reproduce:
Haven't been able to reproduce locally, but this started happening on quite large scale in production in our latest version (+700 users affected). In this release we updated from Firebase 5.10 (FirebaseInstanceID 3.2.2), and at the same time adding custom screen tagging (see code below).
Looking at the relevant code in FIRInstanceIDKeyPairStore line 416, it looks like an issue handling backwards compatibility?
Relevant Code:
Not sure the latter is related to the crash..
--EDIT--
Couple of days later, it seems that the occurrence of the crash is slowing down rapidly (no change on the client side), which seems likely to me if the issue was indeed backwards compatibility/migration:
The text was updated successfully, but these errors were encountered: