Search results for

LLDB crash

29,555 results found

Post

Replies

Boosts

Views

Activity

Reply to Crash in URLConnectionLoader::loadWithWhatToDo
[quote='841772022, edysudarto, /thread/786553?answerId=841772022#841772022, /profile/edysudarto'] but the crash reports I shared here and in the bug report are all coming from Xcode organizer crash reports. [/quote] Right. But the presence of a third-party crash reporter undermines the trustworthiness of Apple crash reports. I talk about this in Implementing Your Own Crash Reporter, and there was a really good (well, bad)-: example of this phenomenon in this recent thread. [quote='855264022, edysudarto, /thread/786553?answerId=855264022#855264022, /profile/edysudarto'] I cannot select [the .ips] as the file seems disabled from the upload menu [/quote] Sorry about that. This is a known bug. The workaround, as explained in Posting a Crash Report, is to change the extension to .txt and attach that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Networking Tags:
3w
Reply to The new navigationLinkIndicatorVisibility modifier crashes on < iOS 26
I'm doing the following hack which works ok: I do not see any difference between this and using the .navigationLinkIndicatorVisibility modifier. It places a NavigationLink with no content over your view. ZStack { YourView() // Hack to prevent the disclosure indicator from showing NavigationLink(value: ScreenType.detail(toDo.guid)) { EmptyView() }.opacity(0) } // .navigationLinkIndicatorVisibility(.hidden) // Not properly backported to < iOS 26, so crashes on launch.
Topic: UI Frameworks SubTopic: SwiftUI
3w
Reply to SwiftData Fatal error: Editors must register their identifiers before invoking operations on this store
Update: I managed to reproduce the crash and solve it (I think). I had a scenario where the ModelActor in some cases would leak and stay transient after the user logged out. If another user logged in afterwards and another instance of the ModelActor would be created, this crash would occur. After I fixed the leak, the app seemingly no longer crashes. It's still a bit of a mystery to me, why it would crash though. The ModelActors are initialized with their own user-specific database, so they are completely distinct. My theory is that the leaked database could reference some resources that no longer existed after the user logged out and that caused the crash.
Topic: App & System Services SubTopic: iCloud & Data Tags:
3w
Reply to Invalid Code Signing Entitlements
Removing the Entitlements.plist did solve the Validation failed (409) error, but my app was still crashing on launch in TestFlight. I had to add None to my csproj file to stop the launch crash, which means there is some kind of linker issue, but I haven't been able to narrow it down any further yet.
Topic: Code Signing SubTopic: Entitlements Tags:
3w
Invalid Code Signing Entitlements
Hi, I have a .NET MAUI app which I've added subscriptions to using the Plugin.InAppBilling nuget package. When I tested on TestFlight I got an almost immediate crash. After doing some research I followed advice to add an Entitlements.plist file to Platforms > iOS with the following entry: com.apple.developer.in-app-purchase The distribution provisioning profile I'm using to sign my app has the App ID set to an Identifier which has In-App Purchase ticked, but greyed out in it's Capabilities section on https://developer.apple.com/. I'm not sure why it's ticked and greyed out, but I assume that means that In-App Purchase is enabled. The app runs file locally but when I create an IPA file and add it to Transporter for upload to App Store Connect I get the following error: Validation failed (409) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.in-app-purchase' in 'Payload/[Rem
Topic: Code Signing SubTopic: Entitlements Tags:
4
0
376
Aug ’25
Reply to Where's the replacement for Quartz Debug?
Hello, Quartz Debug is available as an additional tools package for Xcode. For example, Additional Tools for Xcode 26 beta 6 contains: This package includes audio, graphics, hardware I/O, and other auxiliary tools. These tools include AU Lab, OpenGL Driver Monitor, OpenGL Profiler, *****, Quartz Debug, CarPlay Simulator, HomeKit Accessory Simulator, IO Registry Explorer, Network Link Conditioner, PacketLogger, Printer Simulator, 64BitConversion, Clipboard Viewer, Crash Reporter Prefs, Dictionary Development Kit, Help Indexer, and Modem Scripts.
Topic: Developer Tools & Services SubTopic: General Tags:
4w
Xcode 26 beta 5 xcodebuild crash
Good day! When your project have total 887 or more SPM local targets and then you try to build it, xcodebuild will be crash. Crash log: SWBBuildService-2025-08-11-151103.ips Thread 2 Crashed:: Dispatch queue: com.apple.root.default-qos.cooperative 0 libxpc.dylib 0x197c4826c _availability_version_check + 8 1 libswiftCore.dylib 0x1a9b44428 __isPlatformVersionAtLeast + 92 2 libswiftCore.dylib 0x1a9a6e054 _swift_allocObject_ + 1100 3 SWBMacro 0x104a9c408 specialized _ArrayBuffer._consumeAndCreateNew(bufferIsUnique:minimumCapacity:growForAppend:) + 116 4 SWBMacro 0x104a97b58 specialized Array.append(contentsOf:) + 116 5 SWBMacro 0x104a954e8 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 160 6 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 7 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 8 SWBMacro 0x104a96548 MacroEvaluationProgra
Topic: Developer Tools & Services SubTopic: Xcode Tags:
4
0
172
4w