-
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
Crashes in FPRScreenTraceTracker thread #1986
Comments
Internally tracked at b/118274589 |
I have exactly the same issue, any news about how to fix this crash? |
This should be fixed in next release of Firebase Performance (planned mid December, release M40). |
Hello, Please can you also update Carthage version files. They don't include 5.15.0 binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseABTestingBinary.json" |
@Igor-Palaguta Carthage was updated with 5.15.0 today. |
Thanks! |
Reduced the occurrence, but still happening. |
Still happening with Firebase/Performance (5.16.0). |
@senryxie Do you have the same backtrace as the original issue? What is the version of the FirebasePerformance pod from Podfile.lock? |
@paulb777 Firebase/Performance (5.16.0) is from the Podfile.lock. It's happening in production, I got this from Fabric.
|
Thanks - It looks like a different crash, but we may be able to track here. I'll reopen. |
This is indeed a different issue. Curious - Can we know the volume/percentage of this crash? |
Hi @visumickey, in the last two weeks, there are 72 crashes from 67 users out of around 400k unique users. |
Internally tracked at b/127766474. |
We got 49 crashes with 47 users
|
@levantAJ This was marked as fixed in Firebase 5.19.0. Are you using at least that version? |
@paulb777 I'm using |
We are seeing crashes in
+[FPRFeatureControl featureForceState:]
on the com.google.FPRScreenTraceTracker as well as the main thread.There are no specific steps to reproduce this crash. They popped up in Firebase on devices mainly on iOS 12.0
Stack trace for com.google.FPRScreenTraceTracker
Stack trace of main thread
The text was updated successfully, but these errors were encountered: