Generally, you would add a new Target to the iOS project. Then you can share code that is common to both targets, and have other code files that are target-specific. In shared code files, it is possible to mark code as applying only to a specific platform.

It might be cleaner to have the action take place in the view you are navigating to, using .onAppear?

My first thought is that Apple may be unlikely to approve something called "Bonjourr", since they already have a technology called "Bonjour".

Do you have a question?

Did you make any progress on this, @modern?

Is your cube virtual, or real (like this one, at Boughton House)? Have you looked at "Tracking Geographic Locations in AR"? https://developer.apple.com/documentation/arkit/content_anchors/tracking_geographic_locations_in_ar

In a SwiftUI ForEach, each item must be uniquely Identifiable. In your ForEach, you use the "id" parameter, to specify how to uniquely identify each item... ForEach(clothimages, id: \.self) If your items are not unique (they are not!), then they will not display correctly. This is how ForEach works. In your clothimages, it is the image name that must be unique, for the ForEach to work. Update clothimages, so that all image names are unique. To print text below your images, try: func maincustom(content: Image, text: String) -> some View { VStack { content .resizable() .frame(width: 200, height: 250) Text(text) } .padding(8) }

For your next question, please try pasting your code into a code block (using "Paste and Match Style"), instead of using screenshots.

Apple say: "...the split view controller is typically the root view controller of your app’s window." typically... so it doesn't have to be. Alternatively, can't you just set your rootViewController in code (based on some condition, where the app supports SplitViewController)? if supportsSplitViewController { appDelegate?.window??.rootViewController = splitViewController } else { // something else... }

Apple provides several Sign in with Apple buttons... see: https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple/overview/buttons/

It's an interesting idea. I like the Touch Bar... ...but since Apple have removed it from the latest MacBook Pros, I think they are unlikely to bring it back (or anything like your version) in the near future.

Works for me... ...make sure you have the Console visible, and not just the Variables View (which uses the same space, and can sometimes hide the Console)

You have not defined "aspectRatio"

I would say that if the documentation does not specify a thread, then any thread can be used, as long as UI updates take place on the main thread.

To remove an app from sale: From the App Store Connect website... go to the page for the app go to "Pricing and Availability" click "Remove from sale" click "Save"