It looks like the Form is being vertically centred in the view. What happens if you embed the Form inside a VStack or ZStack, and set the alignment to the top?

You can't have transparent icons, so the system uses black.

Raise a bug.

Why not just have the app call a script on your servers when a user submits a form in the app? The script can email you.

Is there anything on this page that might help? https: // useyourloaf.com/blog/button-configuration-in-ios-15/

Surely that's up to you? If your app is a credit card app and the user has asked to close their account, you wouldn't want them spending on the card, right? Does your business model allow a user to continue to do something while their account is being deleted. Deletion should be atomic - their account is useable, then it isn't. It's up to you to decide whether you block the account while it's being deleted, or not.

I haven't ever written any C++ on the Mac, but I think you can write it in Xcode. To be honest, though you might have strengths in Windows GUI programming, mainly just the ideas of how GUIs work on an OS is useful. You should prepare yourself for learning how things work on the Mac. We have UIKit, but that's Objective-C and Swift. You might find it handy to start writing stuff in Objective-C or Swift and see how that works out for you. Swift is going to be supported going forward (and Objective-C for a good long time yet). Check out some of the sample code projects on Apple's website (look for the WWDC 2022 stuff). You can gain a lot of knowledge by trying their stuff out and changing things to see how things work. Good luck.

You put it inside the struct but not inside var body: some View: struct ContentView: View { @State var another = false   var body: some View {     if(another) {       AnotherView()     } else {       ContentView()     } } }

I get the same issues, see here. They sometimes work on the Simulator, but most of the time they don't. And they're not working properly at all on a physical Watch.

A List shows a row for each item you supply, in a single column: List { Text("A List Item") Text("A Second List Item") Text("A Third List Item") } Because the example is using a list of Landmark objects, they have to be Identifiable, so there's an id parameter for each one. The syntax is saying: Go through each item in the set of Landmark objects: landmarks Create a variable we can refer to when we're using each one: landmark Add a row using the LandmarkRow view, and supply the current landmark to that view so the view can use the data. In Xcode if you put your cursor onto a variable, you'll see where else that variable is used, so if you click on landmark on the first line of code you shared, it would be highlighted in the second line, too: List(landmarks, id: \.id) { >->->landmark<-<-< in LandmarkRow(landmark: >->->landmark<-<-<) }

Apple's videos rarely give you all the info required :( Take a look at this post. The big green image shows my project structure. I have my complications in a separate target which the Watch App embeds: Main App (embeds Widget, Widget Intents Handler and Watch App) Widget Widget Intents Handler Watch App (embeds Complications and Complications Intents Handler) Complications (new, copy of Widget, but altered to target watchOS) Complications Intents Handler If you look in your list of targets (click the blue project icon at the top of the project list), the icon on the Complications one needs to be a circle because it's being deployed to the Watch. Mine didn't work when the icon was a square, because it was inadvertently being targeted to iOS. Go to the Build Settings tab for the Complications target and make sure the Base SDK is watchOS. When you change anything in the project structure, Xcode gets a bit angry and will gift you a ton of errors. I'd backup your existing project and work on a copy. Let me know how you get on.

This isn't a developer problem, and you should really use the normal support forums. However, have you tried removing the widget and re-adding it?

It's a circle. Apple might add an .accessorySquare widget in future, but they haven't yet, so just work with the widget as it is. That being said, raise a feedback request in the usual way and maybe they'll add it.

Jeez. Your phone does exactly what it did before. Maybe there isn't enough space to see the percentage? Maybe it's just a bug. Who knows? But coming on here to the Developer forums to grumble about it is just weird.

Right, well, after having consulted the vast swathes of info on this (there is none), I've come to the conclusion that I must be doing something wrong since other developers have released apps with complications and widgets that work. Even the code that worked on iOS 15 doesn't work on iOS 16, so this is going to take forever. Sorry, customers! No updates for you yet.