ShakeSShake
Jun 30

[iOS SDK v14.1.2] Crash on launch when calling Shake.start(), NSDateFormatter

Thread 0 name: Thread 0 Crashed: 0 libicucore.A.dylib 0x00000001a1f59cd8 icu::SimpleDateFormat::subParse(icu::UnicodeString const&, int&, char16_t, int, signed char, signed char, signed char*, int&, icu::Calendar&, int, icu::MessageFormat*, UTimeZoneFormatTimeType*, int... + 516 (smpdtfmt.cpp:3150) 1 libicucore.A.dylib 0x00000001a1f59cd4 icu::SimpleDateFormat::subParse(icu::UnicodeString const&, int&, char16_t, int, signed char, signed char, signed char*, int&, icu::Calendar&, int, icu::MessageFormat*, UTimeZoneFormatTimeType*, int... + 512 (smpdtfmt.cpp:3150) 2 libicucore.A.dylib 0x00000001a1f59274 icu::SimpleDateFormat::parse(icu::UnicodeString const&, icu::Calendar&, icu::ParsePosition&) const + 1004 (smpdtfmt.cpp:2460) 3 libicucore.A.dylib 0x00000001a1f87560 udat_parseCalendar + 176 (udat.cpp:411) 4 CoreFoundation 0x00000001a2074e04 CFDateFormatterGetAbsoluteTimeFromString + 540 (CFDateFormatter.c:1797) 5 CoreFoundation 0x00000001a2074ba0 CFDateFormatterCreateDateFromString + 108 (CFDateFormatter.c:1747) 6 Foundation 0x00000001a3451b7c getObjectValue + 272 (NSDateFormatter.m:589) 7 Foundation 0x00000001a33f56dc -[NSDateFormatter getObjectValue:forString:errorDescription:] + 200 (NSDateFormatter.m:567) 8 Foundation 0x00000001a33f55d8 -[NSDateFormatter dateFromString:] + 64 (NSDateFormatter.m:625) 9 Shake 0x000000010293637c 0x1028d4000 + 402300 10 Shake 0x00000001028f578c 0x1028d4000 + 137100 11 Shake 0x00000001028e1d7c 0x1028d4000 + 56700 12 CoreFoundation 0x00000001a20c4d6c __CFSimpleMergeSort + 380 (CFSortFunctions.c:111) 13 CoreFoundation 0x00000001a20c4d04 __CFSimpleMergeSort + 276 (CFSortFunctions.c:154) 14 CoreFoundation 0x00000001a20c4ce8 __CFSimpleMergeSort + 248 (CFSortFunctions.c:153) 15 CoreFoundation 0x00000001a20c4748 CFSortIndexes + 316 (CFSortFunctions.c:322) 16 CoreFoundation 0x00000001a2011cf8 -[NSArray sortedArrayFromRange:options:usingComparator:] + 740 (NSArray.m:631) 17 CoreFoundation 0x00000001a2016df8 -[NSMutableArray sortedArrayFromRange:options:usingComparator:] + 60 (NSMutableArray.m:600) 18 Shake 0x00000001028e1bb4 0x1028d4000 + 56244 19 Shake 0x00000001028e18f0 0x1028d4000 + 55536 20 Shake 0x00000001028df194 0x1028d4000 + 45460 21 Shake 0x00000001028da538 0x1028d4000 + 25912 22 App 0x00000001022c5788 specialized AppDelegate.application(_:didFinishLaunchingWithOptions:) + 388 (AppDelegate.swift:29) 23 App 0x00000001022c5188 application + 4 (<compiler-generated>:0) 24 App 0x00000001022c5188 @objc AppDelegate.application(_:didFinishLaunchingWithOptions:) + 108 25 UIKitCore 0x00000001a4b207a8 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 360 (UIApplication.m:2279) 26 UIKitCore 0x00000001a4b2223c -[UIApplication _callInitializationDelegatesWithActions:forCanvas:payload:fromOriginatingProcess:] + 3504 (UIApplication.m:2671) 27 UIKitCore 0x00000001a4b28388 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1244 (UIApplication.m:4201) 28 UIKitCore 0x00000001a417bcd8 -[_UISceneLifecycleMultiplexer completeApplicationLaunchWithFBSScene:transitionContext:] + 216 (_UISceneLifecycleMultiplexer.m:436) 29 UIKitCore 0x00000001a4b24134 -[UIApplication _compellApplicationLaunchToCompleteUnconditionally] + 68 (UIApplication.m:3181) 30 UIKitCore 0x00000001a4b24560 -[UIApplication _run] + 1036 (UIApplication.m:0) 31 UIKitCore 0x00000001a4b29df4 UIApplicationMain + 168 (UIApplication.m:4740) 32 App 0x000000010207be08 main + 208 (main.swift:17) 33 libdyld.dylib 0x00000001a1d65cf8 start + 4
CompletedCompleted
Nov 24, 2021

This has been fixed by avoiding naming collisions with objective C categories, please update to the latest Shake iOS SDK.

Jul 1, 2021

Jin Wang Hi Jin, Thanks for the stack trace. Looks like there is an issue with date formatting. We had a similar issue like this already reported which happened when the main app target added a category extension on the NSDate class, overriding the Shake one. If this is the case, expect this to be fixed in the next release. Sending over to the QA team to inspect.

Jun 30, 2021

We're in the progress of updating the SDK to the latest but I didn't see any mention in the release notes around this issue so just want to raise it as a bug in case it's not fixed yet.