I'm not sure, if it's the same problem or not, but I also faced problems with failing swipes in UI tests (in iOS simulator): at least in certain cases (like swipeLeft() to reveal the standard "accessory menu" on a table row), they behave like clicks. I was able to pinpoint it to running x86_64 build of UI tests on M1 (adding ARCHS=x86_64 to xcodebuild arguments). With the very same native build on M1, swipes in UI tests behave as expected. Just in case, I'm reproducing it on Xcode 13.4.1 and iOS simulator for iPhone 8 running iOS 15.2. Will check most recent iOS 15.5 a bit later.

Move your DerivedData to a path that is short enough. E.g. to /tmp. That was a solution that worked for us/seems to be related to paths hard-coded in LC_PATH load commands or something like that (take a look at otool -l <your mach_o executable> output).

I'm not sure whether that's your case or not, but I faced it with Git pre-push hook. The issue was caused by the fact that GIT_DIR was set to the "source" directory, and, as far as I understand, that's something that affects git checkouts that are done during xcodebuild. (It clearly looks like a xcodebuild bug to me, that supposedly does git clone followed by git checkout, with the latter unexpectedly impacted by GIT_DIR). I'm able to reproduce it by doing something like below (with clean DerivedData): env GIT_DIR="$PWD/.git" xcodebuild -disableAutomaticPackageResolution ... The remedy in my case was to unexport GIT_DIR for the invocation of xcodebuild, like below: env -u GIT_DIR xcodebuild -disableAutomaticPackageResolution ... Wondering if something similar happens with GIT_DIR in your setup.

Just to mention it, we observed some problems on iOS 15 and employed the workaround with attaching the view IDs to the views at top level. However, immediately after that we realized that it makes sense even from UX perspective: considering e.g. the case of scrollable section with title, it makes sense to scroll to the section as whole rather to the title of the section, as it makes difference when there's not enough content below the section to scroll it to the top: in that scenario, attaching the id to the section makes the whole section rather just the title scrolled into in the view.