Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
After releasing the latest update to our app, we've started to see this crash in the crash logs.
I saw some other Remote Config crashes when I searched the github issues, but I didn't see any with this particular stack trace (or similar).
I spent a bit of time looking through the source code related to the stack trace, and I can see how the error happens. It looks like
I realize that we're a version or two behind on the Firebase SDK. I looked at the release notes and source diff and didn't see anything that looked like a fix for this, but if I'm wrong and updating the SDK will fix this, please let me know.
Thanks @visumickey - this is our number 1 crash at the moment, we could do with a fix asap.
Here's the trace from thread 9 of an example crash - I can send you the whole log directly if necessary?
Crashlytics also shows the following:
Here's an extract from "podfile.lock":
This is recognised as a different crash in Crashlytics, and is also happening regularly. Sounds very similar though.
"BUG IN CLIENT OF LIBDISPATCH: dispatch_sync called on queue already owned by current thread"