Search results for

LLDB crash

29,555 results found

Post

Replies

Boosts

Views

Activity

WKWebView LoadRequest crash on ios 26
Since the ios 26 beta our app is crashing when calling LoadRequest() on the wkwebview class. The app crashes out completely when it occurs even in the debugger, I was able to get a stack trace from our Sentry crash handler. See below It seems that calling LoadRequest from the mainthread fixes the issue but I don't understand why, theres no documentation to suggest this must be done. Any ideas? Below is the stack trace I got from Sentry: WebKit +0x0054e00 WebKit::allDataStores WebKit +0x0bf34f4 WebKit::NetworkProcessProxy::preconnectTo WebKit +0x0acef64 WebKit::WebPageProxy::preconnectTo WebKit +0x0b0d92c ***::Detail::CallableWrapper::call WebKit +0x0ab6cf8 WebKit::WebPageProxy::maybeInitializeSandboxExtensionHandle WebKit +0x0ab84dc WebKit::WebPageProxy::loadRequestWithNavigationShared WebKit +0x0ab7adc WebKit::WebPageProxy::loadRequest WebKit +0x05d0704 -[WKWebView loadRequest:] Grid3iOS +0x5240944 xamarin_dyn_objc_msgSendSuper In App Grid3iOS +0x187dec4 wrapper_managed_to_native_O
1
0
59
4w
Reply to SwiftData Fatal error: Editors must register their identifiers before invoking operations on this store
Do you have a full symbolicated crash report to share? You can include crash reports directly in your post using the forums attachment feature. For any random crash related to SwiftData / Core Data, I'd suggest that you add com.apple.CoreData.ConcurrencyDebug 1 as a launch argument of the app to check if there is any violation, as discussed here. Also, I guess ConsumptionSession is Sendable? Otherwise, Xcode will give you an error if you compile with Swift 6. If you haven't used Swift 6, I'd suggest that you give it a try to see if that unveils any race condition. Best, —— Ziqiao Chen  Worldwide Developer Relations.
4w
Native Crash - Unknown Function (/usr/lib/system/libsystem_kernel.dylib) Unknown Function (/usr/lib/system/libsystem_kernel.dylib)
Hi, I encountered the following error while trying to launch a video game developed with Unity and running on an iPhone 12 and iPhone 16 Pro. Native StackTrace: Thread 2 (crashed) 0 libsystem_kernel.dylib 0x00000001d40102ec 1 libsystem_c.dylib 0x000000019330fba0 2 UnityFramework 0x000000010e7bc744 3 UnityFramework 0x000000010dc1c22c 4 UnityFramework 0x000000010cc26da4 5 CoreFoundation 0x000000018b4af984 6 libobjc.A.dylib 0x0000000183277140 7 libc++abi.dylib 0x00000001e7d20068 8 libc++abi.dylib 0x00000001e7d2000c 9 libdispatch.dylib 0x0000000193256de8 10 libdispatch.dylib 0x000000019325e400 11 libdispatch.dylib 0x000000019325ef30 12 libdispatch.dylib 0x0000000193269cb4 13 libdispatch.dylib 0x0000000193269528 14 libsystem_pthread.dylib 0x00000001e7e00934 15 libsystem_pthread.dylib 0x00000001e7dfd0cc
5
0
95
4w
Reply to iOS26 wkWebview Crash Application threw exception CALayerInvalidGeometry: CALayer position contains NaN:
I had the same crash with same crashlog. In my case I used WKWebView to display PDF document. Crash used to occur when you long press to call actions menu anywhere in the area without text. If you long press on text, actions menu was displayed without crash. It was on iOS 26 beta 5, but now on iOS 26 beta 7 I can't reproduce crash in such scenario. Looks like it was fixed, but can't say for sure, since I didn't find mentions of such problem in release notes.
Topic: Safari & Web SubTopic: General
4w
Reply to iOS 18 CoreFoundation crash in __CFRunLoopServiceMachPort (EXC_BREAKPOINT SIGTRAP)
You’re using a third-party crash reporter and it’s undermining your ability to debug this issue. This is not uncommon. I discuss this in way too much detail in Implementing Your Own Crash Reporter. My advice is that you remove your third-party crash reporter and then wait for new Apple crash reports to arrive. To illustrate the sorts of problems I’m talking about here, let me pull apart that second crash report, starting with this: Exception Type: EXC_CRASH (SIGSEGV) Exception Codes: 0x0000000000000000, 0x0000000000000000 Triggered by Thread: 0 This shows that your process crashed due to a memory access exception. That it, it was running some code that accessed an invalid memory location. Let’s look at the backtrace of the crashing thread: Thread 0 name: Thread 0 Crashed: 0 libsystem_kernel.dylib … mach_msg2_trap + 8 (:-1) 1 libsystem_kernel.dylib … mach_msg2_internal + 76 (mach_msg.c:201) 2 libsystem_kernel.dylib … mach_msg_overwrite + 4
Topic: App & System Services SubTopic: General Tags:
4w
SwiftData Fatal error: Editors must register their identifiers before invoking operations on this store
I have a UIKit app where I've adopted SwiftData and I'm struggling with a crash coming in from some of my users. I'm not able to reproduce it myself and as it only happens to a small fraction of my user base, it seems like a race condition of some sort. This is the assertion message: SwiftData/DefaultStore.swift:453: Fatal error: API Contract Violation: Editors must register their identifiers before invoking operations on this store SwiftData.DefaultStore: 00CF060A-291A-4E79-BEC3-E6A6B20F345E did not. (ID is unique per crash) This is the ModelActor that crashes: @available(iOS 17, *) @ModelActor actor ConsumptionDatabaseStorage: ConsumptionSessionStorage { struct Error: LocalizedError { var errorDescription: String? } private let sortDescriptor = [SortDescriptor(SDConsumptionSession.startTimeUtc, order: .reverse)] static func createStorage(userId: String) throws -> ConsumptionDatabaseStorage { guard let appGroupContainer = FileManager.default.containerURL(forSecurityApplicationGr
5
0
168
4w
Reply to Invalid Code Signing Entitlements
I have the same problem. Dis you solve that? I do not have a crash on payment, because I set IgnoreInvalidProducts with true value. But with this case i can not receive my subscriptions… I receive invalid products array with my subscription ID… I can offer you to try this: https://github.com/9khub/MAUI.StoreKit2
Topic: Code Signing SubTopic: Entitlements Tags:
Aug ’25
SwiftData crash when switching between Window and ImmersiveSpace in visionOS
Environment visionOS 26 Xcode 26 Issue I am experiencing crash when trying to access a [String] from a @Model data, after dismissing an immersiveSpace and opening a WindowGroup. This crash only occurs when trying to access the [String] property of my Model. It works fine with other properties. Thread 1: Fatal error: This backing data was detached from a context without resolving attribute faults: PersistentIdentifier(...) Steps to Reproduce Open WindowGroup Dismiss window, open ImmersiveSpace Dismiss ImmersiveSpace, reopen WindowGroup Any guidance would be appreciated! @main struct MyApp: App { var body: some Scene { WindowGroup(id: main) { ContentView() } .modelContainer(for: [Item.self]) ImmersiveSpace(id: immersive) { ImmersiveView() } } } // In SwiftData model @Model class Item { var title: String = // Accessing this property works fine var tags: [String] = [] @storageRestrictions(accesses: _$backingData, initializes: _tags) init(initialValue) { _$backingData.setValue(forKey: . tags, to
3
0
120
Aug ’25
Reply to ELEMENT_TYPE_OF_SET_VIOLATES_HASHABLE_REQUIREMENTS
Thanks for the crash report. That crash report shows two threads running inside HomeViewModel.hanldeAnnouncementCard(…), namely frame 5 on thread 22 and frame 13 on thread 24. Is there any chance they’re operating on the same instance of that HomeViewModel type? If so, that’s problematic. hanldeAnnouncementCard(…) has no locking, so having two threads running in the same instance is a data race. And a data race could easily cause you to hit that assert within Set.insert(…). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Programming Languages SubTopic: Swift Tags:
Aug ’25
Reply to iOS 18 CoreFoundation crash in __CFRunLoopServiceMachPort (EXC_BREAKPOINT SIGTRAP)
[quote='797558021, roadc, /thread/797558, /profile/roadc'] Crash Stacks From APM [/quote] What is “APM” in this context? To help you out here I need to see a crash report. Please post one, using the instructions in Posting a Crash Report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
Aug ’25
[iOS 26][SDK 26] Application never received providerDidBegin(_:) delegate
Observed few times that providerDidBegin(_:) delegate never called for the complete app session after app init(as part of this CXProvider registered) which was built with SDK 26 and running on iOS 26. This issue observed multiple times with our testing. Since there is no providerDidBegin:, client is marking CallKit as not ready and never report any calls for VoIP APNS and ended up in app crash due to [PKPushRegistry _terminateAppIfThereAreUnhandledVoIPPushes] Please refer for sysdiagnose logs : FB19778306
7
0
115
Aug ’25