Post

Replies

Boosts

Views

Activity

EXC_BAD_ACCESS (SIGSEGV) (possible pointer authentication failure)
Hi We had the following crash report from one of our customers that using our SDK: Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x00009970accfd190 -> 0x00000070accfd190 (possible pointer authentication failure) Exception Codes: 0x0000000000000001, 0x00009970accfd190 VM Region Info: 0x70accfd190 is not in any region. Bytes after previous region: 2899300753 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL commpage (reserved) 1000000000-7000000000 [384.0G] ---/--- SM=NUL ...(unallocated) ---> UNUSED SPACE AT END Termination Reason: SIGNAL 11 Segmentation fault: 11 Terminating Process: exc handler [8788] Triggered by Thread: 5 Any suggestion on the reason why it happens? I understand that msgSend is related to zombie but from the code I don't see where it might happen and it's only single client that has this issue. How to father investigate it crashlog.crash
0
0
1.3k
May ’23
willEnterForegroundNotification not get called on app launch
class AppDelegate: NSObject, UIApplicationDelegate, UISplitViewControllerDelegate { var window: UIWindow? @objc func pendoEnterForeground() { print("pendoEnterForeground") } func applicationWillEnterForeground(_ application: UIApplication) { print("applicationWillEnterForeground") } func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool { NotificationCenter.default.addObserver(self, selector: #selector(pendoEnterForeground), name: UIApplication.willEnterForegroundNotification, object: nil) ... Th following works correctly on app with scenes BUT on old apps without scenes the following doesn't work on App launch (on the following foreground background it does work)i.e:pendoEnterForeground and applicationWillEnterForeground doesn't get triggered on first app launch.
0
1
1.1k
May ’23
Symolicate Apple framework crash:Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[<NSTextContentStorage: 0x280587a80> locationFromLocation:withOffset:] received invalid location (null)'
We are releasing IOS SDK and one of our customers has shared with us his crash log which is not symbolicated and shows a wrong instruction place in our SDK. We release our SDK with .DSYms stam2.txt I would like to symbolicate the Apple framework stack first so I have looked at the following : Code Type: ARM-64 (Native) OS Version: iOS 16.1.1 (20B101) I have downloaded the correct package for it: iOS DeviceSupport/16.1.1 (20B101) arm64 If I look at the binary images: 0x1cfeb9000 - 0x1d1696fff UIKitCore arm64-unknown <179501b60fc2344ab969b4e3961ebe10> /System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore so the uuid is 179501b60fc2344ab969b4e3961ebe10 BUT executing dwarfdump --uuid UIKitCore UUID: AA0A89BD-E48F-31DB-AD5C-5C724CE77D12 (arm64) UIKitCore in the iOS DeviceSupport/16.1.1 (20B101) arm64 gave me a different uuid I am wondering why the uuid are differnt? (I have also tried with arm64e) is there a way to symbolicated apple framework stack trace without the .DSYM file of the app? why the only symbolicated method is in our SDK (I guess it because we ship the SDK with .DSYM while the app developer didnt symbolize his crash logs)
0
0
1.2k
Nov ’22
Crash in ios15 EXC_CRASH (SIGKILL)
One of our customers provided us with stack log crash . The crash is coming from within the SDK. It seems that the crash start to happen on iOS 15. (We were unable to reproduce it on the simulator and haven't tried it on device yet) We would like to have more insights about the crash and its reason as according to the reference refernce there is no Termination Reason or Code. CrashLogObfuscated.txt
8
0
8.6k
Dec ’21