Thread 0 Crashed: 20 libsystem_kernel.dylib 0x00000001f58df4c4 __abort_with_payload + [ : 8] 31 libsystem_kernel.dylib 0x00000001f5901bf0 abort_with_payload_wrapper_internal + [ : 104] 42 libsystem_kernel.dylib 0x00000001f5901b88 abort_with_payload_wrapper_internal 53 libobjc.A.dylib 0x00000001b0f6fa5c _objc_fatalv(unsigned long long, unsigned long long, char const*, char*) + [ : 116] 64 libobjc.A.dylib 0x00000001b0f6f9e8 _objc_fatalv(unsigned long long, unsigned long long, char const*, char*) 75 libobjc.A.dylib 0x00000001b0f42c24 weak_register_no_lock + [ : 392] 86 libobjc.A.dylib 0x00000001b0f485b0 objc_initWeak + [ : 436] 97 UIKitCore 0x00000001ba0fcde0 -[UIViewController viewDidMoveToWindow:shouldAppearOrDisappear:] + [ : 776] 108 UIKitCore 0x00000001b9fa5094 -[UIView(Internal) _didMoveFromWindow:toWindow:] + [ : 1232] 119 UIKitCore 0x00000001ba05b350 __45-[UIView(Hierarchy) _postMovedFromSuperview:]_block_invoke + [ : 112] 1210 CoreAutoLayout 0x00000001d4838e90 -[NSISEngine withBehaviors:performModifications:] + [ : 84] 1311 UIKitCore 0x00000001bafc7d40 -[UIView _postMovedFromSuperview:] + [ : 672] 1412 UIKitCore 0x00000001b9fa5fec -[UIView(Internal) _addSubview:positioned:relativeTo:] + [ : 1904] 1513 UIKitCore 0x00000001ba48d8e0 -[_UIKBCompatInputView addSubview:] + [ : 52] 1614 UIKitCore 0x00000001ba36d718 -[UICompatibilityInputViewController setInputMode:] + [ : 1028] 1715 UIKitCore 0x00000001ba48e528 -[UICompatibilityInputViewController shouldUpdateInputMode:] + [ : 228] 1816 CoreFoundation 0x00000001b7dea3b4 CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + [ : 148] 28 UIKitCore 0x00000001ba493f08 -[UIKeyboardTaskQueue performSingleTask:] + [ : 96] 3129 UIKitCore 0x00000001bab129e0 -[UIKeyboardImpl setInputMode:userInitiated:] + [ : 328] 3230 UIKitCore 0x00000001ba9dc758 -[UIKeyboardInputModeController _setCurrentInputMode:force:] + [ : 240] 3331 UIKitCore 0x00000001ba9e0304 -[UIKeyboardInputModeController switchToCurrentSystemInputMode] + [ : 52] 3432 UIKitCore 0x00000001baa020a8 -[UICompatibilityInputViewController resetInputModeInMainThread] + [ : 156] 3533 libdispatch.dylib 0x00000001bf3d3460 _dispatch_call_block_and_release + [ : 32] 3634 libdispatch.dylib 0x00000001bf3d4f88 _dispatch_client_callout + [ : 20] 3735 libdispatch.dylib 0x00000001bf3e37f4 _dispatch_main_queue_drain + [ : 928] 3836 libdispatch.dylib 0x00000001bf3e3444 _dispatch_main_queue_callback_4CF + [ : 44] 3937 CoreFoundation 0x00000001b7e4d6c8 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + [ : 16] 4038 CoreFoundation 0x00000001b7e2f02c __CFRunLoopRun + [ : 2036] 4139 CoreFoundation 0x00000001b7e33eb0 CFRunLoopRunSpecific + [ : 612] 4240 GraphicsServices 0x00000001f2029368 GSEventRunModal + [ : 164] 4341 UIKitCore 0x00000001ba329668 -[UIApplication _run] + [ : 888] 4442 UIKitCore 0x00000001ba3292cc UIApplicationMain + [ : 340] 4543 KYE_iOS 0x0000000104474848 0x1043e0000 + 608328 4644 (null) 0x00000001d672c960 0x0 + 7892814176

