Search results for

LLDB crash

29,540 results found

Post

Replies

Boosts

Views

Activity

Inquiry about Compatibility Issues in iOS 26​
Dear Apple Team, We are reaching out regarding several compatibility issues our app users have encountered after upgrading to iOS 26. These issues not only affect our application but also seem to impact the system's native settings, which has raised concerns about the universality of these problems. Problem Description Bluetooth Functionality: When users attempt to use the Bluetooth feature within our app after upgrading to iOS 26, the app freezes completely. What's more, when accessing the Bluetooth section in the system Settings app, it also freezes and ultimately crashes. Location Service: The location service on the device becomes inoperable after the iOS 26 upgrade. However, both the Bluetooth and location service issues are resolved after the user restarts the device. 2. Questions Universality: We are eager to know if these issues are exclusive to our app or are a more widespread problem among other applications on iOS 26. Are these known compatibility glitches in iOS 26? Avoidance: Is there an
0
0
7
1h
iOS 26 SwiftData crash does not happen in iOS 16
I have a simple app that makes an HTTPS call to gather some JSON which I then parse and add to my SwiftData database. The app then uses a simple @Query in a view to get the data into a list. on iOS 16 this works fine. No problems. But the same code on iOS 26 (targeting iOS 18.5) crashes after about 15 seconds of idle time after the list is populated. The error message is: Could not cast value of type '__NSCFNumber' (0x1f31ee568) to 'NSString' (0x1f31ec718). and occurs when trying to access ANY property of the list. I have a stripped down version of the app that shows the crash available. To replicate the issue: open the project in Xcode 26 target any iOS 26 device or simulator compile and run the project. after the list is displayed, wait about 15 seconds and the app crashes. It is also of note that if you try to run the app again, it will crash immediately, unless you delete the app from the device. Any help on this would be appreciated. Feedback number FB20295815 includes
1
0
38
7h
Reply to NSInvalidArgumentException Crash During Keyboard Language Switch on iOS 26
We have similar crash reports in our app on iOS 26. For us the crash seems to occur while the app is running the background. Last Exception Backtrace: 0 CoreFoundation 0x19a05e8c8 __exceptionPreprocess + 164 (NSException.m:249) 1 libobjc.A.dylib 0x196fd57c4 objc_exception_throw + 88 (objc-exception.mm:356) 2 CoreFoundation 0x19a070e88 -[__NSArrayM objectAtIndex:] + 592 (NSArrayM.m:142) 3 UIKitCore 0x1a0369758 -[_UIFlowLayoutInfo setSizes:forItemsAtIndexPaths:] + 316 (UIFlowLayoutSupport.m:2030) 4 UIKitCore 0x1a0355768 -[UICollectionViewFlowLayout _didPerformUpdateVisibleCellsPassWithLayoutOffset:] + 156 (UICollectionViewFlowLayout.m:2112) 5 UIKitCore 0x1a03136f0 -[UICollectionView _updateVisibleCellsNow:] + 3452 (UICollectionView.m:5683) 6 UIKitCore 0x19fa64604 -[UICollectionView layoutSubviews] + 280 (UICollectionView.m:6895) 7 UIKitCore 0x19f8aa078 UIView._layoutSubviewsWithObservationTracking() + 828 (_UIObservationTracking.swift:383) 8 UIKitCore 0x19f8aab38 @objc UIView._layoutSubviewsWi
Topic: UI Frameworks SubTopic: UIKit Tags:
12h
Reply to Using MetricKit for Hangs on macOS
I have exactly the same problem, and would appreciate some guidance on whether hang diagnostics on macOS actually work. The same as the original poster above, the Simulate MetricKit Payload debug option works fine, and a crash is delivered immediately on restarting the app. No sign of any real hang reports though, even after deliberately causing hangs in the app. It’s my understanding that they should be delivered immediately, but even after waiting several days there’s still nothing. I’ve tried debug, release, and TestFlight builds. Any guidance as to what I could possibly be missing would be great! Thank you.
Topic: App & System Services SubTopic: Core OS Tags:
14h
[Mac OS 26.0.0] [Crash]
Hello,Our app has caught an issue with gesture recognizers. This problem only occurs on Mac OS 26.0. From the stack trace, it seems that this is not a problem on the app side, but an exception reported by AppKit. I have provided the stack trace, please help check it. stack info: NSInternalInconsistencyException: AppKit doesn't support comparing gesture recognizers across windows AppKit doesn't support comparing gesture recognizers across windows NSInternalInconsistencyException __exceptionPreprocess exception info: OS Version: macOS 26.0.0 Exception Type: NSInternalInconsistencyException: AppKit doesn't support comparing gesture recognizers across windows Crash Thread ID: 0 Application Specific Information: AppKit doesn't support comparing gesture recognizers across windows NSInternalInconsistencyException __exceptionPreprocess expanded stack: Crashed Thread:0 stack.package stack.filename stack.function stack.lineno stack.in_app CoreFoundation None __exceptionPreprocess None 0 libobjc.A.dyli
Topic: UI Frameworks SubTopic: AppKit
0
0
14
21h
App Crashing iOS26
I have four apps currently deployed on the App Store. One of these apps crashes on launch when running on iOS 26, but functions as expected on iOS 18 and earlier versions. I am seeking to understand what changes in iOS 26 might be causing this issue. When running the app in debug mode on devices with iOS 26 using Xcode 16.1, the app crashes. The crash log references libobjc-trampolines.dylib, suggesting a potential issue with the Objective-C runtime. Has anyone else encountered a similar issue? AGX: AGX: agxa_device_template.hpp:1467:setupCompiler: *** FATAL: driver shader binary file not found in (null) for extension g15p!!! D [yHZ]: added warning: [MEDIUM]: SW04: A debugger is attached to the App. D [ProbeCallbacks]: [IXGUARD] debugger detected objc[1461]: couldn't dlopen libobjc-trampolines.dylib: dlopen(/usr/lib/libobjc-trampolines.dylib, 0x0106): tried: '/usr/lib/system/introspection/libobjc-trampolines.dylib' (no such file, not in dyld cache), '/usr/lib/libobjc-trampolines.dyl
0
0
16
21h
App Crashing iOS26
I have four apps currently deployed on the App Store. One of these apps crashes on launch when running on iOS 26, but functions as expected on iOS 18 and earlier versions. I am seeking to understand what changes in iOS 26 might be causing this issue. When running the app in debug mode on devices with iOS 26 using Xcode 16.1, the app crashes. The crash log references libobjc-trampolines.dylib, suggesting a potential issue with the Objective-C runtime. Has anyone else encountered a similar issue? AGX: AGX: agxa_device_template.hpp:1467:setupCompiler: *** FATAL: driver shader binary file not found in (null) for extension g15p!!! D [yHZ]: added warning: [MEDIUM]: SW04: A debugger is attached to the App. D [ProbeCallbacks]: [IXGUARD] debugger detected objc[1461]: couldn't dlopen libobjc-trampolines.dylib: dlopen(/usr/lib/libobjc-trampolines.dylib, 0x0106): tried: '/usr/lib/system/introspection/libobjc-trampolines.dylib' (no such file, not in dyld cache), '/usr/lib/libobjc-trampolines.dyl
0
0
9
23h
Reply to Safari 26 close and Refresh buttons not working in Compact tab layout
Fixed in Safari 26.0.1 (20622.1.22.118.4) That should be a lesson for Apple not to assign interns and vibe coders to work on Security critical projects. I also had a crash before this update and I hope Apple looked into it, as it might be exploitable. Memory corruption and KERN_INVALID_ADDRESS are never a good thing. Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000000d8 Exception Codes: 0x0000000000000001, 0x00000000000000d8 Safari 26.0 (20622.1.22.118.2) crash
Topic: Safari & Web SubTopic: General
1d
Reply to Using Glass in SwiftUI Crashes with Missing Weak Symbol
Hi! Can you please make sure that you're on the same version of Xcode as Mac or iOS? Meaning, say you're running beta 5 of Xcode, make sure you're also on beta 5 of iOS/macOS. We've fully released all of the OS26 releases, so if you can fully update both, that should work as well. Please let me know if you're still getting the crash. If so, can you file a feedback report at https://feedbackassistant.apple.com and respond with the FB number? Make sure to add a sysdiagnose of the device.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
1d
Reply to iOS Build Memory Access Issues Causing Crashes
Quinn asked me if I could take a look at this, and I have to say this is going to be a tricky one to track down. Let me start with the basics of what's going on. Pulling from your first crash log, here are the crucial details: Exception Type: EXC_BAD_ACCESS (SIGKILL) Exception Subtype: KERN_PROTECTION_FAILURE at 0x0000000000000000 Exception Codes: 0x0000000000000002, 0x0000000000000000 ... Termination Reason: CODESIGNING 2 Invalid Page ... Thread 4 name: Dispatch queue: assetsQueue Thread 4 Crashed: 0 ??? 0x0 ??? 1 Video Star 0x1012b34b0 __28-[ClipMixerView asyncRender]_block_invoke + 512 2 ...g_rt.asan_ios_dynamic.dylib 0x10559adf4 __wrap_dispatch_async_block_invoke + 196 3 libdispatch.dylib 0x19aacaaac _dispatch_call_block_and_release + 32 4 libdispatch.dylib 0x19aae4584 _dispatch_client_callout + 16 5 libdispatch.dylib 0x19aad32d0 _dispatch_lane_serial_drain + 740 6 libdispatch.dylib 0x19aad3dac _dispatch_lane_invoke + 388 7 libdispatch.dylib 0x19aade1dc _dispatch_root_queue_drain_deferre
1d
Reply to “Wi-Fi Aware Sample” on Phone quit unexpectedly.
Thank you for your post. As per the crash file recommendations, please file a bug against the sample. Include the crash file in the report and provide a link to the sample you used. Additionally, please provide the versions of the sample and the build numbers. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Thanks again for your help on this one. Albert Pascual
  Worldwide Developer Relations.
