I have created an App ,tested on simulator and works very well. Developed using react native expo. But after creating an TestFlight mode for testing , it crashed on startup. I am able to retrieve logs from crashed app, but I could not able to understand anything about cause of this crashed. Any help would be highly appreciated. LOG `Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: ParrotProjectv2 [647] Triggered by Thread: 7 Application Specific Information: abort() called Thread 7 name: Dispatch queue: expo.modules.AsyncFunctionQueue Thread 7 Crashed: 0 libsystem_kernel.dylib 0x1d6241578 __pthread_kill + 8 1 libsystem_pthread.dylib 0x1f70c0118 pthread_kill + 268 2 libsystem_c.dylib 0x19e7ac178 abort + 180 3 libc++abi.dylib 0x1f6ffebf8 abort_message + 132 4 libc++abi.dylib 0x1f6fee444 demangling_terminate_handler() + 348 5 libobjc.A.dylib 0x190321ea4 _objc_terminate() + 144 6 libc++abi.dylib 0x1f6ffdfbc std::__terminate(void (*)()) + 16 7 libc++abi.dylib 0x1f6ffdf60 std::terminate() + 56 8 libdispatch.dylib 0x19e74bec0 _dispatch_client_callout + 40 9 libdispatch.dylib 0x19e753534 _dispatch_lane_serial_drain + 668 10 libdispatch.dylib 0x19e7540a4 _dispatch_lane_invoke + 384 11 libdispatch.dylib 0x19e75ecdc _dispatch_workloop_worker_thread + 648 12 libsystem_pthread.dylib 0x1f70b9ddc _pthread_wqthread + 288 13 libsystem_pthread.dylib 0x1f70b9b7c start_wqthread + 8

We have Xamarin Form application developed which is running on iPhone. But when we trial debug or install our application on simulator IOS 17. Our application cannot running. We using Xcode 15 Beta and Visual Studio for Mac 17.6.3. Please let me know, if you can give us suggestion. Thanks

Hello Guys. Crash when launching the app on iOS12. There seems to be an optimization problem, but I don't know how to deal with it. iOS Deployment Taget is iOS12.0. I'm using Xcode15 Beta8. Any ideas on how to fix this? Thanks. MyApp(2987,0x104a82b80) malloc: *** error for object 0x105591ed0: pointer being freed was not allocated MyApp(2987,0x104a82b80) malloc: *** set a breakpoint in malloc_error_break to debug

When I use tensorflow to write maskrcnn, bus error will be reported. It is not a matter of memory, but a problem of the system itself. I hope it can be solved

Hi Team, Our play-store app is crashing using below logs. This crash is mostly reported for iOS 16.6.0 devices. Please suggest if we have any finding or RCA for this crash. We tried and not able to reproduce this crash and seems this crash impact huge user base of our App Store APP. com.apple.main-thread 0 libsystem_kernel.dylib 0xca4 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x13b74 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x13e4c mach_msg_overwrite + 540 3 libsystem_kernel.dylib 0x11e8 mach_msg + 24 4 CoreFoundation 0x79024 __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x7a250 __CFRunLoopRun + 1208 6 CoreFoundation 0x7f3ec CFRunLoopRunSpecific + 612 7 GraphicsServices 0x135c GSEventRunModal + 164 8 UIKitCore 0x39cf58 -[UIApplication _run] + 888 9 UIKitCore 0x39cbbc UIApplicationMain + 340 10 SURFBoard Central 0x24050 main + 51 (AppDelegate.swift:51) 11 ??? 0x1d3594dec (Missing)

Hello, I have sandboxed mac app which is launching a helper app. The main app has sandbox enabled and has get-task-allow entitlement. From main app I launch[1] a helper which is an application bundle located in Contents/Helpers of the main bundle. The helper has sandbox enabled and com.apple.security.inherit entitlement. Currently I have a problem attaching debugger to helper process or getting access to location services from it (but that's probably different issue). I checked the responsible process and it seems to set up to correct PID of the main application. The Xcode is reporting "Not allowed to attach to process" error and I see the same in the log: macOSTaskPolicy: (com.apple.debugserver) may not get the task control port of (com.****) (pid: 31628): (com.****) is hardened, (com.****) doesn't have get-task-allow, (com.apple.debugserver) is a declared debugger(com.apple.debugserver) is not a declared read-only debugger To add a more of the context what I'm trying to achieve is that we run certain parts of our app in separate child processes so we can restart then if anything goes wrong [2]. So I have few questions: Do I need to launch the helper (child) process a particular way to be able to attach debugger to it? Is there a tool to inspect sandboxes (rules applied and the inheritance)? Do I really need to explicitly enable sandboxing and inheritance on the helper app, doesn't it run in the parent' s sandbox anyway? Thank you. [1] We use boost::child_process for launching the helper, which is using popen behind the scene, but I have the same experience with NSTask. [2] I know that's what XPCServices are for but don't ask :-)

Hello all, I have an application which retrieves URL from browser using accessibility. From time to time I am having this crash and I don't know the reason for it. Could you please help me? This is the stacktrace: It is happening on MacOS 13.5 and it happens on an application built for x86_64 and arm64

I attached the crash log below. Does anyone have any ideas? Cheers. 2023-09-10_07-35-20.6213_+0800-32374179b9259ba69fc5d85abb0772cb36a3a1f1.crash

Hello! In our website, we allow members to follow private RSS feeds on their Podcasts app easily with the click of a button. Underneath the button is a link in the format of: podcast://example.rssurl.com # Example With this URL scheme, the Podcasts app launches correctly and shows the "Follow a Show by URL" input box, with the private RSS feed URL prefilled. However, the prefilled URL uses HTTP instead of HTTPS. So, the example link above (podcast://example.rssurl.com) when clicked is converted to: http://example.rssurl.com in the "Follow a Show by URL" input box in the Podcasts app. We noticed the HTTP form of the URL does not work well, as it sometimes fail to follow the show. Clicking on "Follow" would simply close the box and cause nothing to happen, not even error messages. We then tested with HTTPS by manually inserting the URL like so: https://example.rssurl.com and this would always work. However, this is not ideal as our users would have to manually paste in the URL all the time. It'd be great if the Podcasts URL scheme above would automatically prefill the "Follow a Show by URL" input box with the HTTPS form instead. Is there a way to force this behavior or is this intended from Apple's side? Thank you!

Hi App works in iPhone simulator on mac but crashes on physical device at startup when deployed via TestFlight. Logs from both the physical device and test flight attched. Any help would be appreciated. Thanks Regards Device-Log-MyApp-2023-09-12-154933.ips-post-1.synced TestFlight-crashlog.crash-post-1.txt

iOS app targeting iOS 15.5 has been working fine up to iOS 17 Beta (21A5326a). With iOS 17 RC (21A329) it is now crashing on launch. Anybody experiencing similar issue?

*** Crash Message: -[UIWindow _accessibilityFindSubviewDescendant:]: unrecognized selector sent to instance 0x13118ca70 *** we collected more than 10K+ reports with same call stack, the almost form Accessibility Kit. but no idea how to fix it and no reason why. could take some help please 4. CoreFoundation 0x00000001d0735900 _CF_forwarding_prep_0 + 96 5 AccessibilitySettingsLoader 0x000000025a97608c 70360165-7515-35AD-9723-C4719EB48D13 + 102540 6 AccessibilityUtilities 0x00000001d9bfa720 AXPerformSafeBlockWithErrorHandler + 112 7 AccessibilityUtilities 0x00000001d9bfb258 AXPerformSafeBlock + 56 8 AccessibilitySettingsLoader 0x000000025a976014 70360165-7515-35AD-9723-C4719EB48D13 + 102420 9 AccessibilitySettingsLoader 0x000000025a975ed8 70360165-7515-35AD-9723-C4719EB48D13 + 102104 10 AccessibilitySettingsLoader 0x000000025a97720c 70360165-7515-35AD-9723-C4719EB48D13 + 107020 11 AccessibilityUtilities 0x00000001d9c7be40 265BEA5E-C36A-3E51-A119-A3FD42F3DB5C + 552512 12 AXCoreUtilities 0x00000001db850530 AXPerformBlockSynchronouslyOnMainThread + 72 13 AXCoreUtilities 0x00000001db84faa0 774B92BE-E295-3FDC-99A4-5EFB55BA70C5 + 6816 14 AccessibilityUtilities 0x00000001d9c7b8d0 265BEA5E-C36A-3E51-A119-A3FD42F3DB5C + 551120 15 AccessibilitySettingsLoader 0x000000025a976ed4 70360165-7515-35AD-9723-C4719EB48D13 + 106196 16 AccessibilityUtilities 0x00000001d9c74178 265BEA5E-C36A-3E51-A119-A3FD42F3DB5C + 520568 17 AccessibilityUtilities 0x00000001d9bfff54 265BEA5E-C36A-3E51-A119-A3FD42F3DB5C + 44884 18 AccessibilityUtilities 0x00000001d9bfca28 265BEA5E-C36A-3E51-A119-A3FD42F3DB5C + 31272 19 libdispatch.dylib 0x00000001d7b7feac 5D16936B-4E4C-3276-BA7A-69C9BC760ABA + 16044

Hello, I have a Cocoa application from which I fork a new process (helper sort of) and it crashes on fork due to some cleanup code probably registered with pthreads_atfork() in Network framework. This is crash from the child process: Application Specific Information: *** multi-threaded process forked *** BUG IN CLIENT OF LIBPLATFORM: os_unfair_lock is corrupt Abort Cause 258 crashed on child side of fork pre-exec Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_platform.dylib 0x194551238 _os_unfair_lock_corruption_abort + 88 1 libsystem_platform.dylib 0x19454c788 _os_unfair_lock_lock_slow + 332 2 Network 0x19b1b4af0 nw_path_shared_necp_fd + 124 3 Network 0x19b1b4698 -[NWConcrete_nw_path_evaluator dealloc] + 72 4 Network 0x19af9d970 __nw_dictionary_dispose_block_invoke + 32 5 libxpc.dylib 0x194260210 _xpc_dictionary_apply_apply + 68 6 libxpc.dylib 0x19425c9a0 _xpc_dictionary_apply_node_f + 156 7 libxpc.dylib 0x1942600e8 xpc_dictionary_apply + 136 8 Network 0x19acd5210 -[OS_nw_dictionary dealloc] + 112 9 Network 0x19b1beb08 nw_path_release_globals + 120 10 Network 0x19b3d4fa0 nw_settings_child_has_forked() + 312 11 libsystem_pthread.dylib 0x100c8f7c8 _pthread_atfork_child_handlers + 76 12 libsystem_c.dylib 0x1943d9944 fork + 112 (...) I'm trying to create a child process with boost::process::child which does basically just a fork() followed by execv() and I do it before the - [NSApplication run] is called. Is it know bug or behavior which I've run into? Also what is a correct way to spawn child processes in Cocoa applications? As far as my understanding goes the basically all the available APIs (e.g. posix, NSTask) should be more or less the same thing calling the same syscalls. So forking the process early before main run loop starts and not starting another NSApplication in forked child should be ok ...or not?

I have created a simple debug app using Swift/SwiftUI to understand this issue I have seen in my app. The debug app is just a VStack with .border(Color.red). It has text in the upper left, upper right, and bottom so the red rectangle goes around the entire screen. This is done just using VStack{}, HStack{}, Text(), and Spacer(). I have my debug app running and then bring up another app (gmail, google keep, and duck-duck-go browser all work). I open the keyboard in this other app. I swipe my finger from left to right on the bottom of the screen to go back to my app. When it first opens it looks correct but within a second or two the bottom of the red rectangle and the word on the bottom of my debug app move up about where they would be if there was a keyboard, but there is no keyboard. Some findings: Rotating the iPad does not fix the issue. With stage manager off this doesn't happen. Adding "sendAction(#selector(UIResponder.resignFirstResponder), to: nil, from: nil, for: nil)" to a UIApplication extension and calling that doesn't fix it. Adding a TextField() and touching that to bring up the keyboard and then calling the UIApplication extension does fix it. Going to another app and back fixes it assuming the other app doesn't have the keyboard open. Not all applications with the keyboard open will cause this issue. Issue happens in landscape and portrait rotation If I add a GeometryReader and add Text() to show it and the UIScreen.main.bounds, the bounds don't change with/without issue but geometry does My system: 11in M1 iPad pro running 16.6.1. 512GB with Stage Manager on Xcode 14.3.1 Other apps don't have this issue so what am I missing? Thanks for any help. The debug app: struct ContentView: View { var body: some View { VStack { HStack { Text("Top") Spacer() Text("Top") } Spacer() Text("Bottom") }.border(Color.red) } } ...Gary

Hello! Could please someone help me with such question: in Xcode I could see that there are two possible destinations for Apple Vision - Apple vision vs Apple vision (Designed for iPad). So while I tried to test my app, I noticed that it is possible that my app crashes on Apple Vision for visionOs sdk, but runs on the designed for iPad version and when launched they looks differently. Does it mean that if I want to make sure that my app works correctly for real device, then I should test it on the Apple Vision for visionOs sdk?

Howdy all, I'm in the process of eliminating some compiler warnings in a legacy project, and have come across a compiler warning for the usage of extern void DebugStr(ConstStr255Param debuggerMsg), defined in MacTypes.h as part of CarbonCore-769-1. I've looked through Apple's documentation for Cocoa and the MacOSX13.1 SDK but haven't found any leads on what I could/should replace it with. Can anyone point me in the right direction? Thanks!!

iOS16 above 0 CoreFoundation ___exceptionPreprocess + 164 1 libobjc.A.dylib _objc_exception_throw + 60 2 Foundation -[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:] 3 UIKitCore ___UIKIT_DID_NOT_RECEIVE_A_REMOTE_CACONTEXT_FROM_COREANIMATION_INDICATING_A_POSSIBLE_BACKBOARDD_CRASH + 484 4 UIKitCore ___UIKIT_IS_REQUESTING_A_CACONTEXT_FROM_COREANIMATION + 64 5 UIKitCore +[_UIContextBinder createContextForBindable:withSubstrate:] + 400 6 UIKitCore -[_UIContextBinder _contextForBindable:] + 112 7 UIKitCore -[_UIContextBinder updateBindableOrderWithTest:force:] + 304 8 UIKitCore -[_UIContextBinder createContextsWithTest:creationAction:] + 80 9 UIKitCore -[UIWindowScene _prepareForResume] + 148 10 UIKitCore -[UIScene _emitSceneSettingsUpdateResponseForCompletion:afterSceneUpdateWork:] + 756 11 UIKitCore -[UIScene scene:didUpdateWithDiff:transitionContext:completion:] + 244 12 UIKitCore -[UIApplicationSceneClientAgent scene:handleEvent:withCompletion:] + 336 13 FrontBoardServices -[FBSScene updater:didUpdateSettings:withDiff:transitionContext:completion:] + 420 14 FrontBoardServices ___94-[FBSWorkspaceScenesClient _queue_updateScene:withSettings:diff:transitionContext:completion:]_block_invoke_2 + 152 15 FrontBoardServices -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 168 16 FrontBoardServices ___94-[FBSWorkspaceScenesClient _queue_updateScene:withSettings:diff:transitionContext:completion:]_block_invoke + 344 17 libdispatch.dylib __dispatch_client_callout + 20 18 libdispatch.dylib __dispatch_block_invoke_direct + 264 19 FrontBoardServices ___FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 52 NSInternalInconsistencyException Failed to create remote render context Lifecycle 09-16 12:49:47.944 UIApplication WillResignActive 09-16 12:49:48.484 UIApplication DidEnterBackground 09-16 12:53:38.998 UIApplication WillEnterForeground It seems, app becomes inactive before it 'willEnterForeground',then crash,I do not have any ideas of what happen.

My xcode Version is 14.3.1 (14E300c) You may be able to resolve the issue by installing the latest version of Xcode from the Mac App Store or developer.apple.com. [missing string: 869a8e318f07f3e2f42e11d435502286094f76de] But there is no update on mac app store my system is m1 pro.

We've got hundreds of crashes in our SwiftUI app which we think are "silent" crashes as there are no complaints from clients and yet - it happens on the main thread in the foreground so I'm not completely sure. The annoying thing is that we have no idea by the stack trace what is causing this issue, I feel helpless as this is causing some very loud noise through management and honestly - myself who wants to have this noise cleared. this particular crash is the highest impact (one of a few different weird crashes in our app without clear stack trace) 0 SwiftUI 0x895d90 OUTLINED_FUNCTION_2 + 836 1 SwiftUI 0x895da8 OUTLINED_FUNCTION_2 + 860 2 SwiftUI 0x1329880 OUTLINED_FUNCTION_2 + 424 3 SwiftUI 0x6806c OUTLINED_FUNCTION_441 + 584 4 SwiftUI 0x481b0 OUTLINED_FUNCTION_194 + 544 5 UIKitCore 0x1b7194 -[UIViewController removeChildViewController:notifyDidMove:] + 128 6 UIKitCore 0x77d6e8 -[UINavigationController removeChildViewController:notifyDidMove:] + 80 7 UIKitCore 0x205224 -[UIViewController dealloc] + 768 8 UIKitCore 0x1036c -[UINavigationController viewDidDisappear:] + 372 9 UIKitCore 0xd9c4 -[UIViewController _setViewAppearState:isAnimating:] + 1012 10 UIKitCore 0x46e61c -[UIViewController __viewDidDisappear:] + 136 11 UIKitCore 0x7ec024 __64-[UIViewController viewDidMoveToWindow:shouldAppearOrDisappear:]_block_invoke_3 + 44 12 UIKitCore 0x1a3f24 -[UIViewController _executeAfterAppearanceBlock] + 84 13 UIKitCore 0x1a3e68 -[_UIAfterCACommitBlock run] + 72 14 UIKitCore 0x1a3d9c -[_UIAfterCACommitQueue flush] + 176 15 UIKitCore 0x1a3ca8 _runAfterCACommitDeferredBlocks + 496 16 UIKitCore 0x3f530 _cleanUpAfterCAFlushAndRunDeferredBlocks + 108 17 CoreFoundation 0x43564 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 28 18 CoreFoundation 0xabd9c __CFRunLoopDoBlocks + 368 19 CoreFoundation 0x7bbbc __CFRunLoopRun + 856 20 CoreFoundation 0x80ed4 CFRunLoopRunSpecific + 612 21 GraphicsServices 0x1368 GSEventRunModal + 164 22 UIKitCore 0x3a23d0 -[UIApplication _run] + 888 23 UIKitCore 0x3a2034 UIApplicationMain + 340 24 SwiftUI 0x1d1014 OUTLINED_FUNCTION_895 + 2420 25 SwiftUI 0x13216c block_copy_helper.1 + 388 26 SwiftUI 0x11b4bc OUTLINED_FUNCTION_901 + 2868 Number 27 will be our app's Main function and that it - no other trace of our apps code. Firebase is saying this happens 100% on iOS 16 only and always on the foreground. How can I get to the bottom of this? how can I debug such a crash?

Hi team, We found that the app reported a lot of crash stacks, and the top of the stack had the libxpc library feature, but we could not find the reason. These issues have only emerged since iOS 16 and are growing, can you provide some clues or provide some solutions? Thanks! Crash backtrace can be seen as follows. _ OS Version: 16.6.1 (20G81) Report Version: 104 SDK start time: 2023-09-20 18:42:40 RDM SDK Version: 2.7.27.1 RDM user id : 119902290602 RDM DeviceId: 0DB20076-F323-468F-9EEC-080B77A00E05 RDM APP KEY: 7c35edbf90 Last Exception : 0 libxpc.dylib 0x000000020a019e98 __xpc_dictionary_insert + 96 1 libxpc.dylib 0x000000020a019e84 __xpc_dictionary_insert + 76 2 libxpc.dylib 0x000000020a01b944 __xpc_dictionary_deserialize_apply + 68 3 libxpc.dylib 0x000000020a01b8cc __xpc_dictionary_apply_wire_f + 136 4 libxpc.dylib 0x000000020a018da4 __xpc_dictionary_deserialize + 108 5 libxpc.dylib 0x000000020a00cdf4 __xpc_array_deserialize + 204 6 libxpc.dylib 0x000000020a01b9ec __xpc_dictionary_unpack_value + 120 7 libxpc.dylib 0x000000020a01bbf0 __xpc_dictionary_unpack_value_and_vend + 28 8 libxpc.dylib 0x000000020a01a4c4 __xpc_dictionary_look_up + 156 9 libxpc.dylib 0x000000020a01b094 _xpc_dictionary_get_array + 20 10 libdns_services.dylib 0x000000020a0b9a28 ____dnssd_client_connection_block_invoke_2 + 320 11 libxpc.dylib 0x000000020a015af0 __xpc_connection_call_event_handler + 152 12 libxpc.dylib 0x000000020a015f20 __xpc_connection_mach_event + 992 13 libdispatch.dylib 0x00000001b1657f6c __dispatch_client_callout4 + 20 14 libdispatch.dylib 0x00000001b16746ec __dispatch_mach_msg_invoke + 468 15 libdispatch.dylib 0x00000001b165f40c __dispatch_lane_serial_drain + 372 16 libdispatch.dylib 0x00000001b1675438 __dispatch_mach_invoke + 448 17 libdispatch.dylib 0x00000001b165f40c __dispatch_lane_serial_drain + 372 18 libdispatch.dylib 0x00000001b16600a4 __dispatch_lane_invoke + 384 19 libdispatch.dylib 0x00000001b166acdc __dispatch_workloop_worker_thread + 648 20 libsystem_pthread.dylib 0x0000000209fc1ddc __pthread_wqthread + 288 Exception Type: SIGSEGV SEGV_ACCERR Exception Codes: fault addr: 0x0000000000000036 Crashed Thread: 7 _