Overview I could use some help understanding app versioning for standalone watchOS apps. I'll outline my scenario first, then list my questions. Scenario In Xcode 15, when creating a new standalone watch app called Foobar, Xcode automatically creates some targets for me: Foobar, Foobar Watch App, and two test targets. My goal is to set/increment the app version and build number. When I open the Foobar Watch App target in Xcode, I set the Version and Build number in the General tab to 1.2.3 and 45, respectively. However, when I archive the app, it doesn't use the versions I set: instead, using the default 1.0 (1). The same verison is set when uploading to TestFlight. The only way I have been able to set/increment the app version for an archive is to modify the Foobar target --> Build Settings --> Versioning. Questions I am wondering a few things: Why does Xcode pick the Foobar target version rather than the Foobar Watch App target for a standalone watch app? (I couldn't find documentation around this behavior) The Foobar target's General tab does not list the Identity section, which is normally where I'd expect to set that information. Why would I need to set this information in the Build Settings tab? Since Xcode picks the Foobar target for versioning, what does the watch target version do? Should I ever increment it for my standalone app? Are there any suggested ways to adjust the app version for a standalone watch app? - For example, can I use a variable to keep both app targets in sync?

I would like to create a custom gesture event trigger for my XCUITests. Is there any way I can review the source for the existing functions such as tap()? I couldn't find any source code for extensions like these. Does anyone know if it is public? And has anyone generated a new custom gesture event?