I'm getting a filed to diagnose for expression; submit a bug report (http://swift.org

Hello, I have a problem with an iOS app that is deployed via the MDM system Intune. The app closes immediately after starting. The APP works without distribution via the MDM. Devices with iOS 17 also work. I am attaching a crash report. (txt is ips) Unfortunately I have no idea how to solve the problem because it only occurs via the MDM and therefore I cannot debug it. The problem occurs in production environment. Please help me with the solution. Insight Mobile-2024-06-24-144828.txt Best regards Moritz

Hi there, We recently released our app and got one production crash that can not be reproduced by our developers. It happens only on iOS 17.5.1 and the crash seems to be related to STWebpageController init at app start. The crash number is increasing fast but we have no idea about why it happens. Please help us to check the crash report below: Role: Foreground OS Version: iPhone OS 17.5.1 (21F90) Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Triggered by Thread: 0 Last Exception Backtrace: 0 CoreFoundation 0x1a29fcf20 __exceptionPreprocess + 164 (NSException.m:249) 1 APP_NAME 0x105e9e344 crashpad::(anonymous namespace)::HANDLE_UNCAUGHT_NSEXCEPTION(objc_object*, char const*) + 700 (exception_processor.mm:306) 2 APP_NAME 0x105e9d640 crashpad::(anonymous namespace)::ObjcExceptionPreprocessor(objc_object*) + 2544 (exception_processor.mm:513) 3 libobjc.A.dylib 0x19a8a6018 objc_exception_throw + 60 (objc-exception.mm:356) 4 Foundation 0x1a1f03868 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 188 (NSException.m:252) 5 ScreenTime 0x226860b2c __31-[STWebpageController loadView]_block_invoke + 448 (STWebpageController.m:140) 6 UIKitCore 0x1a55ae418 __146-[NSExtension(UIViewControllerAdditions) _instantiateViewControllerWithInputItems:asAccessory:traitCollection:listenerEndpoint:connectionHandler:]_block_invoke.29 + 268 (NSExtension_UIKitAdditions.m:96) 7 libdispatch.dylib 0x1aa8a013c _dispatch_call_block_and_release + 32 (init.c:1530) 8 libdispatch.dylib 0x1aa8a1dd4 _dispatch_client_callout + 20 (object.m:576) 9 libdispatch.dylib 0x1aa8b05a4 _dispatch_main_queue_drain + 988 (queue.c:7898) 10 libdispatch.dylib 0x1aa8b01b8 _dispatch_main_queue_callback_4CF + 44 (queue.c:8058) 11 CoreFoundation 0x1a29cf710 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 (CFRunLoop.c:1780) 12 CoreFoundation 0x1a29cc914 __CFRunLoopRun + 1996 (CFRunLoop.c:3149) 13 CoreFoundation 0x1a29cbcd8 CFRunLoopRunSpecific + 608 (CFRunLoop.c:3420) 14 GraphicsServices 0x1e787c1a8 GSEventRunModal + 164 (GSEvent.c:2196) 15 UIKitCore 0x1a500490c -[UIApplication _run] + 888 (UIApplication.m:3713) 16 UIKitCore 0x1a50b89d0 UIApplicationMain + 340 (UIApplication.m:5303) 17 APP_NAME 0x104dbc5c0 AppMain + 444 (app_exe_main.mm:128) 18 APP_NAME 0x104dbc630 main + 12 (app_exe_main.mm:135) 19 dyld 0x1c607de4c start + 2240 (dyldMain.cpp:1298) Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001ebab742c __pthread_kill + 8 (:-1) 1 libsystem_pthread.dylib 0x00000001ff856c0c pthread_kill + 268 (pthread.c:1721) 2 libsystem_c.dylib 0x00000001aa95aba0 abort + 180 (abort.c:118) 3 libc++abi.dylib 0x00000001ff774ca4 abort_message + 132 (abort_message.cpp:78) 4 libc++abi.dylib 0x00000001ff764e5c demangling_terminate_handler() + 348 (cxa_default_handlers.cpp:77) 5 libobjc.A.dylib 0x000000019a8c1e2c _objc_terminate() + 144 (objc-exception.mm:496) 6 ourSdk 0x0000000108d8bc40 FIRCLSTerminateHandler() + 500 (FIRCLSException.mm:0) 7 libc++abi.dylib 0x00000001ff774068 std::__terminate(void (*)()) + 16 (cxa_handlers.cpp:59) 8 libc++abi.dylib 0x00000001ff77400c std::terminate() + 108 (cxa_handlers.cpp:88) 9 libdispatch.dylib 0x00000001aa8a1de8 _dispatch_client_callout + 40 (object.m:579) 10 libdispatch.dylib 0x00000001aa8b05a4 _dispatch_main_queue_drain + 988 (queue.c:7898) 11 libdispatch.dylib 0x00000001aa8b01b8 _dispatch_main_queue_callback_4CF + 44 (queue.c:8058) 12 CoreFoundation 0x00000001a29cf710 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 (CFRunLoop.c:1780) 13 CoreFoundation 0x00000001a29cc914 __CFRunLoopRun + 1996 (CFRunLoop.c:3149) 14 CoreFoundation 0x00000001a29cbcd8 CFRunLoopRunSpecific + 608 (CFRunLoop.c:3420) 15 GraphicsServices 0x00000001e787c1a8 GSEventRunModal + 164 (GSEvent.c:2196) 16 UIKitCore 0x00000001a500490c -[UIApplication _run] + 888 (UIApplication.m:3713) 17 UIKitCore 0x00000001a50b89d0 UIApplicationMain + 340 (UIApplication.m:5303) 18 APP_NAME 0x0000000104dbc5c0 AppMain + 444 (app_exe_main.mm:128) 19 APP_NAME 0x0000000104dbc630 main + 12 (app_exe_main.mm:135) 20 dyld 0x00000001c607de4c start + 2240 (dyldMain.cpp:1298)

