Firebase-ios-sdk: [FIRTrace updateTraceWithSessionId]_block_invoke/ [__NSSetM addObject:]:object cannot be nil.

Created on 28 Oct 2018 · 38Comments · Source: firebase/firebase-ios-sdk

version

Firebase 5.10.0
FirebaseAnalytics 5.2.0
FirebasePerformace 2.1.2
GoogleTagManager 7.1.1
GTMSessionFetcher 1.2.1

xcode

Xcode version: _9.4.1
Firebase SDK version: _5.10.0

crash

There has been a lot of collapse in the last two days about [__NSSetM addObject:]: object cannot be nil. The error stack is as follows

0 CoreFoundation
___exceptionPreprocess + 228
1 libobjc.A.dylib
objc_exception_throw + 56
2 CoreFoundation
_CFArgv + 0
3 CoreFoundation
-[__NSSetM addObject:] + 772
4 homeApp
___36-[FIRTrace updateTraceWithSessionId]_block_invoke + 92
5 libdispatch.dylib
__dispatch_call_block_and_release + 24
6 libdispatch.dylib
__dispatch_client_callout + 16
7 libdispatch.dylib
__dispatch_lane_serial_drain$VARIANT$mp + 592
8 libdispatch.dylib
__dispatch_lane_invoke$VARIANT$mp + 432
9 libdispatch.dylib
__dispatch_workloop_worker_thread + 600
10 libsystem_pthread.dylib
_pthread_wqthread + 312
11 libsystem_pthread.dylib
start_wqthread + 4

performance

Source

zhengzeqin007

👍9

Most helpful comment

The crash was because of a incorrect configurations set on our backend server. We have rolled back the change and we should not see this crash anymore. The configuration rollback happened yesterday. We will be rolling out a fix on the client as well on this.

visumickey on 30 Oct 2018

👍4

All 38 comments

Tracked internally at b/118559496

paulb777 on 28 Oct 2018

I'm also getting a ton of these after updating to the latest version of Firebase.

bryanbartow on 28 Oct 2018

👍2

This is one of two seemingly related issues causing a 8% crash rate of my application. This is an URGENT issue.

Other variants (adding nil object to set):
__48-[FPRNetworkTrace updateTraceWithCurrentSession]_block_invoke

FirebasePerformance 2.1.2
Firebase/Core (5.10.0)

will update versions and report back.

BrettThePark on 28 Oct 2018

Thanks for the reports.

Please identify your Firebase and FirebasePerformance versions. The latest version of Firebase is 5.11.0 and FirebasePerformance is 2.2.0.

paulb777 on 28 Oct 2018

But some time ago it was normal. It was only in the last two days that this problem occurred. Did any recent adjustments lead to it?

zhengzeqin007 on 29 Oct 2018

Can you please confirm the version of Firebase Performance on which this issue is occurring? Secondly, were you able to reproduce in your development environment?

visumickey on 29 Oct 2018

@zhengzeqin007 Are you seeing this issue only in the last couple of days? Can you share the version of the Performance SDK for the version of the app that is crashing?

visumickey on 29 Oct 2018

@visumickey This problem first appeared in 2018-10-27 and was normal before. My table here is as follows

zhengzeqin007 on 30 Oct 2018

I am also getting same issue. Here are the pod details I am using.

(Copied from podfile.lock)

