Xcode -> Bazel Debugger integration may stop working under certain situations

[jerrymarino]

Currently, we have a few ways to integrate with the debugger that may have fragility, especially in situations like migrating to Bazel. After running a Bazel build for the first time we generate a source map into the home directory.

Confirm if:

• Xcode is able to load this source map consistently and try to mitigate it otherwise
• Switching between Bazel and Xcode is working

[jerrymarino]

This requires a deeper investigation and manual testing to reproduce

The current workaround for this issue is:

• validate that the correct .lldbinit files are inside of ~/: ~/.lldbinit and ~/.lldbinit-tulsiproj
• if the correct LLDB init files aren't there then do a Bazel build
• restart Xcode

[fnazarios]

Hi @jerrymarino. We just finish our implementation with Bazel and XCHammer and we are unable to run the app on a simulator by Xcode. Xcode prompts the message "Could not attach". Does this behavior have any relationship with this issue?