Search results for

LLDB crash

29,559 results found

Post

Replies

Boosts

Views

Activity

Using Previews causes a system crash on Xcode 26 Beta 4 and MacOS 26 Beta 4
Hey, I've updated to both Xcode 26 Beta 4 and MacOS 26 Beta 4. Both run super stable so far. However, every time I use Xcode Previews for a few minutes, the entire system freezes for a few seconds and then crashes and reboots. I'm trying to generate a system diagnosis (which it offers me after the reboot), but it seems to be stuck generating. It's hard to say what exactly causes the crash, unfortunately. But it happened multiple times after starting to use Xcode Previews. Anyone else has that problem? I've also filed a feedback for this: FB19013059 Cheers Dennis
11
0
612
Jul ’25
New iPadOS 26 beta4 crash in `UISplitViewController`
Sample Project In iPadOS 26 beta4, when a UISplitViewController transitions to compact layout and proposes the secondary view controller, a crash occurs: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Layout requested for visible navigation bar, ; layer = > delegate=0x102826600, when the top item belongs to a different navigation bar. topItem = title='Detail' style=navigator rightBarButtonItems=0x600000011e10, navigation bar = ; layer = > delegate=0x102826000, possibly from a client attempt to nest wrapped navigation controllers.' When we show the primary view, there is no crash. Similarly, there is no crash on beta-3. To reproduce the crash in the demo project: Launch the project on an iPad. Try the Demo Tap List-Detail Pattern To trigger the crash, select any of the list items and switch the app to a compact layout. The crash occurs because the app will attempt to propose the secondary view controller. T
Topic: UI Frameworks SubTopic: UIKit
1
0
174
Jul ’25
Regression: CoreNFC crash happening through sole presence of a method
I sent this feedback some time ago and still haven't received an answer. Can someone poke someone internally please? Thank you! FB18815675 I have no idea what exactly is going on but after 5 days I found the culprit and I have a reproducible sample project. In the project is a package that does some basic NFC NDEF encoding. I put a commented out method in there and when you comment that in then the app starts crashing at runtime when scanning an NFC tag. Please check out the project and see yourself. Thanks https://github.com/NickAtGit/iOS26-CoreNFC-Crash
3
0
219
Jul ’25
Reply to Background App Refresh
I fear you’re getting distracted by the Operation side of this. Operation isn’t required by this API. Its presence in the docs is an artefact of history, in that those docs were written before Swift concurrency was a thing. If you were doing this today, you’d ignore Operation and just use Swift concurrency. Similarly, the docs are within the UIKit, but that’s also not required by this API, and if you were doing it today you’d use SwiftUI. So, here’s how I created an app that manages an app refresh task using Swift concurrency and SwiftUI: Using Xcode 16.4, I created a new project from the iOS > App template, choosing SwiftUI for my interface. I switched the Swift Language Version build setting to Swift 6. If you’re gonna do Swift concurrency, you might as well have the compiler enforce the rules! I created an AppModel type to hold the state of my app: import Foundation import Observation @Observable @MainActor final class AppModel { private(set) var lastUpdate: Date? = nil private var isUpdating: Bool = fa
Jul ’25
Reply to App Store code signing show "Beta Profile"
Sorry I didn’t respond sooner; I wasn’t notified of your reply )-: Thanks for the crash report. This suggests that you don’t have a code signing problems. Rather, the presence of the Last Exception Backtrace section indicates that your app is up and running and then threw a language exception. The backtrace on that exception is interesting: Last Exception Backtrace: 0 CoreFoundation … __exceptionPreprocess + 164 1 libobjc.A.dylib … objc_exception_throw + 88 2 munsblog … 0x1029c0000 + 33407840 3 munsblog … 0x1029c0000 + 35102404 4 UIKitCore … -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 320 Frame 4 indicates that UIKit is calling one of your app delegate methods. Frame 3 is your app delegate method implementation. It calls some other method in your code, frame 2, which throws a language exception. To make progress with this you’ll need to uncover the identity of your code in frames 3 and 2. For advice on how to do that, see Adding identifiable symbol names to a crash
Jul ’25
The new navigationLinkIndicatorVisibility modifier crashes on < iOS 26
This new modifier is supposedly backported to iOS 17, but on attempting to use it on the latest iOS 18.5, this happens: Symbol not found: _$s7SwiftUI17EnvironmentValuesV33_navigationIndicatorVisibilityABIAA0G0OvpMV This happens with any usage of the modifier. An availability check won't save you either. The cruelest part of this is that I only need the modifier on iOS 26, lmao. Am I just missing something?
Topic: UI Frameworks SubTopic: SwiftUI
9
0
205
Jul ’25
Gatekeeper rejects notarized app ("Unnotarized Developer ID") when using necessary entitlements
Hello everyone, I'm hoping to get some guidance on a frustrating codesigning issue. I have a macOS application that successfully completes the entire notarization and stapling process, but it is still rejected by Gatekeeper during the final verification step. The rejection only happens when I apply the entitlements that I believe are necessary for my app's functionality. The application is built with PyInstaller and has the following components: A main executable written in Python. A bundled Tcl/Tk instance for the GUI. Embedded Playwright components, which include the Node.js runtime and a full Chromium browser instance. These are located deep inside the .app bundle. The Problem The core of my application relies on Playwright to perform some automated tasks, and its bundled Chromium browser requires specific entitlements to function under the Hardened Runtime. Specifically, it needs com.apple.security.cs.allow-jit and com.apple.security.cs.allow-unsigned-executable-memory. My signing process is as follows: P
9
0
467
Jul ’25
Reply to Crash when deallocating NEAppProxyFlow
That’s a mighty interesting crash you have there. I have an idea as what might be happening here, but I’d like to confirm some things. Please post a full crash report, per the advice in Posting a Crash Report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Jul ’25
Crashes on iOS 18.x
Starting with iOS 18.3, we are getting infrequent crash reports somehow related to web sockets. Are there any new caveats we should be aware of or is it just a CFNetwork bug? Incident Identifier: 0D4343CE-3089-4514-841D-80CEC353B6B8 Distributor ID: com.apple.AppStore Hardware Model: iPhone16,2 AppStoreTools: 16C7015 AppVariant: 1:iPhone16,2:18 Code Type: ARM-64 (Native) Role: Non UI Parent Process: launchd [1] Date/Time: 2025-03-18 15:42:14.1732 -0400 Launch Time: 2025-03-15 20:38:20.7015 -0400 OS Version: iPhone OS 18.3.1 (22D72) Release Type: User Baseband Version: 2.40.05 Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 VM Region Info: 0 is not in any region. Bytes before following region: 4373233664 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 104aa4000-104aa8000 [ 16K] r-x/r-x SM=COW /var/containers/Bundle/Applicat
7
0
114
Jul ’25
Reply to Symbol not found: ___res_9_state
As my colleague Ed mentioned, the interface has a lot of ‘interesting’ backstory. My general advice is to avoid that API wherever possible. However, before we dig into alternatives I want to ask about this: [quote='793921021, Nick_Ni, /thread/793921, /profile/Nick_Ni'] When running my app with Xcode16.4, it crashed with the error: [/quote] I built a tiny test function that calls __res_9_state and called it from both a macOS program and an iOS app and both worked just fine. So where are you running your code? Specifically, what platform and what version of that platform? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Jul ’25
Reply to Change to SwiftData ModelContainer causing crashes
Thank you for your response. I had actually read that post in depth before posting here. What I would really like to know is, am I doing anything wrong with my VersionedSchema, ModelContainer or @Models please? I have been looking all around and it is hard to find the right answer for my specific case where I have transitioned to a Versioned Schema where I have suddenly placed all my @Models in, and have also changed my ModelContainer. I actually initially built this new container like so as I thought this was correct for migration plans: actor ModelContainerActor { @MainActor static func container() -> ModelContainer { let schema = Schema( versionedSchema: AllSwiftDataSchemaV3.self ) let configuration = ModelConfiguration() let container = try! ModelContainer( for: schema, migrationPlan: PlanBriefMigrationPlan.self, configurations: configuration ) return container } } Which I believe may have been causing the crashes. I haven't had any crashes in the last 24 hours since changing to this
Jul ’25