Crashlytics (3.10.9):
- Fabric (~> 1.7.13)
- Fabric (1.7.13)
- Firebase/Core (5.11.0):
- Firebase/CoreOnly
- FirebaseAnalytics (= 5.3.0)
- Firebase/CoreOnly (5.11.0):
- FirebaseCore (= 5.1.6)
- Firebase/Performance (5.11.0):
- Firebase/Core
- FirebasePerformance (= 2.2.0)
- FirebaseABTesting (2.0.0):
- FirebaseCore (~> 5.0)
- Protobuf (~> 3.5)
- FirebaseAnalytics (5.3.0):
- FirebaseCore (~> 5.1)
- FirebaseInstanceID (~> 3.3)
- GoogleAppMeasurement (~> 5.3)
- GoogleUtilities/AppDelegateSwizzler (~> 5.2)
- GoogleUtilities/MethodSwizzler (~> 5.2)
- GoogleUtilities/Network (~> 5.2)
- "GoogleUtilities/NSData+zlib (~> 5.2)"
- nanopb (~> 0.3)
- FirebaseCore (5.1.6):
- GoogleUtilities/Logger (~> 5.2)
- FirebaseInstanceID (3.3.0):
- FirebaseCore (~> 5.1)
- GoogleUtilities/Environment (~> 5.3)
- GoogleUtilities/UserDefaults (~> 5.3)
- FirebasePerformance (2.2.0):
- FirebaseAnalytics (~> 5.3)
- FirebaseInstanceID (~> 3.3)
- FirebaseRemoteConfig (~> 3.1)
- GoogleToolboxForMac/Logger (~> 2.1)
- "GoogleToolboxForMac/NSData+zlib (~> 2.1)"
- GoogleUtilities/ISASwizzler (~> 5.2)
- GoogleUtilities/MethodSwizzler (~> 5.2)
- GTMSessionFetcher/Core (~> 1.1)
- Protobuf (~> 3.5)
- FirebaseRemoteConfig (3.1.0):
- FirebaseABTesting (~> 2.0)
- FirebaseAnalytics (~> 5.3)
- FirebaseCore (~> 5.1)
- FirebaseInstanceID (~> 3.3)
- GoogleUtilities/Environment (~> 5.2)
- "GoogleUtilities/NSData+zlib (~> 5.2)"
- Protobuf (~> 3.5)
- GoogleAppMeasurement (5.3.0):
- GoogleUtilities/AppDelegateSwizzler (~> 5.2)
- GoogleUtilities/MethodSwizzler (~> 5.2)
- GoogleUtilities/Network (~> 5.2)
- "GoogleUtilities/NSData+zlib (~> 5.2)"
- nanopb (~> 0.3)
- GoogleToolboxForMac/Defines (2.1.4)
- GoogleToolboxForMac/Logger (2.1.4):
- GoogleToolboxForMac/Defines (= 2.1.4)
- "GoogleToolboxForMac/NSData+zlib (2.1.4)":
- GoogleToolboxForMac/Defines (= 2.1.4)
- GoogleUtilities/AppDelegateSwizzler (5.3.4):
- GoogleUtilities/Environment
- GoogleUtilities/Logger
- GoogleUtilities/Network
- GoogleUtilities/Environment (5.3.4)
- GoogleUtilities/ISASwizzler (5.3.4)
- GoogleUtilities/Logger (5.3.4):
- GoogleUtilities/Environment
- GoogleUtilities/MethodSwizzler (5.3.4):
- GoogleUtilities/Logger
- GoogleUtilities/Network (5.3.4):
- GoogleUtilities/Logger
- "GoogleUtilities/NSData+zlib"
- GoogleUtilities/Reachability
- "GoogleUtilities/NSData+zlib (5.3.4)"
- GoogleUtilities/Reachability (5.3.4):
- GoogleUtilities/Logger
- GoogleUtilities/UserDefaults (5.3.4):
- GoogleUtilities/Logger
- GTMSessionFetcher/Core (1.2.0)
- nanopb (0.3.901):
- nanopb/decode (= 0.3.901)
- nanopb/encode (= 0.3.901)
- nanopb/decode (0.3.901)
- nanopb/encode (0.3.901)
- Protobuf (3.6.1)

DibyajyotiAndolasoft on 30 Oct 2018

Hello All, Any updates on this? How this will be fixed? my app has 600 crashes with this issue.

I am using these versions. Before iOS 12, I have not found these crashes.

Using Firebase (5.5.0)
Using FirebaseAnalytics (5.1.0)
Using FirebaseCore (5.1.0)
Using FirebaseInstanceID (3.2.0)
Using FirebasePerformance (2.1.0)

imRanjit on 30 Oct 2018

visumickey on 30 Oct 2018

👍4

@visumickey for clarification ... if the issue was on the backend, what is the need for a client side fix?

BrettThePark on 30 Oct 2018

@visumickey for clarification ... if the issue was on the backend, what is the need for a client side fix?

It is just a protective/defensive fix on the client side to avoid such instances in the future.

visumickey on 30 Oct 2018

@visumickey @BrettThePark its a firebase issue right? so what that has to do with your backend servers?

imRanjit on 31 Oct 2018

@visumickey - The issue is still present for our app.
Is this really fixed on backend?
We've been facing globally more than 1600 crashes for the same amount of users overnight.
This is really a huge issue to our customers and if nothing happens we need to release a hot fix and remove performance as our only option which would not be the optimal of course.

mberndt92 on 31 Oct 2018

@visumickey - We are still getting crashes this morning. I just updated Firebase and realized we were on version 5.9 of Firebase/Core and 2.1.2 of Performance. Will I need to do a release with the updated versions to stop having this crash? Also, all of the users have iOS 12.

sarahedenyoung on 31 Oct 2018

👍1

@mberndt92 @sarahedenyoung Couple of questions:

Has the number of crashes started reducing in the last couple of days? (This is to confirm if the configuration rollback has rolled out to the devices)
Can you confirm the version of the Performance SDK on the version of your app that has this crash? (Intent is to check if the issue is occuring in the latest version of the Performance SDK, 2.2.0)

@mberndt92 Would you mind updating to the latest version of the Performance SDK (2.2.0)?

visumickey on 31 Oct 2018

@visumickey

No, it has not
App had version 2.1.2

sarahedenyoung on 31 Oct 2018

@visumickey @sarahedenyoung
"We are still getting crashes this morning".....me too

zeqinjie on 1 Nov 2018

Any updates?

sarahedenyoung on 1 Nov 2018

@sarahedenyoung no update still FirebasePerformace v2.1.2. but i think it's a back-end problem. It's reasonable to say that no updated version should be able to solve the problem.

