XCode Popup error - LLDB provided no error string

Question

Created Jul ’24

Replies 1

Boosts 0

Participants 2

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 tried deleting my Xcode, deleting everything in /Library/Developer and ~/Library/Developer , but this does not solve the issue either.
I have also tried setting up env variables as mentioned in console. IDEPreferLogStreaming = YES . But this does't also help solve the case.

Any guidance to solve this error will be appreciated. TIA !

Boost

Answer 1

Developer Tools Engineer OP

Apple

Aug ’24

Please reproduce the issue, capture a sysdiagnose (on the host, as this affects the simulator), and attach it to a feedback report. The error message ("LLDB provided no error string") is pretty generic and gets shown when we don't have more information about the problem, which makes this hard to diagnose without more information.

If you want to diagnose this issue further yourself, open the Console.app before trying to launch or attach to your app. When it fails, look for log messages from Xcode, LLDB, debugserver, or really any other subsystem that might have been involved in the launch. Often these logs will leave a clue as to what went wrong.

0