Search results for

“LLDB crash”

30,527 results found

Post

Replies

Boosts

Views

Activity

Reply to MacOS 26 TestFlight SIGKILLs app when updating
First off, one other question I should have asked earlier— what does the crash log you're getting from the SIGKILL actually show? Is it just random state (whatever your app happened to be doing at the time)? Or does it show a pattern, particularly anything tied to your app’s own quit cycle? One possibility that I didn't cover here is that your app IS getting 'quit', but something is going wrong and stalling things long enough that the system kills you. I see, so quit AppleEvent is kinda like the Windows WM_QUIT message. Yes, except WM_QUIT is like the 'quit', since the AppleEvent came first. Yes, AppleEvents are that old. We definitely will file a bug. Bug number? In the meantime, the documentation for Sudden Termination says it's for shutdown. Unfortunately, the phrasing in our documentation is using trickier wording that it really should. Here's what it actually says: macOS 10.6 and later includes a mechanism that allows the system to log out or shut down more qu
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Dec ’25
LLDB Cannot Load ODBC Driver Due to Sandbox Restrictions - How to Debug
I'm developing a macOS console application that uses ODBC to connect to PostgreSQL. The application works fine when run normally, but fails to load the ODBC driver when debugging with LLDB(under root works fine as well). Error Details When running the application through LLDB, I get this sandbox denial in the system log (via log stream): Error 0x0 0 0 kernel: (Sandbox) Sandbox: logd_helper(587) deny(1) file-read-data /opt/homebrew/lib/psqlodbcw.so The application cannot access the PostgreSQL ODBC driver located at /opt/homebrew/lib/psqlodbcw.so(also tried copy to /usr/local/lib/...). Environment macOS Version: Latest Sequoia LLDB: Using LLDB from Xcode 16.3 (/Applications/Xcode16.3.app/Contents/Developer/usr/bin/lldb) ODBC Driver: PostgreSQL ODBC driver installed via Homebrew Code Signing: Application is signed with Apple Development certificate What is the recommended approach for debugging applications that need to load dynamic libraries? Are there specific entit
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
1
0
312
Sep ’25
Reply to [Resolved] App crashes when launched from dock, doesn't crash when run from terminal
Comically, my app does not crash when run from lldb or even when attached to lldb. Curious. This rules out most environmental issues. If you launch the app from Finder (or Dock, those are equivalent) it runs in the standard environment, and attaching with LLDB doesn’t change that.Two things:Please post a full crash report. Use the <> button to format it as code.Can you get a core dump? macOS does not enable core dumps by default but you can enable them from your app by running the following code at startup:struct rlimit limit; BOOL success = getrlimit(RLIMIT_CORE, &limit) >= 0; assert(success); limit.rlim_cur = limit.rlim_max; success = setrlimit(RLIMIT_CORE, &limit) >= 0; assert(success); Note It seems that, out of the box, 10.15 sets the permissions on /cores/ to drwxr-xr-x. For an app (not running as root) to generate a core this must be drwxrwxrwt. You can change this as follows: % sudo chmod 1777 /cores Don’t forget to change it back when y
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jan ’20
Reply to Any easy explanation about how Model I/O works combined wiht Scenekit?
I downloaded this and testing it on XCode 9 Beta, and seems to always crash on me. With this error message:Assertion failed: ([url isKindOfClass:NSURL.class]), function -[AAPLSceneViewController voxelize:], file /Users/justme/Documents/_DEVELOPMENT/VoxelPandaGettingStartedwithVoxelsUsingModelIOandSceneKit/VoxelPanda/VoxelPanda/AAPLSceneViewController.m, line 79.(lldb)Maybe my MacBookPro is too old?
Topic: Graphics & Games SubTopic: SceneKit Tags:
Aug ’17
Reply to I set AVVideoCodecTypeAppleProRes4444 and I get a AVVideoCodecTypeH264 movie
I have just discovered the cause of the trouble. If I added a soundtrack to the movie, the 4444ProRes codec unexpectedly turned into an H.264 codec. So, I have just replaced [[AVAssetExportSession alloc] initWithAsset:videoAudioComposition presetName:AVAssetExportPresetHighestQuality]; with [[AVAssetExportSession alloc] initWithAsset:videoAudioComposition presetName:AVAssetExportPresetAppleProRes4444LPCM]; and now it works well. I can quite get a movie with 4444 ProRes codec and the audio tracks. The only point I miss now is that the AVAssetExportPresetAppleProRes4444LPCM is available on macOS 10.15+. Which preset could I use on macOS 10.13 ?
Topic: Media Technologies SubTopic: Video Tags:
Jan ’21
LLDB plugin fails to load on new XCode - apparent library validation issues
The .NET Runtime has shipped an lldb extension that looks to extend LLDB functionality to be able to reason about .NET managed code. This has been working for a long time, but now it fails to load with the error error: this file does not represent a loadable dylib. Loading works if I use a self-compiled version of LLDB. I can't really debug XCode's LLDB, but there are some logs that seemed to hint it was signing checks failing for library validation, but neither Developer nor Application signing would satisfy these. LLDB resides within the XCode bundle at /Applications/Xcode.app/Contents/Developer/usr/bin/lldb. codesign confirms that the bundle enforces library validation. Is there any way to confirm this is the issue? It looks like: Library Validation failed: Rejecting '/*/libsosplugin.dylib' (Team ID: none, platform: no) for process 'lldb(77691)' (Team ID: none, platform: yes), reason: mapped file has no Team ID and is not a platform binary (sig
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3
0
1.4k
May ’23
Multiple crash reports when running new app on Xcode 12 simulator
I create a new app in Xcode 12 and when I simulate the app on iphone Sim, Xcode doesn't crash but these are the errors I get each time I run the simulator... CalendarWidgetAppExtension quit unexpectedly. parsecd quit unexpectedly. healthappd quit unexpectedly. NewsTag quit unexpectedly. NewsToday2 quit unexpectedly. bulletindistributord quit unexpectedly. ProtectedCloudKeySyncing quit unexpectedly. ...all in succession. Anybody know how to fix this? Thanks in advanced...
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3
0
3.2k
Oct ’20
Reply to SwiftUI Tutorial Application Alleged Incompatibility with macOS
Thanks for taking a look. It was Section 2, Step 4, having typed in the 'struct LandmarkRow_Previews ...' code that the problem occurred. I have re-opened the project and selected LandmarkRow view. The preview canvas states 'Preview paused'. Clicking the refresh arrow again throws the error Landmarks quit unexpectedly. Upon clicking 'Reopen', get You can't use this version of the application Landmarks with this version of macOS. I think I'd better try the tutorial again from scratch.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Sep ’22
LLDB is invoking Xcode to display source code all of a sudden. How to switch back?
I've cross posted this at https://stackoverflow.com/q/79647300/6230282 Basically, I use command line and emacs app to develop on daily basis, but all of a sudden, LLDB is invoking Xcode to display source code for me, instead of printing them in command line. How do I switch back? Or alternatively, can I set a custom editor for LLDB? (lldb) version lldb-1700.0.9.502 Apple Swift version 6.1.2 (swiftlang-6.1.2.1.2 clang-1700.0.13.5) About Xcode: Version 16.4 (16F6)
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1
0
182
Jun ’25
Unable to properly attach to executable with lldb running under Rosetta
I'm trying to attach with lldb to a x64 process running under Rosetta, attachment itself succeeded but lldb is unable to load target neither it's modules. And getting this output: (lldb) process attach --pid 20586 Process 20586 stopped * thread #1, stop reason = signal SIGSTOP frame #0: 0x00007ff813a1d1ee -> 0x7ff813a1d1ee: jae 0x7ff813a1d1f8 0x7ff813a1d1f0: movq %rax, %rdi 0x7ff813a1d1f3: jmp 0x7ff813a18cdb 0x7ff813a1d1f8: retq Target 0: (No executable module.) stopped. Architecture set to: x86_64-apple-macosx-. (lldb) target modules list error: the target has no associated executable images A few weeks ago I had the same problem, but some combination of actions like rebuilding deleting and redownloading binaries and some other unknown magic fixed this behaviour. And today I stumbled upon this problem again, and same actions does not make any effect. Attaching to process works in general (event to processes running under Rosetta), but this specific process I want to deb
Topic: Developer Tools & Services SubTopic: General Tags:
2
0
1.5k
Jul ’23
Reply to NSDocument doesn't autosave last changes
I tried this implementation to autosave changes before quitting the app, but it doesn't work since NSDocument.hasUnautosavedChanges is unexpectedly false. I now get the impression that perhaps a document would be saved automatically before quitting, but there is an issue with how NSTextView marks a document as edited. I would appreciate any insight into this issue. func applicationShouldTerminate(_ sender: NSApplication) -> NSApplication.TerminateReply { let edited = documents.filter({ $0.hasUnautosavedChanges }) if edited.isEmpty { return .terminateNow } var remaining = edited.count for document in edited { document.autosave(withImplicitCancellability: false) { [self] error in if let error = error { presentError(error) } else { remaining -= 1 if remaining == 0 { NSApp.reply(toApplicationShouldTerminate: true) } } } } return .terminateLater }
Topic: UI Frameworks SubTopic: AppKit Tags:
Sep ’25
Reply to Debugger lldb-mi no longer present?
It seems that lldb-mi is no longer part of the main LLDB project. See this announcement. Xcode does not use lldb-mi itself — it was only included in the Xcode distribution as a side effect of including LLDB proper — and thus this change means lldb-mi no longer ships with Xcode. If you need lldb-mi you can build it yourself based on the open source repository. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Nov ’19
Reply to Execution was interrupted, reason: internal ObjC exception breakpoint(-10)..
Can't show the exact code.As the break point hit the function, I am trying to change its parameter value in debug pane like below: (lldb) po someVar ABC (lldb) expression self.someVar = XYZ () $R4 = {} (lldb) po self.someVar XYZ (lldb) po methodName(with: self.someVar) error: Execution was interrupted, reason: internal ObjC exception breakpoint(-10).. The process has been returned to the state before expression evaluation. (lldb)
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Feb ’21
Reply to Establishing stable multi peer data transfer with Network framework
Yeah that was my feeling as well. I don't know how one would go about debugging that, or how I could get it in a symbolicated form. In Xcode when your app crashes, lldb should come up in the console and you can type bt into the console and this will give you the symbolicated trace of the crashing thread. If this happened on the device then you will need to get the crash logs from the device, so see this article here. But if I add both cases to my set of connections to monitor, this never happens. Well done debugging and finding this missing case. Matt Eaton DTS Engineering, CoreOS meaton3@apple.com
Topic: App & System Services SubTopic: Networking Tags:
Aug ’21
XCode Popup error - LLDB provided no error string
Hi all, Whenever I am trying to build my app on IOS and attach it to a Simulator. The build is getting succeeded but whenever the app is starting to launch on simulator, it is throwing a pop up error - LLDB provided no error string The following error in the popup - Could not launch “XX” Domain: IDEDebugSessionErrorDomain Code: 3 Failure Reason: LLDB provided no error string. User Info: { DVTErrorCreationDateKey = 2024-07-22 04:47:11 +0000; DVTRadarComponentKey = 855031; IDERunOperationFailingWorker = DBGLLDBLauncher; RawUnderlyingErrorMessage = LLDB provided no error string.; } Additionally in the console, this is printed in red in console - Logging Error: Failed to initialize logging system. Log messages may be missing. If this issue persists, try setting IDEPreferLogStreaming=YES in the active scheme actions environment variables. I have tried all things - like restarting Xcode, restarting my Mac, cleaning up my workspace and trying to build again, but nothing helps. I have even
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1
0
802
Jul ’24
Reply to MacOS 26 TestFlight SIGKILLs app when updating
First off, one other question I should have asked earlier— what does the crash log you're getting from the SIGKILL actually show? Is it just random state (whatever your app happened to be doing at the time)? Or does it show a pattern, particularly anything tied to your app’s own quit cycle? One possibility that I didn't cover here is that your app IS getting 'quit', but something is going wrong and stalling things long enough that the system kills you. I see, so quit AppleEvent is kinda like the Windows WM_QUIT message. Yes, except WM_QUIT is like the 'quit', since the AppleEvent came first. Yes, AppleEvents are that old. We definitely will file a bug. Bug number? In the meantime, the documentation for Sudden Termination says it's for shutdown. Unfortunately, the phrasing in our documentation is using trickier wording that it really should. Here's what it actually says: macOS 10.6 and later includes a mechanism that allows the system to log out or shut down more qu
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Replies
Boosts
Views
Activity
Dec ’25
LLDB Cannot Load ODBC Driver Due to Sandbox Restrictions - How to Debug
I'm developing a macOS console application that uses ODBC to connect to PostgreSQL. The application works fine when run normally, but fails to load the ODBC driver when debugging with LLDB(under root works fine as well). Error Details When running the application through LLDB, I get this sandbox denial in the system log (via log stream): Error 0x0 0 0 kernel: (Sandbox) Sandbox: logd_helper(587) deny(1) file-read-data /opt/homebrew/lib/psqlodbcw.so The application cannot access the PostgreSQL ODBC driver located at /opt/homebrew/lib/psqlodbcw.so(also tried copy to /usr/local/lib/...). Environment macOS Version: Latest Sequoia LLDB: Using LLDB from Xcode 16.3 (/Applications/Xcode16.3.app/Contents/Developer/usr/bin/lldb) ODBC Driver: PostgreSQL ODBC driver installed via Homebrew Code Signing: Application is signed with Apple Development certificate What is the recommended approach for debugging applications that need to load dynamic libraries? Are there specific entit
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Replies
1
Boosts
0
Views
312
Activity
Sep ’25
Reply to [Resolved] App crashes when launched from dock, doesn't crash when run from terminal
Comically, my app does not crash when run from lldb or even when attached to lldb. Curious. This rules out most environmental issues. If you launch the app from Finder (or Dock, those are equivalent) it runs in the standard environment, and attaching with LLDB doesn’t change that.Two things:Please post a full crash report. Use the <> button to format it as code.Can you get a core dump? macOS does not enable core dumps by default but you can enable them from your app by running the following code at startup:struct rlimit limit; BOOL success = getrlimit(RLIMIT_CORE, &limit) >= 0; assert(success); limit.rlim_cur = limit.rlim_max; success = setrlimit(RLIMIT_CORE, &limit) >= 0; assert(success); Note It seems that, out of the box, 10.15 sets the permissions on /cores/ to drwxr-xr-x. For an app (not running as root) to generate a core this must be drwxrwxrwt. You can change this as follows: % sudo chmod 1777 /cores Don’t forget to change it back when y
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jan ’20
Reply to Any easy explanation about how Model I/O works combined wiht Scenekit?
I downloaded this and testing it on XCode 9 Beta, and seems to always crash on me. With this error message:Assertion failed: ([url isKindOfClass:NSURL.class]), function -[AAPLSceneViewController voxelize:], file /Users/justme/Documents/_DEVELOPMENT/VoxelPandaGettingStartedwithVoxelsUsingModelIOandSceneKit/VoxelPanda/VoxelPanda/AAPLSceneViewController.m, line 79.(lldb)Maybe my MacBookPro is too old?
Topic: Graphics & Games SubTopic: SceneKit Tags:
Replies
Boosts
Views
Activity
Aug ’17
Reply to I set AVVideoCodecTypeAppleProRes4444 and I get a AVVideoCodecTypeH264 movie
I have just discovered the cause of the trouble. If I added a soundtrack to the movie, the 4444ProRes codec unexpectedly turned into an H.264 codec. So, I have just replaced [[AVAssetExportSession alloc] initWithAsset:videoAudioComposition presetName:AVAssetExportPresetHighestQuality]; with [[AVAssetExportSession alloc] initWithAsset:videoAudioComposition presetName:AVAssetExportPresetAppleProRes4444LPCM]; and now it works well. I can quite get a movie with 4444 ProRes codec and the audio tracks. The only point I miss now is that the AVAssetExportPresetAppleProRes4444LPCM is available on macOS 10.15+. Which preset could I use on macOS 10.13 ?
Topic: Media Technologies SubTopic: Video Tags:
Replies
Boosts
Views
Activity
Jan ’21
LLDB plugin fails to load on new XCode - apparent library validation issues
The .NET Runtime has shipped an lldb extension that looks to extend LLDB functionality to be able to reason about .NET managed code. This has been working for a long time, but now it fails to load with the error error: this file does not represent a loadable dylib. Loading works if I use a self-compiled version of LLDB. I can't really debug XCode's LLDB, but there are some logs that seemed to hint it was signing checks failing for library validation, but neither Developer nor Application signing would satisfy these. LLDB resides within the XCode bundle at /Applications/Xcode.app/Contents/Developer/usr/bin/lldb. codesign confirms that the bundle enforces library validation. Is there any way to confirm this is the issue? It looks like: Library Validation failed: Rejecting '/*/libsosplugin.dylib' (Team ID: none, platform: no) for process 'lldb(77691)' (Team ID: none, platform: yes), reason: mapped file has no Team ID and is not a platform binary (sig
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
3
Boosts
0
Views
1.4k
Activity
May ’23
Multiple crash reports when running new app on Xcode 12 simulator
I create a new app in Xcode 12 and when I simulate the app on iphone Sim, Xcode doesn't crash but these are the errors I get each time I run the simulator... CalendarWidgetAppExtension quit unexpectedly. parsecd quit unexpectedly. healthappd quit unexpectedly. NewsTag quit unexpectedly. NewsToday2 quit unexpectedly. bulletindistributord quit unexpectedly. ProtectedCloudKeySyncing quit unexpectedly. ...all in succession. Anybody know how to fix this? Thanks in advanced...
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
3
Boosts
0
Views
3.2k
Activity
Oct ’20
Reply to SwiftUI Tutorial Application Alleged Incompatibility with macOS
Thanks for taking a look. It was Section 2, Step 4, having typed in the 'struct LandmarkRow_Previews ...' code that the problem occurred. I have re-opened the project and selected LandmarkRow view. The preview canvas states 'Preview paused'. Clicking the refresh arrow again throws the error Landmarks quit unexpectedly. Upon clicking 'Reopen', get You can't use this version of the application Landmarks with this version of macOS. I think I'd better try the tutorial again from scratch.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Sep ’22
LLDB is invoking Xcode to display source code all of a sudden. How to switch back?
I've cross posted this at https://stackoverflow.com/q/79647300/6230282 Basically, I use command line and emacs app to develop on daily basis, but all of a sudden, LLDB is invoking Xcode to display source code for me, instead of printing them in command line. How do I switch back? Or alternatively, can I set a custom editor for LLDB? (lldb) version lldb-1700.0.9.502 Apple Swift version 6.1.2 (swiftlang-6.1.2.1.2 clang-1700.0.13.5) About Xcode: Version 16.4 (16F6)
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
1
Boosts
0
Views
182
Activity
Jun ’25
Unable to properly attach to executable with lldb running under Rosetta
I'm trying to attach with lldb to a x64 process running under Rosetta, attachment itself succeeded but lldb is unable to load target neither it's modules. And getting this output: (lldb) process attach --pid 20586 Process 20586 stopped * thread #1, stop reason = signal SIGSTOP frame #0: 0x00007ff813a1d1ee -> 0x7ff813a1d1ee: jae 0x7ff813a1d1f8 0x7ff813a1d1f0: movq %rax, %rdi 0x7ff813a1d1f3: jmp 0x7ff813a18cdb 0x7ff813a1d1f8: retq Target 0: (No executable module.) stopped. Architecture set to: x86_64-apple-macosx-. (lldb) target modules list error: the target has no associated executable images A few weeks ago I had the same problem, but some combination of actions like rebuilding deleting and redownloading binaries and some other unknown magic fixed this behaviour. And today I stumbled upon this problem again, and same actions does not make any effect. Attaching to process works in general (event to processes running under Rosetta), but this specific process I want to deb
Topic: Developer Tools & Services SubTopic: General Tags:
Replies
2
Boosts
0
Views
1.5k
Activity
Jul ’23
Reply to NSDocument doesn't autosave last changes
I tried this implementation to autosave changes before quitting the app, but it doesn't work since NSDocument.hasUnautosavedChanges is unexpectedly false. I now get the impression that perhaps a document would be saved automatically before quitting, but there is an issue with how NSTextView marks a document as edited. I would appreciate any insight into this issue. func applicationShouldTerminate(_ sender: NSApplication) -> NSApplication.TerminateReply { let edited = documents.filter({ $0.hasUnautosavedChanges }) if edited.isEmpty { return .terminateNow } var remaining = edited.count for document in edited { document.autosave(withImplicitCancellability: false) { [self] error in if let error = error { presentError(error) } else { remaining -= 1 if remaining == 0 { NSApp.reply(toApplicationShouldTerminate: true) } } } } return .terminateLater }
Topic: UI Frameworks SubTopic: AppKit Tags:
Replies
Boosts
Views
Activity
Sep ’25
Reply to Debugger lldb-mi no longer present?
It seems that lldb-mi is no longer part of the main LLDB project. See this announcement. Xcode does not use lldb-mi itself — it was only included in the Xcode distribution as a side effect of including LLDB proper — and thus this change means lldb-mi no longer ships with Xcode. If you need lldb-mi you can build it yourself based on the open source repository. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Nov ’19
Reply to Execution was interrupted, reason: internal ObjC exception breakpoint(-10)..
Can't show the exact code.As the break point hit the function, I am trying to change its parameter value in debug pane like below: (lldb) po someVar ABC (lldb) expression self.someVar = XYZ () $R4 = {} (lldb) po self.someVar XYZ (lldb) po methodName(with: self.someVar) error: Execution was interrupted, reason: internal ObjC exception breakpoint(-10).. The process has been returned to the state before expression evaluation. (lldb)
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Feb ’21
Reply to Establishing stable multi peer data transfer with Network framework
Yeah that was my feeling as well. I don't know how one would go about debugging that, or how I could get it in a symbolicated form. In Xcode when your app crashes, lldb should come up in the console and you can type bt into the console and this will give you the symbolicated trace of the crashing thread. If this happened on the device then you will need to get the crash logs from the device, so see this article here. But if I add both cases to my set of connections to monitor, this never happens. Well done debugging and finding this missing case. Matt Eaton DTS Engineering, CoreOS meaton3@apple.com
Topic: App & System Services SubTopic: Networking Tags:
Replies
Boosts
Views
Activity
Aug ’21
XCode Popup error - LLDB provided no error string
Hi all, Whenever I am trying to build my app on IOS and attach it to a Simulator. The build is getting succeeded but whenever the app is starting to launch on simulator, it is throwing a pop up error - LLDB provided no error string The following error in the popup - Could not launch “XX” Domain: IDEDebugSessionErrorDomain Code: 3 Failure Reason: LLDB provided no error string. User Info: { DVTErrorCreationDateKey = 2024-07-22 04:47:11 +0000; DVTRadarComponentKey = 855031; IDERunOperationFailingWorker = DBGLLDBLauncher; RawUnderlyingErrorMessage = LLDB provided no error string.; } Additionally in the console, this is printed in red in console - Logging Error: Failed to initialize logging system. Log messages may be missing. If this issue persists, try setting IDEPreferLogStreaming=YES in the active scheme actions environment variables. I have tried all things - like restarting Xcode, restarting my Mac, cleaning up my workspace and trying to build again, but nothing helps. I have even
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
1
Boosts
0
Views
802
Activity
Jul ’24