Search results for

“LLDB crash”

30,535 results found

Post

Replies

Boosts

Views

Activity

Reply to System Panic with IOUserSCSIParallelInterfaceController during Dispatch Queue Configuration
Part 1... However, a subsequent call to ivars->fResponseMap->GetAddress() returns NULL (0x0). Subsequent call when? The expectation (and what our driver does) is that you'd immediately call GetAddress() and then basically never look at the map again. In one of our drivers, that never is quite literal. The code is basically: IOMemoryMap *memoryMap = NULL; if ( parallelCommandIOMemoryDescriptor->CreateMapping(0, 0, 0, 0, 0, &memoryMap) == kIOReturnSuccess ) { ivars->fCommandAddress = memoryMap->GetAddress(); } ... if ( parallelResponseIOMemoryDescriptor->CreateMapping(0, 0, 0, 0, 0, &memoryMap) == kIOReturnSuccess ) { ivars->fParallelResponseAddress = memoryMap->GetAddress(); } ...and, yes, that code leaks two IOMemoryMap's. I don't know what the exact thinking was, but I suspect they realized that the only reason that mapping would ever become invalid/useless was because the driver was being torn down, so freeing doesn't really matter. I'll admit, there is a certain charm to tha
Topic: App & System Services SubTopic: Drivers Tags:
Feb ’26
Reply to failed to set category, reason: 未能完成操作。（OSStatus错误4097。）
Thanks for the post and the crash file. Looks like you have received no replies. Looking at the crash file it seems like 135 threads at least. I would recommend to go ahead and create a focused sample project that reproduces this issue as I'm not aware of any open bugs on that API. Why not calling it from the main thread? Do you get the same results with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.
Topic: Media Technologies SubTopic: Audio Tags:
Feb ’26
Questions on OS Activity Tracing
This is stemmed from another forum post on Apple Unified Logging. A few additional questions were raised towards a relevant but different topic - activity tracing, starting a new post following The Eskimo's suggestion. The first question is on log capture from an activity chain. The related documentation stated something but very vaguely. https://developer.apple.com/documentation/os/generating-log-messages-from-your-code?language=objc#Choose-the-Appropriate-Log-Level-for-Each-Message If an activity object exists, the system captures information for the related process chain We had hoped that this would somewhat play into the speculative logging approach we had touched upon in the original post, in the sense that if we try to log an error or fault within an activity, then it helps to capture and persist other logs on the activity chain even though they are originally not meant to be. But unfortunately from our test it didn't seem to be behaving towards that understanding. Then our question is, if we may ask -
Topic: App & System Services SubTopic: Core OS Tags:
1
0
97
Feb ’26
Cannot preview in this file – SwiftUI Preview referencing deleted simulator
I'm running Xcode 26.2 (17C52). After deleting all simulators and creating new ones, SwiftUI Preview stopped working. Xcode reports: “Simulator [D774B214-XXXX-XXXX-XXXX-XXXXXXXX8288] failed to boot and may have crashed.” However, when I list all available simulators using xcrun simctl list, there is no simulator with that identifier. It seems Xcode is still referencing a previously deleted simulator. I have tried: Deleting all simulators again Creating new simulators Restarting Xcode and the system But the issue persists and Preview still fails to launch. Has anyone encountered this issue or knows how to clear the cached simulator reference used by SwiftUI Preview?
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
102
Feb ’26
Reply to Any (developer) option to override log quarantine?
Apologies I meant to ask about activity tracing as well (they are related to this topic but if we think another forum post is better I can do it too). At certain point this also became one of the directions we wanted to explore but we've only uncovered more questions. The related documentation stated something but very vaguely. https://developer.apple.com/documentation/os/generating-log-messages-from-your-code?language=objc#Choose-the-Appropriate-Log-Level-for-Each-Message If an activity object exists, the system captures information for the related process chain We had hoped that this would somewhat play into the speculative logging approach we had touched upon, in the sense that if we try to log an error or fault within an activity, then it helps to capture and persist other logs on the activity chain even though they are originally not meant to be. But unfortunately from our test it didn't seem to be behaving towards that understanding. Then our question is, if we may ask - what are the exact additional in
Topic: App & System Services SubTopic: Core OS Tags:
Feb ’26
Repeated NUIdentifier crash
Some of our app's users are repeatedly running into a crash on NeutrinoCore -[NUIdentifier initWithNamespace:name:version:] + 2352. It looks from the stack trace like multiple threads are performing PHFetchRequests, but that shouldn't be causing a crash. It's isolated to a small number of users, which makes me think that it's something related to their specific Photos databases (e.g., data corruption.) Do you have any suggestions how I might be able to resolve this? 2 libsystem_c.dylib abort + 124 3 NeutrinoCore -[NUAssertionPolicyCrashReport notifyAssertion:] + 66 4 NeutrinoCore -[NUAssertionPolicyComposite notifyAssertion:] + 160 5 NeutrinoCore -[NUAssertionPolicyUnique notifyAssertion:] + 176 6 NeutrinoCore -[NUAssertionHandler handleFailureInFunction:file:lineNumber:currentlyExecutingJobName:description:arguments:] + 156 7 NeutrinoCore _NUAssertFailHandler + 176 8 NeutrinoCore -[NUIdentifier initWithNamespace:name:version:] + 2352 9 NeutrinoCore -[NUIdentifier initWithName:version:] + 84
Topic: Media Technologies SubTopic: Photos & Camera Tags:
0
0
216
Feb ’26
UIActivityViewController not vertically scrollable when sharing CSV on specific device (Save option unreachable)
Platform UIKit iOS UIActivityViewController Environment Device (issue reported): iPhone 16 iOS Version: 26.2 App Type: UIKit / Swift (standard modal presentation of UIActivityViewController) Summary When presenting UIActivityViewController to share a CSV file, the share sheet does not allow vertical scrolling, making lower actions (including Save to Files) unreachable. The same flow works correctly when sharing a PDF, and the issue cannot be reproduced on other test devices. Steps to Reproduce Launch the app and log in Navigate to More → Reports Tap Export Report Choose Export Report (CSV) Observe the share sheet Expected Result The user should be able to vertically scroll the share sheet All share actions (including Save to Files) should be reachable Actual Result Share sheet opens but vertical scrolling is disabled Lower options (including Save to Files) are not reachable No crash or console errors
Topic: UI Frameworks SubTopic: UIKit Tags:
3
0
410
Feb ’26
Reply to Apps closed in background without crashlog or hint
Termination in the background is part of the normal iOS app lifecycle. When the user moves your app to the background, the system typically suspends it. After that, if the system gets low on resources, typically memory, it’ll terminate your app, thus removing it from memory. This is absolutely normal; iOS has behaved this way since we introduced multitasking. This doesn’t generate a crash report because the app hasn’t crashed. The system tends to terminate apps that are using more memory, so one way to reduce the chances of this happening to your app is to reduce your memory footprint as you move into the background. If you’d like to explore that option, check out Making changes to reduce memory use. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Processes & Concurrency
Feb ’26
Reply to Read, Write, and Consuming Files / URLs
After thinking about this some more, I'm not sure reading a store directly from the asset pack will solve my issue. The database get's updated regularly, so if there's an update that finishes downloading while the app is running, the original linked store will be destroyed and replaced with the new one. Which probably will crash the app.
Topic: App & System Services SubTopic: iCloud & Data Tags:
Feb ’26
iOS 26 Crash: _xzm_xzone_malloc_freelist_outlined in com.apple.network.connections
Hello Apple Support Team, We are seeing a production crash on iOS 26 devices that appears to originate from Apple system frameworks rather than application code. Crash Summary Crash signature: _xzm_xzone_malloc_freelist_outlined Crashed thread: com.apple.network.connections Frameworks involved: CFNetwork, Security, libdispatch, libsystem_malloc Affected OS: iOS 26.x App built with: Xcode 16 Devices: Multiple models (not device-specific) Reproducibility: Intermittent, higher frequency during app launch / background networking Observed Stack Trace (top frames) _xzm_xzone_malloc_freelist_outlined dispatch_data_create_alloc xpc_data_deserialize SecTrustEvaluateIfNecessary CFNetwork HTTPProtocol / HTTP3Connection com.apple.network.connections App Context The app uses URLSession for networking. Multiple third-party SDKs are integrated (Firebase Analytics, Dynatrace, Appsflyer, and similar analytics/monitoring SDKs). These SDKs perform concurrent background network requests, espec
Topic: App & System Services SubTopic: Networking
0
0
195
Feb ’26
Reply to iOS Simulator fails to boot (18.6 / 26.1 / 26.2) – launchd_sim could not bind to session
I’m facing an issue where iOS Simulator versions 18.6 and above (including iOS 26.0.1) fail to boot, while older simulators like iOS 18.0 / 18.2 work fine on the same machine. Environment macOS 26.2 (Build 25C56) Xcode 26.0 (Build 17A324) iOS Simulator runtimes: iOS 18.0 – works iOS 18.6 – fails to boot iOS 26.0.1 – fails to boot Error observed Unable to boot the Simulator NSPOSIXErrorDomain Code: 4 (Interrupted system call) Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding This happens even when launching the Simulator app directly (without running any app). Steps already tried (no success) Shut down and erased all simulators: xcrun simctl shutdown all xcrun simctl erase all Deleted CoreSimulator data: rm -rf ~/Library/Developer/CoreSimulator killall -9 com.apple.CoreSimulator.CoreSimulatorService Rebooted macOS multiple times Reinstalled simulator runtimes via Xcode → Settings → Platforms Attempted runtime deletion using: xcrun simctl runtime de
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Feb ’26
Reply to LLDB assertion failure when debugging Swift app
The last line of the message says: Please file a bug report against lldb reporting this failure log, and as many details as possible Let's start there — what is the FB of your report in Feedback Assistant? Further, make sure to include things like the Xcode version and the OS version you are debugging on, and to see if this reproduces with the latest Xcode version, currently Xcode 26.2. — Ed Ford,  DTS Engineer
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Feb ’26
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:
Feb ’26
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
Topic: UI Frameworks SubTopic: UIKit Tags:
1
0
193
Feb ’26
Reply to System Panic with IOUserSCSIParallelInterfaceController during Dispatch Queue Configuration
Part 1... However, a subsequent call to ivars->fResponseMap->GetAddress() returns NULL (0x0). Subsequent call when? The expectation (and what our driver does) is that you'd immediately call GetAddress() and then basically never look at the map again. In one of our drivers, that never is quite literal. The code is basically: IOMemoryMap *memoryMap = NULL; if ( parallelCommandIOMemoryDescriptor->CreateMapping(0, 0, 0, 0, 0, &memoryMap) == kIOReturnSuccess ) { ivars->fCommandAddress = memoryMap->GetAddress(); } ... if ( parallelResponseIOMemoryDescriptor->CreateMapping(0, 0, 0, 0, 0, &memoryMap) == kIOReturnSuccess ) { ivars->fParallelResponseAddress = memoryMap->GetAddress(); } ...and, yes, that code leaks two IOMemoryMap's. I don't know what the exact thinking was, but I suspect they realized that the only reason that mapping would ever become invalid/useless was because the driver was being torn down, so freeing doesn't really matter. I'll admit, there is a certain charm to tha
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
Feb ’26
Reply to SpringBoard Crashes on macOS Simulator When Receiving Critical Alerts
@Engineer I am running into this same Springboard crash when posting a Critical Alert notification in the iOS 26 Simulator. @mnydigital Did you ever get a resolution, or even a workaround, to this issue?
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Feb ’26
Reply to failed to set category, reason: 未能完成操作。（OSStatus错误4097。）
Thanks for the post and the crash file. Looks like you have received no replies. Looking at the crash file it seems like 135 threads at least. I would recommend to go ahead and create a focused sample project that reproduces this issue as I'm not aware of any open bugs on that API. Why not calling it from the main thread? Do you get the same results with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.
Topic: Media Technologies SubTopic: Audio Tags:
Replies
Boosts
Views
Activity
Feb ’26
Questions on OS Activity Tracing
This is stemmed from another forum post on Apple Unified Logging. A few additional questions were raised towards a relevant but different topic - activity tracing, starting a new post following The Eskimo's suggestion. The first question is on log capture from an activity chain. The related documentation stated something but very vaguely. https://developer.apple.com/documentation/os/generating-log-messages-from-your-code?language=objc#Choose-the-Appropriate-Log-Level-for-Each-Message If an activity object exists, the system captures information for the related process chain We had hoped that this would somewhat play into the speculative logging approach we had touched upon in the original post, in the sense that if we try to log an error or fault within an activity, then it helps to capture and persist other logs on the activity chain even though they are originally not meant to be. But unfortunately from our test it didn't seem to be behaving towards that understanding. Then our question is, if we may ask -
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
97
Activity
Feb ’26
Cannot preview in this file – SwiftUI Preview referencing deleted simulator
I'm running Xcode 26.2 (17C52). After deleting all simulators and creating new ones, SwiftUI Preview stopped working. Xcode reports: “Simulator [D774B214-XXXX-XXXX-XXXX-XXXXXXXX8288] failed to boot and may have crashed.” However, when I list all available simulators using xcrun simctl list, there is no simulator with that identifier. It seems Xcode is still referencing a previously deleted simulator. I have tried: Deleting all simulators again Creating new simulators Restarting Xcode and the system But the issue persists and Preview still fails to launch. Has anyone encountered this issue or knows how to clear the cached simulator reference used by SwiftUI Preview?
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
2
Boosts
0
Views
102
Activity
Feb ’26
Reply to Any (developer) option to override log quarantine?
Apologies I meant to ask about activity tracing as well (they are related to this topic but if we think another forum post is better I can do it too). At certain point this also became one of the directions we wanted to explore but we've only uncovered more questions. The related documentation stated something but very vaguely. https://developer.apple.com/documentation/os/generating-log-messages-from-your-code?language=objc#Choose-the-Appropriate-Log-Level-for-Each-Message If an activity object exists, the system captures information for the related process chain We had hoped that this would somewhat play into the speculative logging approach we had touched upon, in the sense that if we try to log an error or fault within an activity, then it helps to capture and persist other logs on the activity chain even though they are originally not meant to be. But unfortunately from our test it didn't seem to be behaving towards that understanding. Then our question is, if we may ask - what are the exact additional in
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Feb ’26
Repeated NUIdentifier crash
Some of our app's users are repeatedly running into a crash on NeutrinoCore -[NUIdentifier initWithNamespace:name:version:] + 2352. It looks from the stack trace like multiple threads are performing PHFetchRequests, but that shouldn't be causing a crash. It's isolated to a small number of users, which makes me think that it's something related to their specific Photos databases (e.g., data corruption.) Do you have any suggestions how I might be able to resolve this? 2 libsystem_c.dylib abort + 124 3 NeutrinoCore -[NUAssertionPolicyCrashReport notifyAssertion:] + 66 4 NeutrinoCore -[NUAssertionPolicyComposite notifyAssertion:] + 160 5 NeutrinoCore -[NUAssertionPolicyUnique notifyAssertion:] + 176 6 NeutrinoCore -[NUAssertionHandler handleFailureInFunction:file:lineNumber:currentlyExecutingJobName:description:arguments:] + 156 7 NeutrinoCore _NUAssertFailHandler + 176 8 NeutrinoCore -[NUIdentifier initWithNamespace:name:version:] + 2352 9 NeutrinoCore -[NUIdentifier initWithName:version:] + 84
Topic: Media Technologies SubTopic: Photos & Camera Tags:
Replies
0
Boosts
0
Views
216
Activity
Feb ’26
UIActivityViewController not vertically scrollable when sharing CSV on specific device (Save option unreachable)
Platform UIKit iOS UIActivityViewController Environment Device (issue reported): iPhone 16 iOS Version: 26.2 App Type: UIKit / Swift (standard modal presentation of UIActivityViewController) Summary When presenting UIActivityViewController to share a CSV file, the share sheet does not allow vertical scrolling, making lower actions (including Save to Files) unreachable. The same flow works correctly when sharing a PDF, and the issue cannot be reproduced on other test devices. Steps to Reproduce Launch the app and log in Navigate to More → Reports Tap Export Report Choose Export Report (CSV) Observe the share sheet Expected Result The user should be able to vertically scroll the share sheet All share actions (including Save to Files) should be reachable Actual Result Share sheet opens but vertical scrolling is disabled Lower options (including Save to Files) are not reachable No crash or console errors
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
3
Boosts
0
Views
410
Activity
Feb ’26
Reply to Apps closed in background without crashlog or hint
Termination in the background is part of the normal iOS app lifecycle. When the user moves your app to the background, the system typically suspends it. After that, if the system gets low on resources, typically memory, it’ll terminate your app, thus removing it from memory. This is absolutely normal; iOS has behaved this way since we introduced multitasking. This doesn’t generate a crash report because the app hasn’t crashed. The system tends to terminate apps that are using more memory, so one way to reduce the chances of this happening to your app is to reduce your memory footprint as you move into the background. If you’d like to explore that option, check out Making changes to reduce memory use. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Processes & Concurrency
Replies
Boosts
Views
Activity
Feb ’26
Reply to Read, Write, and Consuming Files / URLs
After thinking about this some more, I'm not sure reading a store directly from the asset pack will solve my issue. The database get's updated regularly, so if there's an update that finishes downloading while the app is running, the original linked store will be destroyed and replaced with the new one. Which probably will crash the app.
Topic: App & System Services SubTopic: iCloud & Data Tags:
Replies
Boosts
Views
Activity
Feb ’26
iOS 26 Crash: _xzm_xzone_malloc_freelist_outlined in com.apple.network.connections
Hello Apple Support Team, We are seeing a production crash on iOS 26 devices that appears to originate from Apple system frameworks rather than application code. Crash Summary Crash signature: _xzm_xzone_malloc_freelist_outlined Crashed thread: com.apple.network.connections Frameworks involved: CFNetwork, Security, libdispatch, libsystem_malloc Affected OS: iOS 26.x App built with: Xcode 16 Devices: Multiple models (not device-specific) Reproducibility: Intermittent, higher frequency during app launch / background networking Observed Stack Trace (top frames) _xzm_xzone_malloc_freelist_outlined dispatch_data_create_alloc xpc_data_deserialize SecTrustEvaluateIfNecessary CFNetwork HTTPProtocol / HTTP3Connection com.apple.network.connections App Context The app uses URLSession for networking. Multiple third-party SDKs are integrated (Firebase Analytics, Dynatrace, Appsflyer, and similar analytics/monitoring SDKs). These SDKs perform concurrent background network requests, espec
Topic: App & System Services SubTopic: Networking
Replies
0
Boosts
0
Views
195
Activity
Feb ’26
Reply to iOS Simulator fails to boot (18.6 / 26.1 / 26.2) – launchd_sim could not bind to session
I’m facing an issue where iOS Simulator versions 18.6 and above (including iOS 26.0.1) fail to boot, while older simulators like iOS 18.0 / 18.2 work fine on the same machine. Environment macOS 26.2 (Build 25C56) Xcode 26.0 (Build 17A324) iOS Simulator runtimes: iOS 18.0 – works iOS 18.6 – fails to boot iOS 26.0.1 – fails to boot Error observed Unable to boot the Simulator NSPOSIXErrorDomain Code: 4 (Interrupted system call) Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding This happens even when launching the Simulator app directly (without running any app). Steps already tried (no success) Shut down and erased all simulators: xcrun simctl shutdown all xcrun simctl erase all Deleted CoreSimulator data: rm -rf ~/Library/Developer/CoreSimulator killall -9 com.apple.CoreSimulator.CoreSimulatorService Rebooted macOS multiple times Reinstalled simulator runtimes via Xcode → Settings → Platforms Attempted runtime deletion using: xcrun simctl runtime de
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Feb ’26
Reply to LLDB assertion failure when debugging Swift app
The last line of the message says: Please file a bug report against lldb reporting this failure log, and as many details as possible Let's start there — what is the FB of your report in Feedback Assistant? Further, make sure to include things like the Xcode version and the OS version you are debugging on, and to see if this reproduces with the latest Xcode version, currently Xcode 26.2. — Ed Ford,  DTS Engineer
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Feb ’26
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:
Replies
Boosts
Views
Activity
Feb ’26
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
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
1
Boosts
0
Views
193
Activity
Feb ’26