[Bug]: Fatal Exception: NSInvalidArgumentException *** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[1]

[Abrar-ios]

What happened?

crash stack trace
Fatal Exception: NSInvalidArgumentException
0 CoreFoundation 0x9cb4 __exceptionPreprocess
1 libobjc.A.dylib 0x183d0 objc_exception_throw
2 CoreFoundation 0x1aff84 -[__NSCFString characterAtIndex:].cold.1
3 CoreFoundation 0x1bb4ac -[__NSPlaceholderDictionary initWithCapacity:].cold.1
4 CoreFoundation 0x2545c -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]
5 CoreFoundation 0x252fc +[NSDictionary dictionaryWithObjects:forKeys:count:]
6 OneSignalCore 0xa06c (Missing UUID 3ecfe67b55a5307db6b7aaac358b905e)
7 OneSignalCore 0x9338 (Missing UUID 3ecfe67b55a5307db6b7aaac358b905e)
8 Instabug 0x20c430 (Missing UUID efd66983d9ce3d8c8b7fd82a09624d03)
9 CFNetwork 0x20048 CFURLRequestSetMainDocumentURL
10 CFNetwork 0x2fd30 _CFNetworkErrorCopyLocalizedDescriptionWithHostname
11 libdispatch.dylib 0x2320 _dispatch_call_block_and_release
12 libdispatch.dylib 0x3eac _dispatch_client_callout
13 libdispatch.dylib 0xb534 _dispatch_lane_serial_drain
14 libdispatch.dylib 0xc0d8 _dispatch_lane_invoke
15 libdispatch.dylib 0x16cdc _dispatch_workloop_worker_thread
16 libsystem_pthread.dylib 0xddc _pthread_wqthread
17 libsystem_pthread.dylib 0xb7c start_wqthread

Steps to reproduce?

I couldn't confirm the exact steps to reproduce the issue. However, I observed that the application crashes at random time intervals whenever it is brought to the active state.

What did you expect to happen?

application shouldn't crash at least

OneSignal iOS SDK version

Release 5.2.7

iOS version

17, 16

Specific iOS version

iPadOS 16.5.0
iPadOS 14.6.0

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[nomimalik92]

I am getting this same issue and I am unable to reproduce it on my system.

It is effecting maximum users on my application.

[nan-li]

Hi @Abrar-ios and @nomimalik92 thank you for reaching out. We made a fix for this crash in Release 5.2.9. Please upgrade to that version or later.