Search results for

“LLDB crash”

30,536 results found

Post

Replies

Boosts

Views

Activity

Crash in swift::_getWitnessTable when passing UITraitBridgedEnvironmentKey
When using UITraitBridgedEnvironmentKey to pass a trait value to the swift environment, it causes a crash when trying to access the value from the environment. The issue seems to be related to how swift uses the UITraitBridgedEnvironmentKey protocol since the crash occurs in swift::_getWitnessTable () from lazy protocol witness table accessor…. It can occur when calling any function that is generic using the UITraitBridgedEnvironmentKey type. I originally encountered the issue when trying to use a UITraitBridgedEnvironmentKey in SwiftUI, but have been able to reproduce the issue with any function with a similar signature. https://developer.apple.com/documentation/swiftui/environmentvalues/subscript(_:)-9zku Steps to Reproduce Requirements for the issue to occur Project with a minimum iOS version of iOS 16 Build the project with Xcode 26 Run on iOS 18 Add the following code to a project and call foo(key: MyCustomTraitKey.self) from anywhere. @available(iOS 17.0, *) func foo(key: K.Type) where
4
0
240
Jan ’26
startProxy delegate for NETransparentProxyProvider class is being called twice for the same pid extension sometimes
We have an application which is written in Swift, which activates Transparent Proxy network extension. Our Transparent Proxy module is a system extension, which is exposing an app proxy provider interface (We are using NETransparentProxyProvider class and in extension’s Info.plist we use com.apple.networkextension.app-proxy key.) Sometimes we have observed that on starting the transparent proxy extension, the startProxy overridden delegate method(override func startProxy(options: [String : Any]?, completionHandler: @escaping (Error?) -> Void) {) in our AppProxyProvider class which is derived from NETransparentProxyProvider being called more than once for the same extension(pid). This leads to Over-resume of an object crash as we invoke setTunnelNetworkSettings inside the startProxy delegate. As this is controlled by the system, we are not sure why this delegate being called more than once sometimes even if we call the start TransparentProxy only once. Note that, this issue is seen only in Mac OS T
4
0
312
Jan ’26
Reply to Xcode 26 can no longer launch, and crashes immediately
Hi, there. Sorry you're dealing with this. We're aware of the issue and you can expect a broad fix to make its way into an Xcode near you soon. In the meantime, you can resolve this by removing the local user state for your Xcode Project or Workspace: Quit Xcode (if it's still running, or if another workspace is open). In Finder, find your .xcodeproj file Right-click it > Show Package Contents Navigate to: {project}.xcworkspace → xcuserdata Delete the xcuserdata folder Once you relaunch Xcode, you may need to recreate any user-local state for your project or workspace, but the crash will be gone and you will be able to keep working. Please follow up if you have any further difficulties. Thanks.
Jan ’26
Xcode 26 can no longer launch, and crashes immediately
Each time I try to launch Xcode 26, it immediately crashes in SourceEditorDataSource.ideChat_gracefullyApplyChangesToReflect. I'm now no longer able to use Xcode. A partial crash log attached. So far I've tried deleting derived data, rebooting, deleting ~/Library/Caches/com.apple.dt.Xcode. What should I do? Thank you in advance for any help. crash-report.txt
1
0
284
Jan ’26
Swift Playgrounds macOS repeatedly asks “My App would like to access data from other apps”
Environment: Swift Playgrounds (macOS) SwiftUI App Preview macOS version: 26.2 (25C56) Issue: In Swift Playgrounds on macOS, the app repeatedly shows the system permission dialog: “My App would like to access data from other apps. Keeping app data separate makes it easier to manage your privacy and security.” Steps to Reproduce: Create a new SwiftUI app in Swift Playgrounds. Run the SwiftUI App Preview. When the permission dialog appears, click “Allow”. Expected Result: The permission should be granted once and persist, allowing the preview to continue normally. Actual Result: After clicking “Allow”, the SwiftUI App Preview crashes and restarts. When the preview restarts, the same permission dialog appears again. This repeats indefinitely, creating a loop. Notes: This occurs even when no explicit file system or inter-app data access code is written. The permission choice does not appear to persist between preview restarts. Question: Is this a known limitation of Swift Playgrounds sandboxing or SwiftU
2
0
452
Jan ’26
Reply to C function in library code gets stripped when distributed
Here is a more step by step breakdown of the problem I have a iOS library that exposes a C function. This function is marked with default visibility and used via attribute tags to prevent the compiler/linker from stripping it #ifdef __cplusplus #define DYLIB_EXPORT extern C __attribute__((visibility(default))) __attribute__((used)) #else #define DYLIB_EXPORT __attribute__((visibility(default))) __attribute__((used)) #endif DYLIB_EXPORT bool say_hello_world(); #import helper_functions.h #import bool say_hello_world() { NSLog(@Hello WORLD 🟢!); return true; } From a dynamic library, called sdk, I want to call this function. In this example it's a Rust lib unsafe extern C { fn say_hello_world() -> bool; } #[unsafe(no_mangle)] extern C fn sdk_init() -> i32 { unsafe { say_hello_world(); } return 0; } When the app is compiled and launched from Xcode (either on debug or release schemes) then this works, the following snippet works and prints the hello WORLD message: #import OpacityObjCWrapper.h #import helper
Topic: Programming Languages SubTopic: General Tags:
Jan ’26
AVCaptureSession preview briefly goes blank after interruption (lock/unlock or camera switch) while isRunning == true
Environment Device: iPhone 15 Pro iOS: iOS 18.0 Framework: AVFoundation App type: Custom camera app using AVCaptureSession + AVCaptureVideoPreviewLayer I’m seeing an intermittent but frequent issue where the camera preview layer briefly flashes empty after certain interruptions, even though the capture session reports itself as running and no errors are emitted. This happens most often after: Locking and unlocking the device Switching cameras (back ↔ front) The issue is not 100% reproducible, but occurs often enough to be noticeable in normal usage. What happens The preview layer briefly flashes as empty (sometimes just a “micro-frame”) Duration: typically ~0.5–2 seconds before frames resume session.isRunning == true throughout No crash, no runtime error, no interruption end failure Focus/exposure restore correctly once frames resume Visually it looks like the preview layer loses frames temporarily, even though the session appears healthy. Repro Intermittent but frequent after: Lock → unlock device S
1
0
902
Jan ’26
C function in library code gets stripped when distributed
This is a continuation of https://developer.apple.com/forums/thread/795348 I rambled too much and did not understand the underlaying problem. The problem is that I have a C function in a iOS library. I want to call this C function from a dylib that this library loads on runtime. When running directly from Xcode (either in debug or release mode) this works correctly. However, when the app is uploaded to testflight or distributed for debugging then the function is stripped and a null function pointer exception crashes the app. In the last post it was really hard to explain and I was pressed on time but I've created a minimal reproducible example: https://github.com/ospfranco/dylib_crash The instructions to run and reproduce the crash are on the README.
2
0
664
Jan ’26
Hardware Memory Tag (MIE) enforcement outside of debugger
(Xcode 26.2, iPhone 17 Pro) I can't seem to get hardware tag checks to work in an app launched without the special Hardware Memory Tagging diagnostics. In other words, I have been unable to reproduce the crash example at 6:40 in Apple's video Secure your app with Memory Integrity Enforcement. When I write a heap overflow or a UAF, it is picked up perfectly provided I enable the Hardware Memory Tagging feature under Scheme Diagnostics. If I instead add the Enhanced Security capability with the memory-tagging related entitlements: I'm seeing distinct memory tags being assigned in pointers returned by malloc (without the capability, this is not the case) Tag mismatches are not being caught or enforced, regardless of soft mode The behaviour is the same whether I launch from Xcode without Hardware Memory Tagging, or if I launch the app by tapping it on launchpad. In case it was related to debug builds, I also tried creating an ad hoc IPA and it didn't make any difference. I realise there's a wrinkle here
6
0
1.3k
Jan ’26
Reply to Threading issues when using debugger
We are seeing the same in a SwiftUI runtime. Completely new crash. What version are you running?
Replies
Boosts
Views
Activity
Jan ’26
Reply to Xcode Crashes when viewing XCUITest Result
Hi Kenny, There should be a file in ~/Library/Logs/DiagnosticReports/ that is named something like Xcode-$timestamp.ips - if you can share that then I can check to see if there are known workarounds. Also have you/can you submit a Feedback item with the details of the crash?
Replies
Boosts
Views
Activity
Jan ’26
Reply to macOS 26: NSTokenField crashes due to NSGenericException caused by too many Update Constraints
No reply from Apple and no similar reports in the Feedback app, as usual. I also gave up on updating my feedback with each beta, it's just too frustrating. Instead, I rewrote everything to use strings instead of a custom token type. It requires more parsing passes, but it doesn't crash. Hope this path is also an option for you!
Topic: UI Frameworks SubTopic: AppKit Tags:
Replies
Boosts
Views
Activity
Jan ’26
Crash in swift::_getWitnessTable when passing UITraitBridgedEnvironmentKey
When using UITraitBridgedEnvironmentKey to pass a trait value to the swift environment, it causes a crash when trying to access the value from the environment. The issue seems to be related to how swift uses the UITraitBridgedEnvironmentKey protocol since the crash occurs in swift::_getWitnessTable () from lazy protocol witness table accessor…. It can occur when calling any function that is generic using the UITraitBridgedEnvironmentKey type. I originally encountered the issue when trying to use a UITraitBridgedEnvironmentKey in SwiftUI, but have been able to reproduce the issue with any function with a similar signature. https://developer.apple.com/documentation/swiftui/environmentvalues/subscript(_:)-9zku Steps to Reproduce Requirements for the issue to occur Project with a minimum iOS version of iOS 16 Build the project with Xcode 26 Run on iOS 18 Add the following code to a project and call foo(key: MyCustomTraitKey.self) from anywhere. @available(iOS 17.0, *) func foo(key: K.Type) where
Replies
4
Boosts
0
Views
240
Activity
Jan ’26
Reply to Post-iOS update crash on app launch with split/black screen (Flutter + WebView)
Does this crash generate a crash report? If so, please post an example. See Posting a Crash Report for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jan ’26
startProxy delegate for NETransparentProxyProvider class is being called twice for the same pid extension sometimes
We have an application which is written in Swift, which activates Transparent Proxy network extension. Our Transparent Proxy module is a system extension, which is exposing an app proxy provider interface (We are using NETransparentProxyProvider class and in extension’s Info.plist we use com.apple.networkextension.app-proxy key.) Sometimes we have observed that on starting the transparent proxy extension, the startProxy overridden delegate method(override func startProxy(options: [String : Any]?, completionHandler: @escaping (Error?) -> Void) {) in our AppProxyProvider class which is derived from NETransparentProxyProvider being called more than once for the same extension(pid). This leads to Over-resume of an object crash as we invoke setTunnelNetworkSettings inside the startProxy delegate. As this is controlled by the system, we are not sure why this delegate being called more than once sometimes even if we call the start TransparentProxy only once. Note that, this issue is seen only in Mac OS T
Replies
4
Boosts
0
Views
312
Activity
Jan ’26
Reply to Xcode 26 can no longer launch, and crashes immediately
Hi, there. Sorry you're dealing with this. We're aware of the issue and you can expect a broad fix to make its way into an Xcode near you soon. In the meantime, you can resolve this by removing the local user state for your Xcode Project or Workspace: Quit Xcode (if it's still running, or if another workspace is open). In Finder, find your .xcodeproj file Right-click it > Show Package Contents Navigate to: {project}.xcworkspace → xcuserdata Delete the xcuserdata folder Once you relaunch Xcode, you may need to recreate any user-local state for your project or workspace, but the crash will be gone and you will be able to keep working. Please follow up if you have any further difficulties. Thanks.
Replies
Boosts
Views
Activity
Jan ’26
Xcode 26 can no longer launch, and crashes immediately
Each time I try to launch Xcode 26, it immediately crashes in SourceEditorDataSource.ideChat_gracefullyApplyChangesToReflect. I'm now no longer able to use Xcode. A partial crash log attached. So far I've tried deleting derived data, rebooting, deleting ~/Library/Caches/com.apple.dt.Xcode. What should I do? Thank you in advance for any help. crash-report.txt
Replies
1
Boosts
0
Views
284
Activity
Jan ’26
Swift Playgrounds macOS repeatedly asks “My App would like to access data from other apps”
Environment: Swift Playgrounds (macOS) SwiftUI App Preview macOS version: 26.2 (25C56) Issue: In Swift Playgrounds on macOS, the app repeatedly shows the system permission dialog: “My App would like to access data from other apps. Keeping app data separate makes it easier to manage your privacy and security.” Steps to Reproduce: Create a new SwiftUI app in Swift Playgrounds. Run the SwiftUI App Preview. When the permission dialog appears, click “Allow”. Expected Result: The permission should be granted once and persist, allowing the preview to continue normally. Actual Result: After clicking “Allow”, the SwiftUI App Preview crashes and restarts. When the preview restarts, the same permission dialog appears again. This repeats indefinitely, creating a loop. Notes: This occurs even when no explicit file system or inter-app data access code is written. The permission choice does not appear to persist between preview restarts. Question: Is this a known limitation of Swift Playgrounds sandboxing or SwiftU
Replies
2
Boosts
0
Views
452
Activity
Jan ’26
Reply to C function in library code gets stripped when distributed
Here is a more step by step breakdown of the problem I have a iOS library that exposes a C function. This function is marked with default visibility and used via attribute tags to prevent the compiler/linker from stripping it #ifdef __cplusplus #define DYLIB_EXPORT extern C __attribute__((visibility(default))) __attribute__((used)) #else #define DYLIB_EXPORT __attribute__((visibility(default))) __attribute__((used)) #endif DYLIB_EXPORT bool say_hello_world(); #import helper_functions.h #import bool say_hello_world() { NSLog(@Hello WORLD 🟢!); return true; } From a dynamic library, called sdk, I want to call this function. In this example it's a Rust lib unsafe extern C { fn say_hello_world() -> bool; } #[unsafe(no_mangle)] extern C fn sdk_init() -> i32 { unsafe { say_hello_world(); } return 0; } When the app is compiled and launched from Xcode (either on debug or release schemes) then this works, the following snippet works and prints the hello WORLD message: #import OpacityObjCWrapper.h #import helper
Topic: Programming Languages SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jan ’26
AVCaptureSession preview briefly goes blank after interruption (lock/unlock or camera switch) while isRunning == true
Environment Device: iPhone 15 Pro iOS: iOS 18.0 Framework: AVFoundation App type: Custom camera app using AVCaptureSession + AVCaptureVideoPreviewLayer I’m seeing an intermittent but frequent issue where the camera preview layer briefly flashes empty after certain interruptions, even though the capture session reports itself as running and no errors are emitted. This happens most often after: Locking and unlocking the device Switching cameras (back ↔ front) The issue is not 100% reproducible, but occurs often enough to be noticeable in normal usage. What happens The preview layer briefly flashes as empty (sometimes just a “micro-frame”) Duration: typically ~0.5–2 seconds before frames resume session.isRunning == true throughout No crash, no runtime error, no interruption end failure Focus/exposure restore correctly once frames resume Visually it looks like the preview layer loses frames temporarily, even though the session appears healthy. Repro Intermittent but frequent after: Lock → unlock device S
Replies
1
Boosts
0
Views
902
Activity
Jan ’26
C function in library code gets stripped when distributed
This is a continuation of https://developer.apple.com/forums/thread/795348 I rambled too much and did not understand the underlaying problem. The problem is that I have a C function in a iOS library. I want to call this C function from a dylib that this library loads on runtime. When running directly from Xcode (either in debug or release mode) this works correctly. However, when the app is uploaded to testflight or distributed for debugging then the function is stripped and a null function pointer exception crashes the app. In the last post it was really hard to explain and I was pressed on time but I've created a minimal reproducible example: https://github.com/ospfranco/dylib_crash The instructions to run and reproduce the crash are on the README.
Replies
2
Boosts
0
Views
664
Activity
Jan ’26
Reply to iOS 26 WKWebView STScreenTimeConfigurationObserver KVO Crash
One more, all crash is happening in iOS 26.1.0 and iPadOS 26.1.0
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Jan ’26
Hardware Memory Tag (MIE) enforcement outside of debugger
(Xcode 26.2, iPhone 17 Pro) I can't seem to get hardware tag checks to work in an app launched without the special Hardware Memory Tagging diagnostics. In other words, I have been unable to reproduce the crash example at 6:40 in Apple's video Secure your app with Memory Integrity Enforcement. When I write a heap overflow or a UAF, it is picked up perfectly provided I enable the Hardware Memory Tagging feature under Scheme Diagnostics. If I instead add the Enhanced Security capability with the memory-tagging related entitlements: I'm seeing distinct memory tags being assigned in pointers returned by malloc (without the capability, this is not the case) Tag mismatches are not being caught or enforced, regardless of soft mode The behaviour is the same whether I launch from Xcode without Hardware Memory Tagging, or if I launch the app by tapping it on launchpad. In case it was related to debug builds, I also tried creating an ad hoc IPA and it didn't make any difference. I realise there's a wrinkle here
Replies
6
Boosts
0
Views
1.3k
Activity
Jan ’26
Reply to iOS 26 WKWebView STScreenTimeConfigurationObserver KVO Crash
I have same problem, and crash count is groving because users update iOS
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Jan ’26