v17.1.0 on iOS 17.5 - iOS SDK Crashes on launch - NSInvalidArgumentException -[__NSArrayM insertObject:atIndex:]: object cannot be nil

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'

*** First throw call stack:

(

0 CoreFoundation 0x00000001804ae0f8 __exceptionPreprocess + 172

1 libobjc.A.dylib 0x0000000180087db4 objc_exception_throw + 56

2 CoreFoundation 0x0000000180393044 -[__NSArrayM insertObject:atIndex:] + 1252

3 Intercom 0x00000001060eb528 IntercomSDK_saveViewHierarchy + 496988

4 Intercom 0x00000001060eadec IntercomSDK_saveViewHierarchy + 495136

5 Foundation 0x0000000180d54084 -[NSObject(NSKeyValueCoding) setValuesForKeysWithDictionary:] + 184

6 Intercom 0x00000001060eacd4 IntercomSDK_saveViewHierarchy + 494856

7 Intercom 0x00000001060eac78 IntercomSDK_saveViewHierarchy + 494764

8 Intercom 0x00000001060a5fe4 IntercomSDK_saveViewHierarchy + 213016

9 Foundation 0x0000000180d54084 -[NSObject(NSKeyValueCoding) setValuesForKeysWithDictionary:] + 184

10 Intercom 0x00000001060a5c04 IntercomSDK_saveViewHierarchy + 212024

11 Intercom 0x00000001060a5af0 IntercomSDK_saveViewHierarchy + 211748

12 Intercom 0x00000001060966c8 IntercomSDK_saveViewHierarchy + 149244

13 Intercom 0x00000001060c1760 IntercomSDK_saveViewHierarchy + 325524

14 Intercom 0x00000001060c12e8 IntercomSDK_saveViewHierarchy + 324380

15 CFNetwork 0x0000000184316e78 CFNetwork + 32376

16 CFNetwork 0x0000000184332c98 _CFHTTPMessageSetResponseProxyURL + 14888

17 libdispatch.dylib 0x0000000105aefec4 _dispatch_call_block_and_release + 24

18 libdispatch.dylib 0x0000000105af173c _dispatch_client_callout + 16

19 libdispatch.dylib 0x0000000105af9a30 _dispatch_lane_serial_drain + 916

20 libdispatch.dylib 0x0000000105afa774 _dispatch_lane_invoke + 420

21 libdispatch.dylib 0x0000000105b071a8 _dispatch_root_queue_drain_deferred_wlh + 324

22 libdispatch.dylib 0x0000000105b06604 _dispatch_workloop_worker_thread + 488

23 libsystem_pthread.dylib 0x0000000104d9f814 _pthread_wqthread + 284

24 libsystem_pthread.dylib 0x0000000104d9e5d4 start_wqthread + 8

)

libc++abi: terminating due to uncaught exception of type NSException

Be the first to reply!

UPDATE: It appears to only crash if the AI chat bot (from the intercom dashboard) is enabled. I hope there is a fix for this coming?

Hi @kosmosx ! Ebenezer here from Engineering Support👋.

Could you update the SDK to the latest version and see if you still get this error?

I know there were some fixes made regarding crashes in the version.

Hi @Ebenezer.Laleye - I updated from 17.1.0 to 17.1.1, but it still immediately crashes. Seems to be related to IntercomSDK_saveViewHierarchy?

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'
*** First throw call stack:
(
	0   CoreFoundation                      0x00000001804ae0f8 __exceptionPreprocess + 172
	1   libobjc.A.dylib                     0x0000000180087db4 objc_exception_throw + 56
	2   CoreFoundation                      0x0000000180393044 -[__NSArrayM insertObject:atIndex:] + 1252
	3   Intercom                            0x0000000104268e78 IntercomSDK_saveViewHierarchy + 496244
	4   Intercom                            0x000000010426873c IntercomSDK_saveViewHierarchy + 494392
	5   Foundation                          0x0000000180d54084 -[NSObject(NSKeyValueCoding) setValuesForKeysWithDictionary:] + 184
	6   Intercom                            0x0000000104268624 IntercomSDK_saveViewHierarchy + 494112
	7   Intercom                            0x00000001042685c8 IntercomSDK_saveViewHierarchy + 494020
	8   Intercom                            0x0000000104223c9c IntercomSDK_saveViewHierarchy + 213144
	9   Foundation                          0x0000000180d54084 -[NSObject(NSKeyValueCoding) setValuesForKeysWithDictionary:] + 184
	10  Intercom                            0x00000001042238bc IntercomSDK_saveViewHierarchy + 212152
	11  Intercom                            0x00000001042237a8 IntercomSDK_saveViewHierarchy + 211876
	12  Intercom                            0x0000000104214380 IntercomSDK_saveViewHierarchy + 149372
	13  Intercom                            0x000000010423ef34 IntercomSDK_saveViewHierarchy + 324400
	14  Intercom                            0x000000010423eabc IntercomSDK_saveViewHierarchy + 323256
	15  CFNetwork                           0x0000000184316e78 CFNetwork + 32376
	16  CFNetwork                           0x0000000184332c98 _CFHTTPMessageSetResponseProxyURL + 14888
	17  libdispatch.dylib                   0x00000001031bfec4 _dispatch_call_block_and_release + 24
	18  libdispatch.dylib                   0x00000001031c173c _dispatch_client_callout + 16
	19  libdispatch.dylib                   0x00000001031c9a30 _dispatch_lane_serial_drain + 916
	20  libdispatch.dylib                   0x00000001031ca774 _dispatch_lane_invoke + 420
	21  libdispatch.dylib                   0x00000001031d71a8 _dispatch_root_queue_drain_deferred_wlh + 324
	22  libdispatch.dylib                   0x00000001031d6604 _dispatch_workloop_worker_thread + 488
	23  libsystem_pthread.dylib             0x00000001036d3814 _pthread_wqthread + 284
	24  libsystem_pthread.dylib             0x00000001036d25d4 start_wqthread + 8
)
libc++abi: terminating due to uncaught exception of type NSException

Hi kosmosx, It’s Mat from the Support Engineering Team 😀

Please reach out to us via Messenger in your workspace so we can create a bug report for our Product Team.

We are having the exact same issue as @kosmosx

When we turn on the AI chat bot, the app insta-crashes in IntercomSDK_saveViewHierarchy with Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'

I can reproduce at will, even on the latest version of the React Native SDK (`"@intercom/intercom-react-native": "7.1.3"`)

Hi @Gianni Settino

Can you flag this issue to us via Messenger? It might be an ongoing bug ticket open, but we might need more information for our engineers to tackle this issue.

Hi @mateusz.leszkiewicz -- I opened a ticket yesterday. Says the team generally replies within 6 hours but going on 20 hours now with no response

Hi Gianni Settino,

We are experiencing a bit of surge in cases but I mark your case as a priority and someone should be with your shortly.

This is still a huge issue in SDK v18.8.1. It’s by far the biggest crash in our app. Only happens on iOS 16+17.

@Philip Engberg

Are you saying that the issue appears for the outdated iOS devices with the latests Interdom SDK?

If yes, we recommend updating all devices to the latest software version to make sure they are safe to use.
Our latest SDK works best on devices that have the latest version of their oses recommended by the producer.

Join the Intercom Community 🎉

Intercom Customers and Employees

Login to the community

Intercom Customers and Employees

Scanning file for viruses.

This file cannot be downloaded