We have a Privileged Helper tool that we install with SMJobBless. I would like to debug it. I've added WaitForDebugger in our helper tool launchd plist and it does wait. But I can't attach to it via Debug->Attach to Process in Xcode with error: Code: 3 Failure Reason: tried to attach to process as user 'myusername' and process is running as user 'root' I set Debug process as: root in scheme settings. But I'm not sure if it does anything since I'm not running this particular scheme at the moment of attach. I tried unsuccessfully to set "Wait for the executable to be launched" but I had to create a new scheme for it since helper is built as part of the main app so maybe I did something wrong. Am I doing something wrong or is it not possible to attach to root process?

I am getting error after XCode build completes in the simulator. Not able to install app in any simulator. Getting a popup with title LLDB provided no error string. and on tapping more details getting below error Domain: IDEDebugSessionErrorDomain Code: 3 Failure Reason: LLDB provided no error string. User Info: { DVTErrorCreationDateKey = "2024-06-24 09:28:54 +0000"; DVTRadarComponentKey = 855031; IDERunOperationFailingWorker = DBGLLDBLauncher; RawUnderlyingErrorMessage = "LLDB provided no error string."; } -- Could not launch <AppName> Domain: IDEDebugSessionErrorDomain Code: 3 Failure Reason: LLDB provided no error string. User Info: { DVTRadarComponentKey = 855031; IDERunOperationFailingWorker = DBGLLDBLauncher; RawUnderlyingErrorMessage = "LLDB provided no error string."; } -- Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { "device_model" = "iPhone14,6"; "device_osBuild" = "17.5 (21F79)"; "device_platform" = "com.apple.platform.iphonesimulator"; "dvt_coredevice_version" = "355.28"; "dvt_mobiledevice_version" = "1643.100.60"; "launchSession_schemeCommand" = Run; "launchSession_state" = 1; "launchSession_targetArch" = arm64; "operation_duration_ms" = 7177; "operation_errorCode" = 3; "operation_errorDomain" = IDEDebugSessionErrorDomain; "operation_errorWorker" = DBGLLDBLauncher; "operation_name" = IDERunOperationWorkerGroup; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 3; "param_destination_isProxy" = 0; "param_destination_platform" = "com.apple.platform.iphonesimulator"; "param_diag_MainThreadChecker_stopOnIssue" = 0; "param_diag_MallocStackLogging_enableDuringAttach" = 0; "param_diag_MallocStackLogging_enableForXPC" = 1; "param_diag_allowLocationSimulation" = 1; "param_diag_checker_tpc_enable" = 0; "param_diag_gpu_frameCapture_enable" = 0; "param_diag_gpu_shaderValidation_enable" = 0; "param_diag_gpu_validation_enable" = 0; "param_diag_memoryGraphOnResourceException" = 0; "param_diag_queueDebugging_enable" = 1; "param_diag_runtimeProfile_generate" = 0; "param_diag_sanitizer_asan_enable" = 0; "param_diag_sanitizer_tsan_enable" = 0; "param_diag_sanitizer_tsan_stopOnIssue" = 0; "param_diag_sanitizer_ubsan_stopOnIssue" = 0; "param_diag_showNonLocalizedStrings" = 0; "param_diag_viewDebugging_enabled" = 1; "param_diag_viewDebugging_insertDylibOnLaunch" = 1; "param_install_style" = 0; "param_launcher_UID" = 2; "param_launcher_allowDeviceSensorReplayData" = 0; "param_launcher_kind" = 0; "param_launcher_style" = 0; "param_launcher_substyle" = 0; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_structuredConsoleMode" = 1; "param_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphonesimulator17.5"; "sdk_osVersion" = "17.5"; "sdk_variant" = iphonesimulator; } -- System Information macOS Version 14.4.1 (Build 23E224) Xcode 15.4 (22622) (Build 15F31d) Timestamp: 2024-06-24T14:58:54+05:30

What are we supposed to use now, since Debugger() was deprecated in 10.8:

Hi, I've just updated XCode 15.4 (15F31d) and on every second run XCoede is crashing and giving me the attached crash report. This was not happening with my previous version Xcode 15.0. I've attached part of the log, I cannot post the entire file because of restrictions on about attachments. Thank you! Log crash

I am having problems building an Unreal project in Xcode. The problem starts when the compiler starts to build a custom made plugin, that works perfectly fine on windows. When looking at the log, it seems that I will have to rebuild the plugin for macOS-arm64, does anyone have some ideas how I should approach? Showing All Messages ------ Building 4 action(s) started ------ [1/4] Link [Apple] Trancendent Undefined symbols for architecture arm64: "ExampleLibraryFunction()", referenced from: FTrancendantMetaNodesModule::StartupModule() in Module.TrancendantMetaNodes.cpp.o ld: symbol(s) not found for architecture arm64 /Users/Shared/Epic Games/UE_5.3/ld:1:1: ignoring file /Users/nicolaslefevre/Desktop/KanuziTemple/Plugins/TrancendantMetaNodes/Source/ThirdParty/TrancendantMetaNodesLibrary/Mac/Release/libExampleLibrary.dylib, building for macOS-arm64 but attempting to link with file built for macOS-x86_64 Total time in Parallel executor: 2.18 seconds Total execution time: 2.95 seconds /Users/Shared/Epic Games/UE_5.3/clang:1:1: linker command failed with exit code 1 (use -v to see invocation)

hi im runing beta on my macbook pro m1 and after i insert one 256gb sd it gets corrupted!! even after i reformat it, its gets corrupted once again, im trying with another one and do it also. anyone have a problem like this?? the two micro ds have fat32 format precaution !!

Hello, I am wondering if anyone else has seen this bug: Create a multiline TextField like so: TextField("a string", text: $myDataStore.placeholder, axis: .vertical) .accessibilityIdentifier("placeholder") .multilineTextAlignment(.leading) .lineLimit(...3) .textFieldStyle(CustomTextFieldStyle(text: $myDataStore.placeholder, hasErrors: myDataStore.placeholder.isEmpty)) Then create a UITest that accesses it. let multilineTextField = app.textViews["placeholder"] // note that multiline textFields can only be accessed as textVIEWS, not textFIELDS. They simply do not appear under po.textFields let exists = multilineTextField.waitForExistence(timeout: 3) XCTAssertTrue(exists, "The field did not appear in time.") multilineTextField.tap() // everything is fine up to here //BUG: multiline textfields will not tap into keyboard on larger device types like the iPhone 15, but they will on SEs. multilineTextField.typeText("A Test") // fails on anything other than an SE, "Neither element nor any descendant has keyboard focus" What is happening here?

As I trying to check "Publishing changes from within view updates is not allowed, this will cause undefined behavior." within the app in Xcode 15.4 , but unable to see that in the specific file but is getting logged in the Xcode , even I tried adding debugger for "All runtime issues" , its not working. Console like Opposed to this I am expecting this to be visible in the file as Anyone can pls help me in there!! Thanks!!

Hey, So I obviously downloaded the dev beta the second I could, and I didn’t notice any bugs. Except after the first reboot, the new Screen Time settings UI is replaced by the old one (see video below). This also has an effect on Remote Screen Time Management somehow, making any change (Downtime, App limit, etc) from the guardian’s device over the internet (as in not directly on the managed phone) not take effect at all. Rebooting does nothing, connecting to wifi does nothing, everything. I reported this to the Feedback Assistant so hopefully they catch wind of this soon. Anyone else experiencing this bug or does anyone have a workaround? Reply if so. Thanks, Mr. Sharky

CrashDoctor Diagnosis: Application threw exception NSInvalidArgumentException: -[_UIRemoteInputViewController _alignsToContentViewController]: unrecognized selector sent to instance 0x122917200 Thread 0 Crashed: 0 CoreFoundation 0x00000001aa1c9e48 __exceptionPreprocess + [ : 164] 1 libobjc.A.dylib 0x00000001a34938d8 objc_exception_throw + [ : 60] 2 CoreFoundation 0x00000001aa33e82c +[NSObject(NSObject) copyDescription] 3 UIKitCore 0x00000001ad0e9d18 -[UIResponder doesNotRecognizeSelector:] + [ : 260] 4 CoreFoundation 0x00000001aa1dff60 forwarding + [ : 1592] 5 CoreFoundation 0x00000001aa248330 forwarding_prep_0 + [ : 96] 6 UIKitCore 0x00000001ac6010f0 -[UIInputWindowControllerHostingItem _aligningInsetsForChildInputViewController:includeSceneBounds:] + [ : 60] 7 UIKitCore 0x00000001ac687e7c -[UIInputWindowControllerHostingItem updateViewConstraints] + [ : 4648] 8 UIKitCore 0x00000001ac686bec -[UIInputWindowControllerHosting updateViewConstraints] + [ : 184] 9 UIKitCore 0x00000001ac706c80 -[UIInputWindowController updateViewConstraints] + [ : 84] 10 UIKitCore 0x00000001ac8c8740 -[UIInputWindowController updateForKeyplaneChangeWithContext:] + [ : 264] 11 UIKitCore 0x00000001ac901ee8 -[UIInputWindowControllerHostingItem updateForKeyplaneChangeWithContext:] + [ : 56] 12 UIKitCore 0x00000001ac59a528 -[_UIRemoteKeyboards performOnControllers:] + [ : 256] 13 UIKitCore 0x00000001ac9061d8 -[UIInputSetHostView _didChangeKeyplaneWithContext:] + [ : 148] 14 UIKitCore 0x00000001ace0ed50 __51-[UICompatibilityInputViewController setInputMode:]_block_invoke_4 + [ : 732] 15 UIKitCore 0x00000001ac8a51ec __146-[NSExtension(UIViewControllerAdditions) _instantiateViewControllerWithInputItems:asAccessory:traitCollection:listenerEndpoint:connectionHandler:]_block_invoke_3 + [ : 220] 16 libdispatch.dylib 0x00000001b17db4b4 _dispatch_call_block_and_release + [ : 32] 17 libdispatch.dylib 0x00000001b17dcfdc _dispatch_client_callout + [ : 20] 18 libdispatch.dylib 0x00000001b17eb7f4 _dispatch_main_queue_drain + [ : 928] 19 libdispatch.dylib 0x00000001b17eb444 _dispatch_main_queue_callback_4CF + [ : 44] 20 CoreFoundation 0x00000001aa25a6d8 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + [ : 16] 21 CoreFoundation 0x00000001aa23c03c __CFRunLoopRun + [ : 2036] 22 CoreFoundation 0x00000001aa240ec0 CFRunLoopRunSpecific + [ : 612] 23 GraphicsServices 0x00000001e4297368 GSEventRunModal + [ : 164] 24 UIKitCore 0x00000001ac73686c -[UIApplication _run] + [ : 888] 25 UIKitCore 0x00000001ac7364d0 UIApplicationMain + [ : 340] 26 KYE_iOS 0x0000000104c5b71c main + [main.m : 14] 27 (null) 0x00000001c8a62960 0x0 + 7661300064

I'm getting occasional crashes, which have not happened while running under a debugger and I haven't figured out how to reproduce. I wonder if anyone can help me glean more information from a crash report. Here's the main part. This particular report if from macOS 14.2 beta, but I've also seen it from 14.1.1. Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018 Exception Codes: 0x0000000000000001, 0x0000000000000018 VM Region Info: 0x18 is not in any region. Bytes before following region: 140723250839528 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> mapped file 7ffcaf60c000-7ffcd7f48000 [649.2M] r-x/r-x SM=COW ...t_id=b7394f27 Error Formulating Crash Report: PC register does not match crashing frame (0x0 vs 0x1022A3630) Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 <translation info unavailable> 0x1022a3630 ??? 1 libsystem_platform.dylib 0x7ff819d0b393 _sigtramp + 51 2 AppKit 0x7ff81d3549a6 -[NSControl _setWindow:] + 59 3 AppKit 0x7ff81d413c19 -[NSSegmentedControl _setWindow:] + 42 4 AppKit 0x7ff81defd3be __21-[NSView _setWindow:]_block_invoke.391 + 324 5 AppKit 0x7ff81d33a62c -[NSView _setWindow:] + 1886 6 AppKit 0x7ff81defd3be __21-[NSView _setWindow:]_block_invoke.391 + 324 7 AppKit 0x7ff81d33a62c -[NSView _setWindow:] + 1886 8 AppKit 0x7ff81d572d08 -[NSWindow dealloc] + 922 9 MyApp 0x1011b6b81 -[JWWindow dealloc] (in MyApp) (JWWindow.m:37) 10 Foundation 0x7ff81b3d179c _NSKVOPerformWithDeallocatingObservable + 151 11 Foundation 0x7ff81acc6d54 NSKVODeallocate + 150 12 libobjc.A.dylib 0x7ff8199189d7 AutoreleasePoolPage::releaseUntil(objc_object**) + 169 13 libobjc.A.dylib 0x7ff819915cf0 objc_autoreleasePoolPop + 235 14 CoreFoundation 0x7ff819d794a1 _CFAutoreleasePoolPop + 22 15 Foundation 0x7ff81ac869ea -[NSAutoreleasePool drain] + 133 16 AppKit 0x7ff81d315694 -[NSApplication run] + 653 17 AppKit 0x7ff81d2e9662 NSApplicationMain + 816 18 MyApp 0x100ef5034 start (in MyApp) + 52 I can see that it involves deallocating a window as part of draining an autorelease pool, but does the presence of _NSKVOPerformWithDeallocatingObservable mean that KVO is involved somehow? And does the note "PC register does not match crashing frame" tell me anything?

My application is currently crashing in production in iPhone devices running iOS 15.x. The app will work as normal while running developer mode, enterprise builds and Test Flight builds. Unfortunately, I am unable to reproduce this issue even app is downloaded from the app store. I observed crash is happening at main.m. Can someone help me to reproduce this issue? How to read this crash log file? Please find the crash log details attached. 2022-03-04_14-15-23.6227_+0900-a1899fd803a4ed683466702be71b9d224b4cd5bc.crash

Xcode13.4.1 is running properly, but after upgrading Xcode14, the debugging device reports an error: Library not loaded: / usr/lib/swift/libswiftCoreGraphics dylib, I according to the online solutions are tried, can't solve my problem, problem is ios10.3.3 equipment, unable to debug, also is unable to start the application success after packaging, Is this a problem with xcode14 itself?

Anyone found a fix?

I've been upgrading Xcode consistently for years and have never seen Metal shaders behave differently from one version to another until now. On macOS 14.5, Xcode 16 beta, suddenly several color outputs turn out completely black where there should be color. All validation is on and nothing seems to be wrong (and hasn't been since maybe Xcode version 11). I've attached two screens. The first is the normal color scheme, the second is in Xcode 16. The settings are the exact same. Normal: Buggy with black + transparent colors (so it seems like either colors are overflowing or are all 0s)? Before I file a bug report or code level request, may I have some thoughts on how to debug this? The only clue I have is that I'm using bindless to multiply color texture samples with color values from my vertex struct. But it still fails even if I use hard-coded values for the texture samples, meaning somehow the color values are not being sent to the shader correctly? This is the most stable part of my rendering pipeline, so I'm surprised if the issue is there. Thank you.

Hello, I am developing a smartcard CTK extension for macOS. I have trouble to smartcard logon the first time after a reboot or a logout (e.g. when there is the text "Your password is required to enable touch id"). Trouble = I'm not asked for the PIN. But time to time after a logout (from whatever account), I can login with the smartcard. After a lockscreen I can always login with the smartcard. Is there an easy way to debug the logon process ? Regards, ++dom

I use to testing iOS app directly on my M1 Mac mini, without needing to plug in an iPhone. After updated to XCode 15.4, this option is gone.