Luis Padron

Some more debugging: Looks like `XCTSourceCodeFrame` contains the address and symbol info, when i print the `XCTSourceCodeFrame.symbolicationError` instance variable I see: ``` Symbolication Error: Error Domain=XCTSymbolicationServiceErrorDomain Code=6 "Unable to get...

Planning on implementing this when I get some free time, if someone would prefer to take this up let me know!

Nice! @adincebic you can take a look at: https://github.com/MobileNativeFoundation/rules_xcodeproj/pull/2785 and https://github.com/MobileNativeFoundation/rules_xcodeproj/pull/2866 which implemented a similar change to the schemes API. @brentleyjones if you have other suggestions to get them started

As a workaround for now: using `_XCAppClipURL` as an environment variable in the run section of the App Clip scheme still works in Xcode 15.x. The scheme UI in Xcode...

Using the following lock for `swift-system`: ```json { "identity" : "swift-system", "kind" : "remoteSourceControl", "location" : "https://github.com/apple/swift-system.git", "state" : { "revision" : "f9266c85189c2751589a50ea5aec72799797e471", "version" : "1.3.0" } }, ```

Workaround was to delete _all_ caches, including our Bazel disk cache

@BalestraPatrick Yeah we have that all setup (correctly i hope). The command line builds are fine its just when generating the project that we see the failure.

The one thing we did which i think caused other build failures (and forced us to use our `action_env` cache buster) was we moved our `Tools/Rules` directory which contained all...

We had another engineer report the same error (different target). They reported deleting a target and then trying to generate a project. I don't believe an Xcode change was involved...

An engineer just reported this again, should we reopen? It's not immediately obvious what's causing this but clearing out caches seems to fix this