I compiled this using Xcode 16RC 16A242 (instead of 15) and it now just about works. In iPadOS 18RC it works perfectly. In iOS 17.6.1 the swipe does not react when started from on top of the button but the showTab2 property does not change either so it remains consistent. It seems this is a problem in Xcode 15 but it has been fixed in Xcode 16 as Sydney 🙏 suggested. PS: 🏆Kudus to Xcode Cloud for making this test so easy to perform. I'd never used it before and it was truly simple to onboard.

(Post obsolete)

Hi Sydney, Xcode Version 15.4 (15F31d) Swift 5 (according to the build settings) I'm surprised, but can't figure yet how to update to 5.1. The code is running on the simulator (iPhone 15) and also iPadOS 18.0 (22A3354) iPad Air and iOS 17.6.1 on an iPhone 13 Pro. I checked all gesture attributes and couldn't find anything dodgy about them. Here's the video: https://youtube.com/shorts/SVlESw5nGX0?si=5JCUgu2iYBCh9Smk Thanks for your interest, Alan

I used Rob the Artist's solution in a different context and it worked perfectly. I was struggling with how to inject a @Namespace in a class that required initialisation into the preview. I'm a newbie so much appreciated the simplicity of the solution. #Preview { struct RectButtonPreview: View { @Namespace var slideLevel var body: some View { RectButtonView(buttonCol: .blue, selected: true) .environment(SlideAnimations(slideLevel: slideLevel)) } } return RectButtonPreview() }

Here's the nub... The scheme does not directly include a reference to the platform used, but it does directly reference the Targets config, which determines the platform used. I had assumed that I select the Target by placing the cursor on the Targets config when building the archive, but this is irrelevant 🤦‍♂️ And the Targets config used is specified in the Builds tab, not the archive tab (where I'd expected it) Such a simple solution - now I finally understand the relation between Targets, Schemes and the builds.

Success! I switched to a different scheme and then the correct destination appeared. I've no idea which of the dip switches was relevant but once I've identified the scheme setting I'll post the answer here.

It is already the target Supported destination. It's also in the included in the project Deployment And it's in the target architecture Just now I added it to the Targeted Device Families for vision OS deployment but that didn't help. There are so many different tabs and settings... is there a way of getting this in xml/json to pinpoint the entry that is missing?

It did indeed. Many thanks!

(the status isn't displayed on the Apple Connect App, so here's a screenshot from the browser)