Search results for

LLDB crash

30,301 results found

Post

Replies

Boosts

Views

Activity

Reply to Popover in Toolbar Causes Crash in Catalyst App on macOS 26
Here is my work around for UIKit extension UIViewController { @objc func configureAsPopoverWith(sender: Any?) { self.modalPresentationStyle = .popover var enableZoom: Bool = true var source: Any? = sender #if targetEnvironment(macCatalyst) // PopOver with Zoom crashes for macOS 26 if #available(iOS 26.0, *), let view = (sender as? UIBarButtonItem)?.value(forKey: view) as? UIView { source = view } enableZoom = false #endif if let sourceView = source as? UIView { self.popoverPresentationController?.sourceView = sourceView self.popoverPresentationController?.sourceRect = sourceView.bounds if #available(iOS 18.0, *), enableZoom { self.preferredTransition = .zoom { _ in sourceView } } } else if let sourceItem = source as? UIBarButtonItem { self.popoverPresentationController?.barButtonItem = sourceItem } } }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Jan ’26
startosinstall “Helper tool crashed…” when upgrading macOS with MDM OS update restrictions — request Apple-recommended update method for MDM-managed Macs
We are upgrading macOS (minor versions and potentially major versions) using a scripted approach: Install the InstallAssistant package via installer Trigger OS install via startosinstall On MDM-managed assets, OS update policies appear to prohibit or interfere with the update flow. The update often fails with startosinstall reporting “Helper tool crashed…” during the “Preparing” phase. Steps to Reproduce On an MDM-enrolled Mac with OS update restriction/deferral policies applied, run: sudo /usr/sbin/installer -pkg /Path/To/InstallAssistant.pkg -target / && echo 'MACOS_PASSWORD' | /Applications/Install macOS Sonoma.app/Contents/Resources/startosinstall --agreetolicense --forcequitapps --stdinpass --user MACOS_USER Actual Result Package installation reports success, but startosinstall fails during preparation with: Standard Output installer: Package name is macOS15.7_SoftwareUpdate installer: Upgrading at base path / installer: The upgrade was successful. By using the agreetolicense option, you
Topic: Business & Education SubTopic: Device Management Tags:
0
0
1.4k
Jan ’26
Reply to Popover in Toolbar Causes Crash in Catalyst App on macOS 26
I'm experiencing the exact same crash in UIKit. With UIBarButtonItems and Popovers. On Mac Catalyst app build with Xcode 26.2 (17C52) on Tahoe 26.2. Same will happen with UIView as a source when presenting the a UIViewController if a zoom transition is set vc.preferredTransition = .zoom { _ in sendingView } Setting the info.plist UIDesignRequiresCompatibility to YES, prevents the default zoom transition and shows the popup with arrows.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Jan ’26
Reply to evaluatedPolicyDomainState
[quote='873184022, iceboy, /thread/811084?answerId=873184022#873184022, /profile/iceboy'] The user previously … [/quote] Well, that’s quite an edge case. Having said that, just because it’s an edge case doesn’t mean it shouldn’t work |-: [quote='873189022, iceboy, /thread/811084?answerId=873189022#873189022, /profile/iceboy'] And what is the basis for generating this value? [/quote] I can’t go into those details. I don’t know off the top of my head but, even if I did, I’m reluctant to discuss implementation details like this unless there’s some specific benefit to it. And I’m not seeing that here. Rather, this is clearly something that you should report as a bug. IMPORTANT For this bug to get any sort of traction, you’ll need a sysdiagnose log. I’m presuming you can’t reproduce that yourself, so you’ll need to ask your user to either send you the sysdiagnose log or file their own bug, attach the log there, and send you the bug number. Ideally they’d trigger this sysdiagnose log immediately after the
Topic: Privacy & Security SubTopic: General Tags:
Jan ’26
Reply to Feedback generator was deactivated by its client more times than it was activated
crash infomation： *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Feedback generator was deactivated by its client more times than it was activated: <_UIZoomEdgeFeedbackGenerator: 0x33527cdc0>' *** First throw call stack。 stack（main thread）： 1 CoreFoundation ___exceptionPreprocess (in CoreFoundation) 2 libobjc.A.dylib _objc_exception_throw (in libobjc.A.dylib) 3 CoreFoundation +[NSException raise:format:] (in CoreFoundation) 4 UIKitCore -[UIFeedbackGenerator _deactivateWithStyle:] (in UIKitCore) 5 Foundation ___NSFireDelayedPerform (in Foundation) 6 CoreFoundation _CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION (in CoreFoundation) 7 CoreFoundation ___CFRunLoopDoTimer (in CoreFoundation) 8 CoreFoundation ___CFRunLoopDoTimers (in CoreFoundation) 9 CoreFoundation ___CFRunLoopRun (in CoreFoundation) 10 CoreFoundation __CFRunLoopRunSpecificWithOptions (in CoreFoundation) 11 GraphicsServices _GSEventRunModal (in GraphicsServices) 12 UIKitCore -[UIAppl
Topic: UI Frameworks SubTopic: UIKit
Jan ’26
Reply to CarPlay navigation issue, maximum depth
I got an answer directly from Apple: You've hit upon one of the most common and often confusing limitations in CarPlay development, the template stack depth limit. For most CarPlay apps, the navigation stack depth is limited to two templates. This means you can have a root template, and then push one more template on top of it. Attempting to push a third template will result in the maximum level exception you're seeing. Apple's first-party apps (like Music, Maps, Phone) often have special entitlements and UI paradigms that are not available to third-party developers, my apologies. Third-party apps that qualify for specific categories (e.g., audio, navigation, EV charging, parking, food ordering) can use CPTabBarTemplate, but even then, each tab's stack is still limited to two. Yes, the crash reports and the maximum level exception are clear indicators of exceeding the template stack depth. This is not a bug in your code's logic, but rather a design constraint imposed by CarPlay for safety reasons. Si
Topic: Design SubTopic: General Tags:
Jan ’26
Reply to System Panic with IOUserSCSIParallelInterfaceController during Dispatch Queue Configuration
SO, I actually think this is what you need to take a much closer look at: Thread 4 (Crashed Thread): Has already received the hardware interrupt for the first command (TEST UNIT READY) and is attempting to invoke the completion API. More specifically, why EXACTLY did that hardware interrupt occur? The assumption you seem to be making is that the system called UserProcessBundledParallelTasks and then wasn't ready to process the completion when your interrupt fired. However, I think what actually happened is slightly different and that UserProcessBundledParallelTasks wasn't actually called at all, and that the interrupt handler fired for other reasons. That leads to my comment here: This also explains why our synchronous test succeeded: within the scope of UserProcessBundledParallelTasks, the system ensures that the target is already fully established and the action pointer is valid. Strictly speaking, that's true but not in the way you're thinking. What's actually going on here is that the system firs
Topic: App & System Services SubTopic: Drivers Tags:
Jan ’26
Reply to Crash log
Thanks for the post, hard to see the crash log for developers here to try to give you ideas. Kindly submit a comprehensive crash report, adhering to the guidelines outlined in Posting a Crash Report. https://developer.apple.com/forums/thread/688669 Thanks Albert Pascual
  Worldwide Developer Relations.
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Jan ’26
Reply to Hardware Memory Tag (MIE) enforcement outside of debugger
So, I have three bits of good news: My boss got me an iPhone 17 so that I can test this properly. Thanks boss! It was a public holiday in the US yesterday, which allowed me to catch up a bit, so I had some time to play with MIE today. I figured out the sequence to get soft mode crash reports (-: Here’s what I did: Using Xcode 26.2 on macOS 26.2 [1], I created a new project from the iOS > App template, choosing Objective-C as the language. In the view controller, I added this code: - (IBAction)testAction:(id)sender { char * buf = malloc(32); buf[16] += 1; free(buf); buf[16] += 1; } I added a Test button and wired it up to that action. In Signing & Capabilities, I added the Enhanced Security capability and checked all the boxes (-: In the scheme editor, I enabled Diagnostics > Hardware Memory Tagging. I selected an iPhone 17 running iOS 26.2 as my run destination and chose Product > Run. On the device, I tapped the Test button. It trapped, with Xcode highlighting the second increment. So f
Topic: Privacy & Security SubTopic: General Tags:
Jan ’26
Crash log
base : 6481543168, size : 5134811136, uuid : 7bc5af5f-1e86-3b36-9036-16025c72cb70 }, vmSummary : ReadOnly portion of Libraries: Total=1.0G resident=0K(0%) swapped_out_or_unallocated=1.0G(100%)nWritable regions: Total=28.8M written=369K(1%) resident=369K(1%) swapped_out=0K(0%) unallocated=28.5M(99%)nn VIRTUAL REGION nREGION TYPE SIZE COUNT (non-coalesced) n=========== ======= ======= nActivity Tracing 256K 1 nAttributeGraph Data 1024K 1 nCoreAnimation 48K 3 nDispatch continuations 6144K 1 nFoundation 16K 1 nKernel Alloc Once 32K 1 nMALLOC 16.8M 10 nMALLOC guard page 3760K 4 nSTACK GUARD 64K 4 nStack 2640K 4 n__AUTH 3975K 362 n__AUTH_CONST 60.1M 643 n__CTF 824 1 n__DATA 28.6M 604 n__DATA_CONST 24.9M 650 n__DATA_DIRTY 4800K 581 n__FONT_DATA 2352 1 n__INFO_FILTER 8 1 n__LINKEDIT 188.3M 7 n__OBJC_RO 84.3M 1 n__OBJC_RW 3177K 1 n__TEXT 839.6M 666 n__TPRO_CONST 128K 2 nmapped file 32.7M 3 npage table in kernel 369K 1 nshared memory 80K 4 n=========== ======= ======= nTOTAL 1.3G 3558 n, legacyInfo : { threadTriggered
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
1
0
251
Jan ’26
App crashes on click NEXT to next View
I am developing an app in Swift Playground (No Xcode). All my Views respond to the navigation call when I click NEXT except one. When I click NEXT the app hangs then crashes. The error message does not identify the cause of the crash. I have research every possible lead with no success. I would like to get some ideas on how to resolve this issue.
Topic: Design SubTopic: General Tags:
0
0
211
Jan ’26
UITabGroup child tabs ignoring viewControllerProvider in Sidebar
Hi, I am implementing a sidebar navigation using UITabBarController with the new UITabGroup API on and above iPadOS 18. I’ve encountered an issue where selecting a child UITab within a group does not seem to trigger the child's own viewControllerProvider. Instead, the UITabBarController displays the ViewController associated with the parent UITabGroup. The Issue: In the snippet below, when I tap Item 2A or Item 2B in the iPad sidebar, the app displays the emptyVC (clear background) defined in the section2Group provider, rather than the teal or cyan ViewControllers defined in the individual child tabs. let item2A = UITab( title: Item 2A, image: UIImage(systemName: a.circle), identifier: tab.section2.item2a ) { _ in self.createViewController( title: Section 2 - Item 2A, color: .systemTeal, description: Part of Section 2A group ) } let item2B = UITab( title: Item 2B, image: UIImage(systemName: b.circle), identifier: tab.section2.item2b ) { _ in self.createViewController( title: Section 2 - Item 2B, color: .syste
Topic: UI Frameworks SubTopic: UIKit Tags:
1
0
104
Jan ’26
Reply to NSStagedMigrationManager Merging Steps
There was a few issues here. None of which are documented very well. And all crash with the same error message. (1) My orginal .xcdatamodel file didn't have a Core Data Model Identifier. Which lead to a crash with NSCustomMigrationStage, even though the versionChecksum are different. (2) The steps passed into NSStagedMigrationManager are not clear or documented. But it appears that if you pass the first version of the model into the steps, it crashes. (3) I'm using manual code generation for the model classes. So my goal was to switch the model names, then switch them back, so I didn't have to change anything. For some reason, stepping through the one migration step per app launch instead of all at once allowed for a successful migration. But running all steps threw an error. Turns out I could just rename the model classes with the _v2 suffix, and the only thing I needed to update was the string in the fetch request. Overall, to resolve this I added a model version identifier I dupl
Topic: App & System Services SubTopic: iCloud & Data Tags:
Jan ’26