-
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
Deadlock in +[FPRRemoteConfigFlags sharedInstance] #6287
Comments
Hello @mike-kerley, thank you for reporting this issue and providing us with the snippets and environment details! While we work on investigating and narrowing down a root cause, it would be helpful to know what iOS version you're seeing this issue occur within. If you're able to provide this information, please do so -- otherwise we'll continue investigating without it. Thanks again |
Sure - it was with iOS 13.4. Thanks for looking into it! |
Great, thank you! note: this issue is being tracked internally at b/165809929 |
Just an update, we found the race condition that caused the issue. Will fix it soon. |
This issue is fixed and will be released in the upcoming release. |
Closing. Please watch the Firebase 7 Milestone to track availability. |
[REQUIRED] Step 1: Describe your environment
Carthage
[REQUIRED] Step 2: Describe the problem
I've been experiencing some intermittent crashes when running my app's tests. The crash dump points to:
Whenever this happens, I see two other threads stuck in a wait state inside
+[FPRRemoteConfigFlags sharedInstance]
(or somewhere deeper in the stack), such as:Steps to reproduce:
This happens intermittently when running tests in Jenkins CI builds. CI nodes are running Mac OS X 10.15.5 (19F101). I haven't seen it on my local machine, nor when running the app normally.
The failing test targets use the main app as a host so we can take UI snapshots. Unit tests without the host app appear unaffected. It seems to happen much more frequently since I updated from Fabric Crashlytics to Firebase Crashlytics; maybe that's affecting the timing somehow?
I'd appreciate any help/workarounds or a bug fix. Thanks!
The text was updated successfully, but these errors were encountered: