Search results for

LLDB crash

30,300 results found

Post

Replies

Boosts

Views

Activity

Reply to Enrollment not completed
I'm having the exact same issue. I took out my IDs and then the developer app crashed each time I got to this point. I called apple support and they said there is nothing that can be done because they cannot verify my identity. So let me verify, I'm ready to verify. I called in multiple times and they told me the same thing each time.
Topic: Community SubTopic: Apple Developers Tags:
2w
Where did I screw up trying concurrency?
I tried making a concurrency-safe data queue. It was going well, until memory check tests crashed. It's part of an unadvertised git project. Its location is: https://github.com/CTMacUser/SynchronizedQueue/commit/84a476e8f719506cbd4cc6ef513313e4e489cae3 It's the blocked-off method `memorySafetyReferenceTypes' in SynchronizedQueueTests.swift. Note that the file and its tests were originally AI slop.
2
0
189
2w
WKWebView + Bluetooth Keyboard: Ctrl+Home / Ctrl+End causes app crash after input blur (iPadOS 18.4.1 / 18.6.2)
1. Summary In a hybrid iOS app using WKWebView (Angular + Capacitor), after programmatically blurring an element and connecting a Bluetooth keyboard, pressing Ctrl+Home or Ctrl+End causes the app to crash. The crash stack shows the issue occurs inside UIKit keyboard handling (UITextInteractionSelectableInputDelegate _moveToStartOfLine), indicating a system-level bug. 2. Steps to Reproduce Open the hybrid app containing a WKWebView. Blur the input (programmatically). Connect a Bluetooth keyboard. Press Ctrl + Home or Ctrl + End. Expected result: No crash. The command should be ignored if no text input is active. Actual result: App crashes immediately. 3. Crash Log (Crashlytics Trace) Crashed: com.apple.main-thread 0 WebKit 0xfbdad0 + 236 1 UIKitCore 0x10b0548 -[UITextInteractionSelectableInputDelegate _moveToStartOfLine:withHistory:] + 96 2 UIKitCore 0xd0fb38 -[UIKBInputDelegateManager _moveToStartOfLine:withHistory:] + 188 3 UIKitCore 0xa16174 __158-[_UIK
1
0
163
2w
Live Activity – crashes on ActivityAuthorizationInfo() and Activity.activities
Hey! I'm working on enabling remotely started live activities. I'm running into 2 crashes: Upon initializing ActivityAuthorizationInfo Upon calling Activity<...>.activities array Both stack traces look like this: 0 libsystem_kernel.dylib +0xce0 _mach_msg2_trap 1 libsystem_kernel.dylib +0x4398 _mach_msg2_internal 2 libsystem_kernel.dylib +0x42b4 _mach_msg_overwrite 3 libsystem_kernel.dylib +0x40fc _mach_msg 4 libdispatch.dylib +0x1cc04 __dispatch_mach_send_and_wait_for_reply 5 libdispatch.dylib +0x1cfa4 _dispatch_mach_send_with_result_and_wait_for_reply 6 libxpc.dylib +0x107ec _xpc_connection_send_message_with_reply_sync 7 BoardServices +0xaea8 -[BSXPCServiceConnectionMessage _sendWithMode:] 8 BoardServices +0x17938 -[BSXPCServiceConnectionMessage sendSynchronouslyWithError:] 9 BoardServices +0xeef0 ___71+[BSXPCServiceConnectionProxy createImplementationOfProtocol:forClass:]_block_invoke They happen to a limited number of users, but not insignificant. Most are on iOS 18.6.2 and iOS 26.1, but the
3
0
374
2w
Reply to Bug? SwiftData + inheritance + optional many-to-one relationship
I encountered another bug with SwiftData and inheritance and reported it (FB21837287). This one is not related to CloudKit. Briefly, SwiftData crashes during auto-save when the schema contains: A base @Model class with at least one subclass (inheritance) A separate @Model class with a reference to the base class The crash occurs specifically when: There is a class inheritance hierarchy (Beta: Alpha) A separate class (Standalone) has a reference typed as the base class (Alpha?) Changing the reference from var ref: Alpha? to var ref: Beta? (subclass) eliminates the crash.
2w
Reply to M4 iPadOS stuck at Apple Logo on reboot.
I had the same problem with my M2 iPad Air, and ChatGPT told me to do this instantly worked. but you have to follow the instructions Yes — here’s the clean, repeatable fix for an iPad stuck in a reboot loop (Apple logo → restarts → logo again). Start at Step 1 and only move on if it doesn’t work. ⸻ Step 1 — Force restart (fastest, safest) This fixes temporary system crashes. If your iPad has Face ID (no Home button): 1. Quickly press Volume Up → release 2. Quickly press Volume Down → release 3. Press and HOLD Power 4. Keep holding until you see the Apple logo, then let go If your iPad has a Home button: 1. Hold Home + Power together 2. Keep holding until the Apple logo appears 👉 If it boots normally, you’re done. ⸻ Step 2 — Recovery Mode (most common real fix) Use this if it keeps looping. What you need • A Mac or Windows PC • A cable • Finder (Mac) or iTunes (Windows / older macOS) Steps 1. Connect iPad to the computer 2. Force-restart but DO NOT release when the Apple logo appears 3. Keep holding
3w
Inserting an NSView (Cocoa) in NSWindowController Views hierarchy
I have an NSWindowController with several IBOutlets created in storyboard. I want to add an NSView and fill it with some color. I need to place it at a specific position in views hierarchy. I have tried 2 ways, no one succeeds. First. include a custom view in storyboard connect to an IBOutlet in an init of controller, set the layer for the view Result: crash Second build programmatically Result: I do not find where to put this code in the controller code That's basic Cocoa, but way more painful than iOS.
Topic: UI Frameworks SubTopic: AppKit Tags:
3
0
283
3w
NSTextLineFragment crash - how to debug
We have crash reports as shown below that we haven't yet been able to repro and could use some help deubgging. My guess is that the app is giving a label or text view an attributed string with an invalid attribute range, but attributed strings are used in many places throughout the app, and I don't know an efficient way to track this down. I'm posting the stack trace here in hopes that someone more familiar with the internals of the system frameworks mentioned will be able to provide a clue to help narrow where I should look. Fatal Exception: NSRangeException NSMutableRLEArray objectAtIndex:effectiveRange:: Out of bounds 0 CoreFoundation 0x2d5fc __exceptionPreprocess 1 libobjc.A.dylib 0x31244 objc_exception_throw 2 Foundation 0x47130 blockForLocation 3 UIFoundation 0x2589c -[NSTextLineFragment _defaultRenderingAttributesAtCharacterIndex:effectiveRange:] 4 UIFoundation 0x25778 __53-[NSTextLineFragment initWithAttributedString:range:]_block_invoke 5 CoreText 0x58964 TLine::DrawGlyphsWithAttributeOverri
6
0
494
3w
Reply to NSTextLineFragment crash - how to debug
Thanks for providing the reproducible case, which will greatly help the TextKit folks to address the issue from the framework side. As the reproducible case shows, the crash is triggered by a specific combination of attributes. Unless you can identify the cases and avoid them, I unfortunately don't see anything from the app side that can fix / work around the issue. I have added my comment to the feedback report (FB16905066). Thank you all again for making the feedback much more actionable by providing the project that reproduces the crash. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: UIKit Tags:
3w
Reply to Inserting an NSView (Cocoa) in NSWindowController Views hierarchy
For your first approach, are you able to provide information about the crash, like a crash log? For your second approach, it is common to see initial view hierarchy setup for a window in your window controller subclass’s overridden windowDidLoad method. For a view that just needs to display a solid color, NSBox can be used for this purpose: let box = NSBox() box.boxType = .custom box.borderWidth = 0.0 box.fillColor = NSColor.systemRed
Topic: UI Frameworks SubTopic: AppKit Tags:
3w
Reply to Horrible weird Window Server killing bug
This got even weirder. One is that sometimes the use of cos() would cause a compiler error, which was fixed by using Darwin.cos(). This may be fixed in Swift 6.3. The other thing is that in my much more complex code, the crash seemed to be caused by both the cos() call evaluating to 0, but only when the line being drawn with that result had a StrokeStyle applied to it. In anycase, I have filed Feedbacks explaining this, and I'm told the WindowServer team has had it brought to their attention.
Topic: UI Frameworks SubTopic: SwiftUI
3w
Reply to why mapkit js does not have LookAroundSceneRequest
Ed Ford,  DTS Engineer Your reply does not help. I have look at the sample code thousands times before I ask this question here. The sample code, and document api does not mention how to update coordinate for the look around object. I need constantly change the look around scene coordinate, the sample code only create look around object based on one coordinate. If I need to update coordinate to a different location for this look around object, can you share the sample code to do this job here for everyone that is interested? This is my code, it destroy everytime before create a new one. It works, but it can crash browser webGL if user change coordinate 16 times and above , then it cause apple base map blank. ` // // --- --- apple look around --- // var lookAround var is_lookAround_load_complete = false var is_first_time_lookAround = true // only for 1st time load function create_apple_look_around(lookAround_lat, lookAround_lng){ /* no way to update coordinate of existing look around object, have to
3w
Apple Intelligence crashed/stopped working
Hi everyone, I’m currently using macOS Version 15.3 Beta (24D5034f), and I’m encountering an issue with Apple Intelligence. The image generation tools seem to work fine, but everything else shows a message saying that it’s “not available at this time.” I’ve tried restarting my Mac and double-checked my settings, but the problem persists. Is anyone else experiencing this issue on the beta version? Are there any fixes or settings I might be overlooking? Any help or insights would be greatly appreciated! Thanks in advance!
3
0
1.6k
3w
[iOS 26.2] Crash due to WKScriptMessageHandler delegate
The crash is specific to iOS 26.2 prior versions working fine. WKScriptMessageHandler delegate func userContentController(_ userContentController: WKUserContentController, didReceive message: WKScriptMessage) Name attribute is accessible but WKScriptMessage body attribute causes crash The object seems to be not accessible(not in memory) self.webkit.configuration.userContentController.add(self, name: sampleHandler) self.webkit.load(request) func userContentController(_ userContentController: WKUserContentController, didReceive message: WKScriptMessage) { print(message.name) // works print(message.body) // crashes }
5
0
1.6k
3w