Search results for

LLDB crash

29,550 results found

Post

Replies

Boosts

Views

Activity

Reply to Notification Service Extension Not Working
Unfortunately, appears to not be executing could be for a lot of reasons, and you will need to first debug and understand what the cause of this NSE not working is, so you can fix it. The reasons the NSE fails to modify the message could be: it crashes at launch it crashes while modifying or exits early without setting the content and calling contentHandler() it goes over the memory and time limits and is terminated by the system it is trying to access on-disk objects that are not available (perhaps due to security settings) and fails the reentrancy of the NSE causes problems if any global variables/singletons/shared objects are not designed accordingly that the same NSE process could be used for multiple notifications it is unable to be started by the system for some reason (the Console log will show those issues) the extension is not configured or built correctly in your application bundle notification is not delivered to the device there is a problem with the notification payload that get
Topic: App & System Services SubTopic: Notifications Tags:
3w
Core Data initialization causes app to deadlock on startup
Users have been reporting that the TestFlight version of my app (compiled with Xcode 26 Beta 6 17A5305f) is sometimes crashing on startup. Upon investigating their ips files, it looks like Core Data is locking up internally during its initialization, resulting in iOS killing my app. I have not recently changed my Core Data initialization logic, and it's unclear how I should proceed. Is this a known issue? Any recommended workaround? I have attached the crash stack below. Thanks! crash_log.txt
Topic: App & System Services SubTopic: iCloud & Data Tags:
2
0
133
3w
Reply to App Crashes on Paper Selection After Background Printer Connection
Yes, we see a lot of crashes like this in our apps, too. But we can't reproduce it. OS Version: iPhone OS 18.6 (22G86) Release Type: User Baseband Version: 2.70.02 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Reason: *** -[__NSSingleObjectArrayI objectAtIndex:]: index 2 beyond bounds [0 .. 0] Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: OurAppName [72412] Triggered by Thread: 0 Last Exception Backtrace: 0 CoreFoundation 0x1950500c0 __exceptionPreprocess + 164 (NSException.m:249) 1 libobjc.A.dylib 0x1924e9abc objc_exception_throw + 88 (objc-exception.mm:356) 2 CoreFoundation 0x1950418c8 -[__NSSingleObjectArrayI objectAtIndex:] + 308 (NSSingleObjectArray.m:18) 3 PrintKitUI 0x1f34d4518 -[UIPrintPaperSizeOption listItemSelected:] + 88 (UIPrintMoreOptions.m:896) 4 PrintKitUI 0x1f34a0a0c -[UIPrintOptionListViewController tableView:didSelectRowAtIndexPath:] + 116 (UIPrintOptionCells.m:103) 5 UIKitCore 0x198b902fc
Topic: UI Frameworks SubTopic: UIKit Tags:
3w
Reply to Storekit configuration broken in Xcode 16.4 the file has been changed
I am experiencing a similar issue using an Xcode 16.4 with a simulator running IOS 18.6 I receive a series of this message when trying to load products from the StoreKit configuration file: Could not parse product: missingValue(for: [StoreKit.ProductResponse.Key.price], expected: StoreKit.BackingValue) If I enable Zombie Objects in the debugger, I also get these messages: Class _NSZombie_SKProductInternal is implemented in both ?? (0x1347517a0) and ?? (0x1347517d0). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed. I've tested the file on a handful of older simulators and everything works fine; neither error is reported on an IOS 18.0 simulator. I've also verified that things are working as expected with TestFlight so I'm less concerned about going to Production. Still, it would be nice be have a much higher level of confidence that there is not a serious bug somewhere before I roll out my next Production release.
Topic: App & System Services SubTopic: StoreKit Tags:
3w
EXC_BAD_ACCESS (SIGSEGV) crash observed in NSDateFormatter APIs
(NSString*)getClienttime { NSDate* currentDate = [NSDate date]; NSDateFormatter* dateformatter = [[NSDateFormatter alloc] init]; dateformatter.timeZone = [NSTimeZone timeZoneForSecondsFromGMT:8*3600]; dateformatter.locale= [NSLocale systemLocale]; [dateformatter setDateFormat:@yyyy-MM-dd HH:mm:ss]; return [dateformatter stringFromDate:currentDate]?:@; } the info of crash 1 libicucore.A.dylib icu::UnicodeString::copyFrom(icu::UnicodeString const&, signed char) (in libicucore.A.dylib) + 36 2 libicucore.A.dylib icu::DecimalFormatSymbols::operator=(icu::DecimalFormatSymbols const&) (in libicucore.A.dylib) + 64 3 libicucore.A.dylib icu::DecimalFormatSymbols::operator=(icu::DecimalFormatSymbols const&) (in libicucore.A.dylib) + 64 4 libicucore.A.dylib icu::DecimalFormat::DecimalFormat(icu::DecimalFormat const&) (in libicucore.A.dylib) + 188 5 libicucore.A.dylib icu::DecimalFormat::clone() const (in libicucore.A.dylib) + 48 6 libicucore.A.dylib icu::NumberFormat::createInstance(icu::Locale c
Topic: UI Frameworks SubTopic: UIKit
0
0
87
3w
Capturing the instruction trace from the ARM ETM
According to the ARM documentation for the CPU models available in Apple Silicon, the CoreSight implementation includes an Embedded Trace Macrocell which can perform a complete Instruction Trace (https://developer.arm.com/documentation/102119/0200/What-is-trace-). Although other operating systems such as Linux make this easy, we have not been able to find any tools or even a system-level API for accessing this feature of the ETM. In the Instruments window of Xcode 16+, there is a Processor Trace instrument, but this performs sampling and is totally unrelated to the Instruction Trace we need for debugging and analysis purposes. Because it produces a complete, contiguous sequence of branch instructions, the Instruction Trace is essential for identifying precise execution behaviors that are otherwise invisible to the developer. On other platforms, an alternative is debugger scripting, but we have found far too many bugs and reliability issues with the macOS implementation of lldb. Any suggestions would
Topic: Developer Tools & Services SubTopic: Instruments
1
0
147
3w
Reply to Verify with wallet run in simulator
Hi @PraneethK, You wrote: I am fallowing the steps mention here https://developer.apple.com/wallet/get-started-with-verify-with-wallet/ and https://developer.apple.com/documentation/passkit/requesting-identity-data-from-a-wallet-pass to run a POC in simulator but I am getting a crash [...] To use Verify with Wallet, you need to submit an entitlement request. Please review the Request the entitlement section of the following page to learn if you app is eligible for this entitlement: Get started with Verify with Wallet API https://developer.apple.com/wallet/get-started-with-verify-with-wallet/ Note: Building an app with this entitlement requires macOS 13 or later. Once you have been approved for the entitlement, review the following documentation as a guide to your implementation: Requesting identity data from a Wallet pass https://developer.apple.com/documentation/passkit/requesting-identity-data-from-a-wallet-pass Lastly, read the section titled Test the implementation for the expected behavior on a
Topic: App & System Services SubTopic: Wallet Tags:
3w
SwiftUI app crash with __swift_instantiateConcreteTypeFromMangledName
Hello, I am experiencing a crash in a SwiftUI app. It happens when I place multiple views inside a ScrollView. The crash occurs only on a physical device (it does not reproduce in the Simulator). It happens during runtime, seemingly while SwiftUI is updating or laying out the view hierarchy. I have not been able to determine the exact cause. I am attaching a text file with the entire backtrace from LLDB. swiftui_crash_backtrace Is this a known SwiftUI issue? Any recommendations on how to further investigate or work around it? Any help or suggestions would be appreciated. Xcode 16.3 / iOS 18.6.2 Thank you!
Topic: UI Frameworks SubTopic: SwiftUI Tags:
1
0
105
3w
Reply to Multicast Entitlements
Thank you for responding, and so quickly. You are correct on the first point, I don't have multicast entitlements in my app (got a nasty crash when I tried), but I am mostly attempting to send multicast udp packets, and kept hitting a roadblock with these permissions. The issue is with the Local Network Privacy permissions. The reason I think it is this, and not incorrect API usage, is I had the app installed on a brand new Mac Mini, and could not send UDP multicast packets from the app. I then ran the app from the Terminal, and it worked just fine. I realized I was missing these network permissions, and re-built and reinstalled it with these permissions enabled. The app worked temporarily after re-installing, but then restarting the machine, the app would again stop working and still not allow me to send these packets. It would work from the terminal (which says that the API's are used correctly. BSD sockets being what they are...) I then created a new user on that machine, and had no issues with th
Topic: App & System Services SubTopic: Networking
3w
Error in Xcode console
Lately I am getting this error. GenerativeModelsAvailability.Parameters: Initialized with invalid language code: en-GB. Expected to receive two-letter ISO 639 code. e.g. 'zh' or 'en'. Falling back to: en Does anyone know what this is and how it can be resolved. The error does not crash the app
Topic: Machine Learning & AI SubTopic: Foundation Models Tags:
1
0
725
3w
Reply to SwiftData Inheritance Query Specialized Model
Thanks a lot for helping Ziqiao, i've made a small iOS App that shows the issue which is available here: https://github.com/fgirardey/SwiftDataInheritance The step to reproduce are: Create a collection named Work Create another collection name Tech that has Work as a parent Kill the app, relaunch and see the crash happening when List is accessing to children through .childrenOrNil.
Topic: App & System Services SubTopic: iCloud & Data Tags:
3w
Reply to Capturing file read events in Endpoint Security client
Hi everyone! I'd like to create an application for system monitoring using the Endpoint Security framework. I already have a working prototype, and now I am trying to expand its capabilities to capture more event types. So, I need to pass you a broad warning here. It is VERY easy to put together a test/development app that works in the basic sense that it runs and doesn't create any obvious failure, but is in fact fundamentally flawed and will fail over and over again under real-world conditions. Even worse, most of these failures will not be simple crashes or hangs in your product but will instead be a variety of strange failures everywhere else. See the forum threads here, here, and here for a few examples. Started looking at filesystem-related events as one of the most important ones for my use case. These seem to be supported fairly well by the framework (ES_EVENT_TYPE_NOTIFY_OPEN/CLOSE/CREATE/WRITE, etc.). However, the READ FILE event seems to be absent… Am I missing something here, or does the
Topic: App & System Services SubTopic: Core OS Tags:
3w