We've faced the same problem in Xcode 16. As a workaround, we've added options -add_ast_path to OTHER_LDFLAGS for every framework (our internal and third party). Option template:
-Wl,-add_ast_path,$(TARGET_BUILD_DIR)/\(framework).framework/Modules/\(framework).swiftmodule/$(NATIVE_ARCH_ACTUAL)-$(LLVM_TARGET_TRIPLE_VENDOR)-$(SHALLOW_BUNDLE_TRIPLE).swiftmodule
Solution to a similar problem was described in https://github.com/florentmorin/Xcode13LLDBBug
But this workaround didn't help us eliminate errors type for self cannot be reconstructed in UI test targets. And the origin of the problem isn't clear yet.
And yes, getting LLDB ready on the first breakpoint takes a lo-o-ot of time.
artyom-stv-joom
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
Xcode 16.1. Same error: "Failed to attach to target process", "Failed to acquire memory location for pushing shared memory into target."
Feedback issue: FB15773948.