1d
WindowServer crash when moving window near left edge of external display
Steps to Reproduce: Connect a MacBook Pro (lid closed) to a large external monitor. Run the SDL3 testwm test application. git clone https://github.com/libsdl-org/SDL.git cmake -S . -B build -DBUILD_SHARED_LIBS=OFF -DSDL_TESTS=ON cmake --build build The testwm binary will be located in the build/test directory. Move the application window around the left edge of the external display. Observed Result: WindowServer crashes. System Configuration: MacBook Pro M3 Max, macOS Sequoia 15.6.1 LG GX9, 5120x2160 resolution, running at 165 Hz refresh rate Lid closed, single external display Panic Log: panic(cpu 7 caller 0xfffffe0027f61d5c): mismatched swapID's 6386399 vs 6386400n @UnifiedPipeline.cpp:14570 Debugger message: panic Memory ID: 0xff OS release type: User OS version: 24G90 Kernel version: Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:55 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6031 Fileset Kernelcache UUID: 8AA69CD2038CD2BAE2ED364428F4DBEA Kernel UUID: 75A21406-D046-3232-AA3F-085335D5C848 Boo
1
0
57
1d
Reply to iOS Build Memory Access Issues Causing Crashes
Thank you for your response! Attached are some crash reports that represent attempts to merge in two separate branches that take our relatively stable (not crashing in the ways described above) main branch and introduce (or reintroduce) the observed crashes. Also, ASan is enabled for two out of four of the reports (one per branch) and disabled for the others. Did you try doing this incrementally? If you have a bunch of them, it’d be interesting to see which combinations do and don’t reproduce the problem. I will try this, but one of the primary issues with tracking these crashes down has been not knowing if/when they are truly eliminated as they tend to come and go after minimal code changes. It seems that almost any change to the code, or which files/libraries/frameworks are included in the build will change how the crashes manifest, or in some cases do not manifest. This is a bit of a long shot, but are there any things in particular (in crash reports or
1d