firebase / firebase-ios-sdk

Firebase SDK for Apple App Development
https://firebase.google.com
Apache License 2.0
5.67k stars 1.49k forks source link

Random crashes in com.google.GoogleConfigService.FIRRemoteConfig #3602

Closed leandromperez closed 5 years ago

leandromperez commented 5 years ago

Hi guys, we're seeing crashes in Fabric related to the activation of the Firebase Remote Config. I'm opening this issue in case anyone else is experiencing something similar.

[REQUIRED] Step 3: Describe the problem

We are getting random crashes when activating the remote config.

Steps to reproduce:

We don't have steps, we're just seeing random crashes in Fabric with this stack trace:

Relevant Code:

Crashed: com.google.GoogleConfigService.FIRRemoteConfig
0  libobjc.A.dylib                0x19b773530 objc_msgSend + 16
1  CoreFoundation                 0x19c47135c -[__NSDictionaryM objectForKeyedSubscript:] + 216
2  OurApp                           0x102d2dc1c -[RCNConfigContent copyFromDictionary:toSource:forNamespace:] + 4370422812
3  OurApp                           0x102d2a080 __49-[FIRRemoteConfig activateWithCompletionHandler:]_block_invoke + 4370407552
4  libdispatch.dylib              0x19bfc0a38 _dispatch_call_block_and_release + 24
5  libdispatch.dylib              0x19bfc17d4 _dispatch_client_callout + 16
6  libdispatch.dylib              0x19bf6a324 _dispatch_lane_serial_drain$VARIANT$mp + 592
7  libdispatch.dylib              0x19bf6ae40 _dispatch_lane_invoke$VARIANT$mp + 428
8  libdispatch.dylib              0x19bf734ac _dispatch_workloop_worker_thread + 596
9  libsystem_pthread.dylib        0x19c1a2114 _pthread_wqthread + 304
10 libsystem_pthread.dylib        0x19c1a4cd4 start_wqthread + 4
google-oss-bot commented 5 years ago

I found a few problems with this issue:

morganchen12 commented 5 years ago

This looks very similar to a series of crashes that were fixed but have not yet been released. The fixes are scheduled to be released soon; can you test when 6.7.0 is out?

leandromperez commented 5 years ago

I will, and I'll keep you posted @morganchen12

paulb777 commented 5 years ago

Going to close, since the issue is expected to be fixed in the upcoming 6.7.0 release.