I have a Swift-SwiftUI app for MacOS that runs perfectly well (meaning no errors whatsoever) on an Intel MacBook Pro (16 GB ram) but crashed immediately when trying to run on an ARM MacBook Air (8 GB ram). The error in the app is SIGTRAP (Name space Signal, Code 5 Trace/BPT trap 5 (Terminating process exc handler 1496. Although the exe was build on the intel Mac, but for both platforms (Intel & ARM) seeking to troubleshoot this issue, I tried to clone the app to further debug it using Xcode within the ARM platform, just to get into a bigger issue: As soon as the app is cloned and read, Xcode crashes with error SIGABRT (Name space Signal, Code 6 Trace/BPT trap 6 (Terminating process exc handler 1006). That happens just by attempt to load the source code of the app within Xcode, which surprises me a lot. Xcode Version on the ARM 15.0.1 (15A507) Xcode Version on the Intel 15.2 (15C500b) OS on the ARM Sonoma 14.2 OS on the Intel Sonoma 14.2.1 As this App is intended to run MacOS 12 and above, I discarded the tiny difference between OS. As to Xcode, it confuses me, as in my view, it shouldn't crash at least before the time of building the exe file... Any help to troubleshoot this will be very much appreciated! Attached: Xcode "quit unexpectedly" crash log Xcode_Cred_Log.txt

I am facing this error on my SDK project. Could not identify what's the actual issue. I've added the Firebase crash logs below. Crashed: com.apple.root.default-qos 0 libdispatch.dylib 0x1a778 dispatch_channel_cancel + 12 1 libdispatch.dylib 0x1a778 dispatch_source_cancel + 12 2 libsystem_dnssd.dylib 0x2084 DNSServiceProcessResult + 860 3 Common 0x2df04 __swift_memcpy5_4 + 25916 4 Common 0x10b00 block_destroy_helper.10 + 188 5 libdispatch.dylib 0x26a8 _dispatch_call_block_and_release + 32 6 libdispatch.dylib 0x4300 _dispatch_client_callout + 20 7 libdispatch.dylib 0x744c _dispatch_queue_override_invoke + 928 8 libdispatch.dylib 0x15be4 _dispatch_root_queue_drain + 392 9 libdispatch.dylib 0x163ec _dispatch_worker_thread2 + 156 10 libsystem_pthread.dylib 0x1928 _pthread_wqthread + 228 11 libsystem_pthread.dylib 0x1a04 start_wqthread + 8

The app stucks on launch page when they tested in iPad Air 5th generation and iOS version 17.3.1 I tested the application in all available simulators

iPhone 16.0 16.0.2 系统上运行小组件出现问题， 其他系统没有问题 SendProcessControlEvent:toPid: encountered an error: Error Domain=com.apple.dt.deviceprocesscontrolservice Code=8 "Failed to show Widget 'com.jiduauto.iphone.jdcomiphoneWidget' error: Error Domain=FBSOpenApplicationServiceErrorDomain Code=5 "The request to open "com.apple.springboard" failed." UserInfo={NSLocalizedDescription=The request to open "com.apple.springboard" failed., NSLocalizedFailureReason=Unexpected error type., NSUnderlyingError=0x600002bbd7a0 {Error Domain=BSServiceConnectionErrorDomain Code=3 "XPC error received on message reply handler" UserInfo={BSErrorCodeDescription=OperationFailed, NSLocalizedFailureReason=XPC error received on message reply handler}}, BSErrorCodeDescription=InvalidResponse}." UserInfo={NSLocalizedDescription=Failed to show Widget 'com.jiduauto.iphone.jdcomiphoneWidget' error: Error Domain=FBSOpenApplicationServiceErrorDomain Code=5 "The request to open "com.apple.springboard" failed." UserInfo={NSLocalizedDescription=The request to open "com.apple.springboard" failed., NSLocalizedFailureReason=Unexpected error type., NSUnderlyingError=0x600002bbd7a0 {Error Domain=BSServiceConnectionErrorDomain Code=3 "XPC error received on message reply handler" UserInfo={BSErrorCodeDescription=OperationFailed, NSLocalizedFailureReason=XPC error received on message reply handler}}, BSErrorCodeDescription=InvalidResponse}., NSUnderlyingError=0x600002bbd5f0 {Error Domain=FBSOpenApplicationServiceErrorDomain Code=5 "The request to open "com.apple.springboard" failed." UserInfo={NSLocalizedDescription=The request to open "com.apple.springboard" failed., NSLocalizedFailureReason=Unexpected error type., NSUnderlyingError=0x600002bbd7a0 {Error Domain=BSServiceConnectionErrorDomain Code=3 "XPC error received on message reply handler" UserInfo={BSErrorCodeDescription=OperationFailed, NSLocalizedFailureReason=XPC error received on message reply handler}}, BSErrorCodeDescription=InvalidResponse}}} Domain: DTXMessage Code: 1 User Info: { DVTErrorCreationDateKey = "2024-02-19 08:02:14 +0000"; } System Information macOS Version 13.5.2 (Build 22G91) Xcode 15.0 (22265) (Build 15A240d) Timestamp: 2024-02-19T16:02:14+08:00

I have the following crash in swiftui that relates to memory reallocation, which I am not sure how to handle Crash.txt

Hello, We are investigating a serious crash impacting users on iOS 16 devices. The crash occurs on app start up. I’ve added the crash report here. This crash occurs in the dyld step. We believe the crash may be related to the binary size of the app. The crash does not occur on simulator or on debug mode. It only occurs on real devices on release mode. We recently introduced a new large binary. We believe the introduction of this framework may be causing this issue due to its large size. However, we don't believe the contents of the framework cause the crash. We've previously introduced very similar frameworks to this with no issue. Our last stable version of the app is 178 MB and our new build is 195 MB. crashlog.crash

I have Sims 4 downloaded onto my macbook and it has been working just fine until it started closing the application out of nowhere. A full crash report would come up everytime yet I do not understand code and need to know what the issue is. The game opens, and for a few minutes works until it simply closes out of nowhere. Here is the crash report: Crashed Thread: 22 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000164420150 Exception Codes: 0x0000000000000001, 0x0000000164420150 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [1224] VM Region Info: 0x164420150 is not in any region. Bytes after previous region: 344401 Bytes before following region: 18562736 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL __LINKEDIT 164364000-1643cc000 [ 416K] r--/rw- SM=COW ...thon370.dylib ---> GAP OF 0x1208000 BYTES __TEXT 1655d4000-1655d8000 [ 16K] r-x/rwx SM=COW ...process.dylib Thread 22 Crashed: 0 Simulation.dylib 0x1656e5060 0x16560c000 + 888928 1 Simulation.dylib 0x1656e5144 0x16560c000 + 889156 2 Simulation.dylib 0x165b51274 0x16560c000 + 5526132 3 libsystem_pthread.dylib 0x19152106c _pthread_start + 148 4 libsystem_pthread.dylib 0x19151be2c thread_start + 8 Thread 22 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0xffffffffffffffff x2: 0x0000000000000001 x3: 0x0000000000000001 x4: 0x0000000000000000 x5: 0x0000000001e84800 x6: 0x00000002a84b6af0 x7: 0x0000000170a76778 x8: 0x000000016441ff68 x9: 0x00000001ec891f40 x10: 0x0000000000000011 x11: 0x00000000000002ee x12: 0x0000000000000008 x13: 0x0000000000000004 x14: 0x0000000100000000 x15: 0x0000000000000000 x16: 0x00000001914e274c x17: 0x00000001f16c86e8 x18: 0x0000000000000000 x19: 0x0000000164436620 x20: 0x0000000164436628 x21: 0x0000000164436668 x22: 0x0000000000000002 x23: 0x000000016440fb60 x24: 0x00000001664bce10 x25: 0x00000000db89ff23 x26: 0x00000000811c9dc5 x27: 0x0000000166498000 x28: 0x0000000166498000 fp: 0x0000000170a76f90 lr: 0x11168001656e5144 sp: 0x0000000170a76f40 pc: 0x00000001656e5060 cpsr: 0x60001000 far: 0x0000000164420150 esr: 0x92000007 (Data Abort) byte read Translation fault

Guys I'm getting insane, I'm trying to create an app and I keep getting this error when I launch it from xcode to my iPhone 13, it happens randomly: sometimes really soon and sometimes after a while. I don't understand if it's a problem related to my app, but I don't think so as I can open it when not connected to the debugger and it doesn't seem to crash. Do you have any solutions?

I currently own an Apple Watch SE2 device. However, when I try to debug from the watch to the actual device, the connection loss issue occurs all too often. Once the connection is lost, it continues to try to connect in the Disconnected list on the Xcode "Devices and Simulators" screen and is in a loading state. Very often, even when the connection is established and you are trying to start debugging, it drops out. Xcode cannot debug properly on the actual device. I later found out that the Apple Watch SE2 does not support 5.0 Hz Wi-Fi, only 2.5 Hz. I think that might be the cause. Is this phenomenon less likely to occur if you debug on an actual device such as a regular Apple Watch 7/8/9 or Ultra model? In fact, if debugging is difficult with the Apple Watch SE model, I am wondering whether I should purchase an additional Apple Watch. Or is there another way to improve this issue? It would be nice if the Apple Watch could be debugged by connecting it to a Mac with an actual cable like the iPhone. I am wondering if there is a way to disable and enable network debugging in Xcode. In the past, debugging the watch using only Bluetooth with the iPhone in Xcode seemed to be more stable. Except for the Watch, the iPad doesn't have any major issues with Wi-Fi debugging on the iPhone.

We have app and notification extension both loading an agent lib to access the same files with read/write/delete operations. To avoid app and notification extension access the file simultaneously, we use boost::interprocess::file_lock when app enters foreground and notification extension didReceive notifications. If extension failed to grab file lock, it will skip loading agent and returns. If app failed to grab file lock, it will start a timer to keep trying while UI will display spinner. Sometimes we saw crash report from our app with: Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: RUNNINGBOARD 3735883980 Triggered by Thread: 0 The code 3735883980 indicate "deadlock" - The operating system terminated the app because it held on to a file lock or SQLite database lock during suspension. In sysdiagnose, we also see "[osservice<com.apple.InputUI>:1496] check if suspended process is holding locks" in runningboardd process. Does it mean that our app fail to unlock? We did lock when app enters foreground and unlock when app goes to background. Is there anything we did wrong? @implementation FileLock -(id)init { self = [super init]; if (nil != self) { // Find empty lock file, created if it doesn't exist. FILE *file = fopen(lockFile.c_str(), "a"); if (file) { fclose(file); } m_lock = boost::make_shared<boost::interprocess::file_lock>(lockFile.c_str()); } return self; } -(BOOL)lock { return m_lock->try_lock(); } -(void)unlock { return m_lock->unlock(); } @end func applicationDidBecomeActive(_ application: UIApplication) { if !bFileLockAcquired { if fileLock.lock() { bFileLockAcquired = true // load agent } else { lockTimer = Timer.scheduledTimer(withTimeInterval: 1.0, repeats: true, block: { _ in DispatchQueue.main.async { if fileLock.lock() { self.lockTimer?.invalidate() self.lockTimer = nil bFileLockAcquired = true // load agent } } }) } } func applicationDidEnterBackground(_ application: UIApplication) { self.lockTimer?.invalidate() self.lockTimer = nil fileLock.unlock() bFileLockAcquired = false }

React Native app crash on splash screen in release mode. In debug everything ok. Here is the error from XCode console. *** Terminating app due to uncaught exception 'RCTFatalException: Unhandled JS Exception: Error: invalid host', reason: 'Unhandled JS Exception: Error: invalid host, stack: @732:405 value@731:2737 @719:2589 h@2:1587 @718:591 h@2:1587 @708:753 h@2:1587 @6:206 h@2:1587 d@2:960 global code@5698:3 ' *** First throw call stack: ( 0 CoreFoundation 0x00000001107ae28d _exceptionPreprocess + 242 1 libobjc.A.dylib 0x0000000112157894 objc_exception_throw + 48 2 React 0x000000011043f1e8 RCTGetFatalHandler + 0 3 Rhino Dev 0x00000001043ed498 -[RCTExceptionsManager reportFatal:stack:exceptionId:] + 508 4 Rhino Dev 0x00000001043ede39 -[RCTExceptionsManager reportException:] + 1620 5 CoreFoundation 0x00000001107b4ebc invoking + 140 6 CoreFoundation 0x00000001107b21df -[NSInvocation invoke] + 302 7 CoreFoundation 0x00000001107b244f -[NSInvocation invokeWithTarget:] + 70 8 React 0x000000011047668b -[RCTModuleMethod invokeWithBridge:module:arguments:] + 583 9 React 0x0000000110478db0 _ZN8facebook5reactL11invokeInnerEP9RCTBridgeP13RCTModuleDatajRKN5folly7dynamicEiN12_GLOBAL__N_117SchedulingContextE + 574 10 React 0x00000001104789ad ___ZN8facebook5react15RCTNativeModule6invokeEjON5folly7dynamicEi_block_invoke + 110 11 libdispatch.dylib 0x000000011554e747 _dispatch_call_block_and_release + 12 12 libdispatch.dylib 0x000000011554f9f7 _dispatch_client_callout + 8 13 libdispatch.dylib 0x00000001155578c9 _dispatch_lane_serial_drain + 1127 14 libdispatch.dylib 0x0000000115558665 _dispatch_lane_invoke + 441 15 libdispatch.dylib 0x000000011556576e _dispatch_root_queue_drain_deferred_wlh + 318 16 libdispatch.dylib 0x0000000115564b69 _dispatch_workloop_worker_thread + 590 17 libsystem_pthread.dylib 0x0000000115a4ec47 _pthread_wqthread + 327 18 libsystem_pthread.dylib 0x0000000115a4db97 start_wqthread + 15 ) libc++abi: terminating due to uncaught exception of type NSException

I have a problem when try to connect the debug device to Xcode. When plug with the cable to connect iPhone with MacBook, enable Connect via network, then unplug iPhone from MacBook. App version: Xcode ver: 15.2 Failed wireless connection devices: iPhone XR (16.5) iPhone 12 Pro (16.2) iPhone XS Max (16.2) issue detail: Open "Devices and Simulators" on Xcode, and turn on the Connect via network. Conform wireless connection icon (like a earth symbol) is displayed, then disconnect wire. "iPhone xr is not connected" is displayed and cannot connect wirelessly. It seems like this problem is only occurs on iOS 16.2 and 16.5 *Note that I have read the Known Issues in Xcode 15.0.1 Release Notes, but I still can debug wirelessly with some other device having iOS older than 16.7 https://developer.apple.com/documentation/xcode-release-notes/xcode-15_0_1-release-notes Is there anyone has encountered this issue and found the root cause? Could you please help me find the solution for it?

The AVP is paired with Xcode and all software is up to date. Trying to copy shared cache symbols, haven't been able to debug on-device yet. It repeatedly gets stuck at 2%, 5%, has made it as high as 8% but just comes back to this: Previous preparation error: Unable to copy shared cache files. I'm sharing more visuals and strings in case others are having a similar issue. I've checked the Console and the "Show Recent Logs" that can be reached from Xcode's Device window but there's nothing there.

Hi everyone, my app is occasionally crashed on App Store. I have searched for this error on the internet but still not have any clues on how to fix it. Below are the information and crash logs Code Type: ARM-64 (Native) OS Version: iPhone OS 17.2.1 (21C66) Device: iPhone 15 Pro 0 CoreFoundation 0x1a8cde69c __exceptionPreprocess + 164 (NSException.m:249) 1 libobjc.A.dylib 0x1a0f67c80 objc_exception_throw + 60 (objc-exception.mm:356) 2 RN8it 0x10255a000 RCTFatal + 568 (RCTAssert.m:146) 3 RN8it 0x1025cb71c -[RCTExceptionsManager reportFatal:stack:exceptionId:] + 432 (RCTExceptionsManager.mm:68) 4 RN8it 0x1025cbf08 -[RCTExceptionsManager reportException:] + 1232 (RCTExceptionsManager.mm:135) 5 CoreFoundation 0x1a8c23794 __invoking___ + 148 (:-1) 6 CoreFoundation 0x1a8c2322c -[NSInvocation invoke] + 428 (NSForwarding.m:3411) 7 CoreFoundation 0x1a8c23054 -[NSInvocation invokeWithTarget:] + 64 (NSForwarding.m:3508) 8 RN8it 0x102588590 -[RCTModuleMethod invokeWithBridge:module:arguments:] + 388 (RCTModuleMethod.mm:584) 9 RN8it 0x10258a574 facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&, int, (anonymous namespace)::SchedulingContext) + 452 (RCTNativeModule.mm:183) 10 RN8it 0x10258a1c4 facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int)::$_0::operator()() const + 68 (RCTNativeModule.mm:104) 11 RN8it 0x10258a1c4 invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int) + 112 (RCTNativeModule.mm:95) 12 libdispatch.dylib 0x1b0be76a8 _dispatch_call_block_and_release + 32 (init.c:1530) 13 libdispatch.dylib 0x1b0be9300 _dispatch_client_callout + 20 (object.m:561) 14 libdispatch.dylib 0x1b0bf0894 _dispatch_lane_serial_drain + 748 (queue.c:3885) 15 libdispatch.dylib 0x1b0bf13c4 _dispatch_lane_invoke + 380 (queue.c:3976) 16 libdispatch.dylib 0x1b0bfc004 _dispatch_root_queue_drain_deferred_wlh + 288 (queue.c:6913) 17 libdispatch.dylib 0x1b0bfb878 _dispatch_workloop_worker_thread + 404 (queue.c:6507) 18 libsystem_pthread.dylib 0x212c0f964 _pthread_wqthread + 288 (pthread.c:2629) 19 libsystem_pthread.dylib 0x212c0fa04 start_wqthread + 8 (:-1)

Hi, a few of my customers are facing a crash on using the app. I am unable to reproduce the issue myself. Can you please help. Here is the crash log of a user. Mine is a SwiftUI app. Crash log of a user

help me understand the crash report this started happening from last update only Translated Report (Full Report Below) Process: dota2 [7353] Path: /Users/USER/Library/Application Support/Steam/*/dota2.app/Contents/MacOS/dota2 Identifier: com.valvesoftware.dota2 Version: 1.0.0 Code Type: X86-64 (Translated) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-02-18 18:00:45.9766 -0500 OS Version: macOS 14.3.1 (23D60) Report Version: 12 Anonymous UUID: 0F5E4D0D-9839-DF78-5C28-93F6D26A5763 Sleep/Wake UUID: 52D18CB1-ADD8-4A75-B6A1-C0CF4CF2A306 Time Awake Since Boot: 85000 seconds Time Since Wake: 1722 seconds System Integrity Protection: enabled Notes: PC register does not match crashing frame (0x0 vs 0x1032D1C08) Crashed Thread: 0 MainThrd Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000441f0f660002 Exception Codes: 0x0000000000000001, 0x0000441f0f660002 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [7353] VM Region Info: 0x441f0f660002 is not in any region. Bytes after previous region: 48357375344643 Bytes before following region: 65536781844478 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL Memory Tag 255 1823fb340000-1823fb380000 [ 256K] rw-/rwx SM=PRV ---> GAP OF 0x67960cc80000 BYTES MALLOC_MEDIUM 7fba08000000-7fba10000000 [128.0M] rw-/rwx SM=PRV Error Formulating Crash Report: PC register does not match crashing frame (0x0 vs 0x1032D1C08) Kernel Triage: VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter

I've recently started working with IPS files, specifically crash reports. According to the documentation there are a number of metadata keys included in these payloads, however, I have found a number that are present in real ips files from device but are not documented. Does anyone know what version of iOS these 'new' metadata keys were introduced? How about if they're expected or if I should treat them as optional. https://developer.apple.com/documentation/xcode/interpreting-the-json-format-of-a-crash-report#IPS-metadata { "app_name":"ApplicationNameHere", "timestamp":"2024-02-15 08:05:05.00 -0600", "app_version":"1.6.0", "slice_uuid":"6b1f9f4e-3025-364f-9847-914fc1fe14d1", "build_version":"800", "platform":2, "bundleID":"reverse.domainname.bundleidentifier", "share_with_app_devs":1, "is_first_party":0, "bug_type":"309", "os_version":"iPhone OS 17.3.1 (21D61)", "roots_installed":0, "name":"ApplicationNameHere", "incident_id":"1CF0B8A1-EB43-46B3-AA9F-CFA8A9259190" } The following keys are not in the documentation: app_name, os_version, slice_uuid, share_with_app_devs, is_first_party, roots_installed I created this feedback to request the documentation be updated with current state. FB13631161 - Developer Documentation: Update IPS metadata to reflect latest values found in IPS Metadata JSON

Background I have a SwiftUI app that uses OSLog and the new Logger framework. In my SwiftUI views, I would like to use something like Self._logChanges() to help debug issues. After some trial and error, I can see the messages appear in the System console log for the app I am debugging using the com.apple.SwiftUI subsystem. Problem I'd like to see those same messages directly in Xcode's console window so I can filter them as needed. How do I do that? Thanks! -Patrick

Hello, I developed a flutter app. But its crashing in review I got. I am attaching the crash report. Can someone help in that. Thanks so much crashlog-91B61DEE-21AB-4CDD-B223-316F7639CA78.txt crashlog-515BA87C-E0D0-47F8-B8C5-7A9E28631EE2.txt crashlog-475FD24A-0BF4-4745-9F8B-83FCA63571FC.txt