Environment • Device: iOS 26 Developer Beta 5 (23A5308g) • Xcode: 16.3 Short description The app crashes the moment the user tries to long-press to select text inside a WKWebView, double-tap an image with Text (magnifier appears) The exception is CALayer position contains NaN. frame = (nan,0;0,48) chorPoint=(inf, 0) and it is thrown in the UI process. Build & run any project that hosts a WKWebView. Inject the following CSS via script (this is what we do to suppress the native callout menu): WKWebView *webView = [[WKWebView alloc] initWithFrame:self.view.bounds configuration:[WKWebViewConfiguration new]]; NSString *js = @document.documentElement.style.webkitUserSelect='none'; document.documentElement.style.webkitTouchCallout='none';; [webView evaluateJavaScript:js completionHandler:nil]; [self.view addSubview:webView]; Incident Identifier: EE6FB046-5087-4F15-A72D-A74965347A30 CrashReporter Key: 29e8e58e02a07557adb4ce3f463d764f3ce8bbd5 Hardware Model: iPhone16,1 Process: wallet [642] Path: /private
Search results for
LLDB crash
29,558 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Environment • Device: any iPhone running iOS 26 Developer Beta 5 (23A5308g) • Xcode: 16.3 Short description The app crashes the moment the user tries to long-press to select text inside a WKWebView, double-tap an image with Text (magnifier appears) The exception is CALayer position contains NaN. frame = (nan,0;0,48) chorPoint=(inf, 0) and it is thrown in the UI process. Build & run any project that hosts a WKWebView. Inject the following CSS via script (this is what we do to suppress the native callout menu): WKWebView *webView = [[WKWebView alloc] initWithFrame:self.view.bounds configuration:[WKWebViewConfiguration new]]; NSString *js = @document.documentElement.style.webkitUserSelect='none'; document.documentElement.style.webkitTouchCallout='none';; [webView evaluateJavaScript:js completionHandler:nil]; [self.view addSubview:webView]; Incident Identifier: EE6FB046-5087-4F15-A72D-A74965347A30 CrashReporter Key: 29e8e58e02a07557adb4ce3f463d764f3ce8bbd5 Hardware Model: iPhone16,1 Process: wallet [
how to fix https:// i.ibb.co/SwZ76KzZ/Screenshot-2025-08-07-at-10-35-24-AM.png
Topic:
Developer Tools & Services
SubTopic:
Xcode
Whenever I try to initialize a LanguageModelSession (let session = LanguageModelSession()), my app crashes with EXC_BAD_ACCESS. SystemLanguageModel.default.availability returns available. I tried running the two sample projects I found that use Foundation Models, FoundationModelsTripPlanner and SwiftTranscriptionSampleApp, and they both also crash—immediately on launch. I commented out the Foundation Models logic from the SwiftTranscriptionSampleApp and ran it again, and it no longer crashed. I'm on macOS 26 Beta 4 on an M1 Pro device. I'm based in Austria (EU), if that matters.
When I open my project with Xcode 26 beta 5, it crashes within a few seconds. It’s completely unusable. See the crash stack trace below: crash
WKWebView has set the option to disable selection (document. documentElement. style. webkitUserSelect='none ';) and long press (document. documentElement. style. webkitTouchCallout='none';). If there is text on one of the images in WebView, simply tap the image twice and then long press the text. The program will crash with the following error message: 0 CoreFoundation 0x185e058c8 __exceptionPreprocess + 164 1 libobjc.A.dylib 0x182d797c4 objc_exception_throw + 88 2 CoreFoundation 0x185e908d4 -[NSException initWithCoder:] + 0 3 QuartzCore 0x18678a874 CA::Layer::set_position(CA::Vec2<double> const&, bool) + 160 4 QuartzCore 0x1869a7270 -[CALayer setPosition:] + 52 5 UIKitCore 0x18c4ac564 -[UIView _backing_setPosition:] + 176 6 UIKitCore 0x18cefdf0c -[UIView setCenter:] + 220 7 UIKitCore 0x18cd9f794 -[_UIEditMenuContentPresentation _displayPreparedMenu:titleView:reason:didDismissMenu:configuration:] + 936 8 UIKitCore 0x18cd9f3c0 __54-[_UIEditMenuContentPresentation _displayMenu:reason:]_block_
Our code is like this: @interface LLLineMoreView() @property (strong, nonatomic) IBOutlet UIView *topLineView; @end Exception Category: mach Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 Crashed Thread: 0 CrashDoctor Diagnosis: Attempted to dereference garbage pointer 0x8. Thread 0 Crashed: 0 CoreFoundation 0x000000018bb3ea7c _CFXNotificationRegistrarAddObserver + [ : 368] 1 CoreFoundation 0x000000018bb3ea0c _CFXNotificationRegistrarAddObserver + [ : 256] 2 CoreFoundation 0x000000018bb3e890 CFXNotificationRegistrarAdd + [ : 576] 3 CoreFoundation 0x000000018bb3e070 _CFXNotificationRegisterObserver + [ : 248] 4 UIKitCore 0x000000018e3a39ac UILabelCommonInit + [ : 188] 5 UIKitCore 0x000000018e8133cc -[UILabel initWithCoder:] + [ : 212] 6 UIFoundation 0x000000019747aaa4 UINibDecoderDecodeObjectForValue + [ : 684] 7 UIFoundation 0x000000019747ac30 UINibDecoderDecodeObjectForValue + [ : 1080] 8 UIFoundation 0x000000019747a6f8 -[UINibDecoder d
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
Here's a recap of the issue Summary of Current Setup So Far (for your documentation): Step Command Output / Result A gem install cocoapods -v 1.14.3 ✅ Installed successfully B which pod user/bob/.rbenv/shims/pod C pod --version 1.14.3 D gem install xcodeproj --pre ✅ Installed xcodeproj-1.27.0 CONCLUSION: This confirms: Xcode 16.3 writes .xcodeproj files with object version 90 The latest xcodeproj gem (1.27.0) only supports up to object version 77 Therefore, CocoaPods will crash every time with modern Xcode, no matter which version of cocoapods you use ✅ Clear Answer ❌ You cannot use CocoaPods right now unless: Xcodeproj is updated to support object version 90 → You’d have to wait for CocoaPods to release a compatible version Or you downgrade Xcode to something that supports .xcodeproj object version 77 → But this means downgrading to Xcode 15.x or lower, which won’t run on macOS 15.5 Sequoia → So you’re stuck.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
In my SceneDelegate via 'scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions)' I call the following code to assign a Storyboard: let storyboard = UIStoryboard(name: Main, bundle: nil) let initialVC = storyboard.instantiateInitialViewController() self.window?.rootViewController = initialVC The Initial VC is a UITabBarController. The app crashes when calling 'instantiateInitialViewController': *** Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: 'Could not instantiate class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ because no class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ was found; the class needs to be defined in source code or linked in from a library (ensure the class is part of the correct target)' terminating due to uncaught exception of type NSException CoreSimulator 1047 - Device: iPhone 16 Pro (06A3EAF6-6623-49FD-BEFE-BE88FDD1
Can anyone please point out what is wrong with this code and suggest a right method? I see a few different issues: (1) You don't need to do any extra work to get access to your buffer, as the IOBufferMemoryDescriptor is basically an IOMemoryDescriptor that makes it easy to read/write the memory. GetAddressRange actually returns a pointer inside your address space. (2) You'll be cutting this code out, but for future reference, you should have passed 0 instead of kIOMemoryMapReadOnly here. bufferDescriptor->CreateMapping(kIOMemoryMapReadOnly, 0, 0, 0, 0, &map); The default behavior here is read/write, which kIOMemoryMapReadOnly is then modifying. I'm actually not sure what the result of your call was, as I would have expected a read-only map to mean you'd crash at memcpy. You didn’t, so I'm not sure what the actual result was, but I suspect you sent NULL data out. (3) I'm not sure what your final goal here is, but you should not be creating and destroying the buffers returned by CreateIOBuffer.
Topic:
App & System Services
SubTopic:
Drivers
Tags:
Our engineering teams need to investigate this issue. We'd greatly appreciate it if you could open a bug report, include crash logs and sample code or models that reproduce the issue, and post the FB number here once you do. We also need packet logs if you can, and a diagnostic log from the iPad in question. Please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for iOS to install a logging profile on your device. Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose. And attach that to the Feedback report as well. Bug Reporting: How and Why? has tips on creating a successful bug report. Please @ mention me in your response with the Feedback number so I can route it to the appropriate teams without delay. Argun Tekant / DTS Engineer / Core Technologies
Topic:
App & System Services
SubTopic:
Core OS
Tags:
This typically means that the app claims the entitlements but those claims aren’t authorised by its provisioning profile. Make sure that: The app has an embedded profile. That profile is a Developer ID profile. That profile includes the certificate you used to sign the app. That profile’s entitlement allowlist includes all of the restricted entitlements the app claims. The number one cause of the problem is forgetting to embed a Developer ID profile. See the “replace the embedded provisioning profiles” step in Exporting a Developer ID Network Extension. You can find a lot more background to this in TN3125 Inside Code Signing: Provisioning Profiles. And I have more focused instructions in Resolving Code Signing Crashes on Launch. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
Networking
Tags:
Could be the same issue. I tried reporting this directly to Apple with a request for Technical Assistance because I hadn't seen any other reports of this behavior. I had developed a SwiftData app that used CloudKit and therefore required all model relationships to be treated as optional. I was sorting an object using a relationship's title field (which was clearly optional) and this worked fine in all simulator and Xcode downloads with no issues. I didn't run into it until I tried using TestFlight to get some beta feedback and the app immediately crashed and the feedback was sparse so I took several months to finally track down what was causing it. I would certainly like to see this fixed because it creates limitations that only surface very late ih the app dev process which is very frustrating. If it shouldn't ever work then it should also crash in the simulator and any Xcode downloads IMHO.
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
Are you using Core Image, by any chance? I'm hitting something very similar, developing for macOS and running under Xcode 16.2 on macOS 15.5. Doing a lot of video work using Core Image, and I get these crashes during a CIRenderTask pretty frequently (like within a few minutes of live rendering), usually within a call to CI::Context::recursive_render. We do get occasional crash reports from release builds, crashing on locking calls within Core Image, but none of those involve qosWaiterSignallerInvariantCheck, and we hit them much, much more often when running with Thread Performance Checker on.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I can't use Xcode without it crashing. Just writing a very simple iOS app with SwiftUI (using only forms and sections). Whenever my canvas updates to correspond to my changes it forces my Macbook to restart. Does anyone have a solution for this. I'll be honest it's becoming really frustrating. Thank you. Macbook M3 Pro 16GB ram, 500gb Space (400gb free space)