Fatal Exception: NSInvalidArgumentException

[smauryaakeed]

Hi team,

we have used OneSignal iOS SDK 3.4.3, and we followed initialisation as given in document.

OneSignal.setLogLevel(.LL_VERBOSE, visualLevel: .LL_NONE)
            OneSignal.initWithLaunchOptions(launchOptions)
            OneSignal.setAppId(Constants.ThirdPartyKey.oneSignalKey)
            OneSignal.promptForPushNotifications(userResponse: { _ in
})

But, I found in some devices it is crashing.

Please find the Crashlytics logs below:

Fatal Exception: NSInvalidArgumentException
0 CoreFoundation 0x1807e25b4 __exceptionPreprocess
1 libobjc.A.dylib 0x1952617a8 objc_exception_throw
2 CoreFoundation 0x180854a80 -[__NSCFString characterAtIndex:].cold.1
3 CoreFoundation 0x180860ad8 -[__NSPlaceholderDictionary initWithCapacity:].cold.1
4 CoreFoundation 0x1806cf360 -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]
5 CoreFoundation 0x1806c1c80 +[NSDictionary dictionaryWithObjects:forKeys:count:]
6 Akeed 0x10068fe94 +[OSRequestInAppMessageViewed withAppId:withPlayerId:withMessageId:forVariantId:]
7 Akeed 0x10064c654 -[OSMessagingController messageViewImpressionRequest:]
8 libdispatch.dylib 0x1803cda54 _dispatch_call_block_and_release
9 libdispatch.dylib 0x1803cf7ec _dispatch_client_callout
10 libdispatch.dylib 0x1803ddc40 _dispatch_main_queue_callback_4CF
11 CoreFoundation 0x18075c1f8 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE
12 CoreFoundation 0x1807560d0 __CFRunLoopRun
13 CoreFoundation 0x1807551c0 CFRunLoopRunSpecific
14 GraphicsServices 0x197d3d734 GSEventRunModal
15 UIKitCore 0x1831c37e4 -[UIApplication _run]
16 UIKitCore 0x1831c9054 UIApplicationMain
17 Akeed 0x1000d5abc main + 14 (AppDelegate.swift:14)
18 libdyld.dylib 0x180411cf8 start

Please help us asap.

[emawby]

@smauryaakeed thank you for reporting I am looking into this.

[emawby]

@smauryaakeed hello this appears to be a crash when sending an in app message impression. Could you please describe your in app message triggers? Have you been able to reproduce the crash at all?

[emawby]

@smauryaakeed Hello, are you still experiencing this issue?

[emawby]

closing for now feel free to reopen if this is still an issue

[kajensen]

I'm seeing this issue across numerous devices with v5.1.6 of the OneSignal SDK