zeqinjie on 1 Nov 2018

@sarahedenyoung @mberndt92 @zeqinjie The configuration changes is taking time to rollout. Please update to the latest version of the Performance 2.2.0 (Already released)/2.2.1 (Rolling out next week) that should solve this problem.

visumickey on 1 Nov 2018

"We are still getting crashes this morning"

Using FirebaseCore (5.1.5)
Using FirebasePerformance (2.1.2)
Using FirebaseRemoteConfig (3.0.2)
Using FirebaseAnalytics (5.2.0)
Using FirebaseInstanceID (3.2.2)
Using FirebaseABTesting (2.0.0)

rafarbr on 1 Nov 2018

Team google, please fix this asap and tell us the solution. My app top 3 crashes.

Crash 1 - [FIRTrace updateTraceWithSessionId]_block_invoke
Crash 2 - [FPRNetworkTrace updateTraceWithCurrentSession]_block_invoke
Crash 3 - Crashed: com.google.perf.sessionIds.networkTrace

imRanjit on 2 Nov 2018

@visumickey:
I can confirm that the crash is not happening with the latest version of the performance SDK (2.2)

Thanks a lot for the support!

mberndt92 on 2 Nov 2018

Thanks for confirming, @mberndt92. I'll close this issue for now, but if anyone is still having issues, please feel free to continue commenting here.

morganchen12 on 2 Nov 2018

🎉2

@imRanjit Like I mentioned - Please update the Performance SDK to 2.2.0 to resolve this crash.

visumickey on 2 Nov 2018

👍1

@visumickey Cant google fix this issue at their backend servers? All app developers facing this issue should again upload a new build to app-store.

imRanjit on 5 Nov 2018

@mberndt92 whether you were able to reproduce this crash?

imRanjit on 5 Nov 2018

@imRanjit
Yes but since the suggested update is in place the crashes have been entirely resolved 🙂

mberndt92 on 5 Nov 2018

Hey thanks. I am also getting these crashes in crashlytics report. But not
able to reproduce on my device

So you updated the SDK and made a new release right ?

On Mon, 5 Nov 2018 at 3:26 PM, Maximilian Berndt notifications@github.com
wrote:

@imRanjit https://github.com/imRanjit
Yes but since the suggested update is in place the crashes have been
entirely resolved 🙂

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebase-ios-sdk/issues/2019#issuecomment-435816998,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AahvTj7mj_Ttt6fOZRz-Z7wjUAYTAj0qks5usAs6gaJpZM4X92pw
.

--
*::DISCLAIMER::

The contents of this e-mail and any attachments are confidential and
intended for the named recipient(s) only.E-mail transmission is not
guaranteed to be secure or error-free as information could be intercepted,
corrupted,lost, destroyed, arrive late or incomplete, or may contain
viruses in transmission. The e mail and its contents(with or without
referred errors) shall therefore not attach any liability on the originator
or redBus.com. Views or opinions, if any, presented in this email are
solely those of the author and may not necessarily reflect the views or
opinions of redBus.com. Any form of reproduction, dissemination, copying,
disclosure, modification,distribution and / or publication of this message
without the prior written consent of authorized representative of redbus.
http://redbus.in/com is strictly prohibited. If you have received this
email in error please delete it and notify the sender immediately.Before
opening any email and/or attachments, please check them for viruses and
other defects.*

imRanjit on 5 Nov 2018

I'm still seeing such crash reports coming from Crashlytics :-/

agordeev on 6 Nov 2018

Hello All, I didn't update the SDK, as I had to do a release for it. But as said above, due to roll-out, my crashes have dropped substantially.

imRanjit on 6 Nov 2018

we had a huge amount of crashes (20% of our users!) due to this issue，we had to remove firebase performance sdk.
we didn't update sdk version (we use pod), the only difference is that we built our app with xcode 10.
is there anyone having the same problem now?

mesonny on 8 Jan 2019

@mesonny What versions of Firebase pods are you using? IIRC, some of the recent bugs fixed and released in FirebasePerformance we're especially prevalent with Xcode 10.

paulb777 on 8 Jan 2019

hello,
same issue with our app, my pod file with lines of:

 pod 'Fabric'
 pod 'Crashlytics'
 pod 'Firebase/Core'
 pod 'Firebase/Performance' 
 pod 'Firebase/Messaging'

installs (04.07.2017) the following packages:

Using Crashlytics (3.9.0)
Using Fabric (1.7.0)
Using Firebase (5.9.0)
Using FirebaseAnalytics (5.2.0)
Using FirebaseCore (5.1.4)
Using FirebaseInstanceID (3.2.2)
Using FirebaseMessaging (3.1.2)
Using FirebasePerformance (2.1.2)
Using GTMSessionFetcher (1.2.0)
Using GoogleAppMeasurement (5.2.0)
Using GoogleToolboxForMac (2.1.4)
Using GoogleUtilities (5.3.0)

now i am trying to fix my old project,
i hope new release of PerformanseSDK has the solution