If you have quite a lot of simulators and they're all set to show automatically, some will be 'lost'. I think you just need to set "Show run destination" to "Always" for the ones you always want to see, and they should then always be displayed.

Original project written in UIKit: 100% fine, but takes ages to do anything. Rewrite project in SwiftUI: 95% doable natively - and easier than UIKit - with 5% having to be wrapped. I've just rewritten one of my apps in SwiftUI and it was faster to write, easier to write, and it looks nicer. SwiftUI is the future. Sorry you're not 100% satisfied with it, but it's not like you can't use UIViewControllerRepresentable where absolutely necessary. I'd rather have the convenience of SwiftUI and do a little extra leg work here and there, than have to go back to UIKit for 100%. Besides, some of these things will get improved and implemented in SwiftUI as we go on, making it faster and easier. Why not go for it?

This might not be correct, but I remember seeing this somewhere? .navigationTitle("Title") .navigationBarTitleDisplayMode(.large) Something like that?

Look in Xcode's settings, in the "Text Editing" tab. There's a bunch of settings there to indent code, insert closing braces etc.

This sounds very much like an exam question or some homework. This isn't the place for that. You should just learn it for yourself. There are plenty of websites that show you how to write in SwiftUI.

Try a Spacer() after the Form?

Did you write the app? If not, get in touch with the developer and state the versions of software that you're using, including the version of macOS.

Two things: Why? Just use the Developer Forums - as you already have done. Please don't just randomly select some tags to add to a post on here. What does adding an account on X have to do with SSO Extensions and Family Controls? If someone comes here and searches for "Family Controls", your post will come up and it has noting to do with family controls at all. Be better.

What method are you using to send a message between the devices? If you send a message and expect a reply, you have to send a reply. If you send a message and don't want a reply, you don't need to handle replying, but there are two different methods for this: // This method is called when a message is sent *and* a reply was requested func session(_ session: WCSession, didReceiveMessage message: [String: Any], replyHandler: @escaping ([String: Any]) -> Void) { // Do something... replyHandler(["itWorked": true]) // <-- Send a reply } // This method is called when a message is sent and a reply was *not* requested func session(_ session: WCSession, didReceiveMessage message: [String: Any]) { // Do something... } You should also confirm the activation state of the session. If it's not activated and not reachable, you can't use interactive messaging.

Can't really help you with this as you haven't given us an image of what you mean. Also, with the code presented, there's very little to go on. Try commenting out everything except one tab, then do another, and another, until you see the issue. That might help pin down where it is.

We really can't help you with this unless you post some code or tell us what you're actually doing.

Well, you haven't told us where this is from. And you've picked random tags to add to your post - which is extremely annoying for us developers, who use those tags to find relevant information. If you use random tags you pollute the information on here. Please don't do this. Secondly, no, you haven't been hacked.

Let's say you have this data: Brand A with Model 1, Model 2, Model 3 Brand B with Model 1, Model 2 If your state vars are set so that both pickers are at 0, then the Brand picker and Model pickers will both show "Choose". If you were to pick Brand A, the Model picker will show "Choose". If you then select Model 3, you will have Brand A and Model 3 shown in the pickers. At this point, brandIndex == 1 and modelIndex == 3. Now, when you change the Brand picker to Brand B, the Model picker will try to show the model with the tag 3 (modelIndex), and since there isn't a 3, you get that error. How about adding the onChange modifier to the Model picker, too? .onChange(of: brandIndex) { modelIndex = 0 }

I'd really appreciate some help here, guys. Anyone from Apple able to chip in and tell me where I'm going wrong? Other apps have widgets working fine, so I must be screwing this up somehow? Sadly, none of the sample code provided by Apple is of any use. Whatever I try just doesn't work. Sorry to be so negative, but a massive company like Apple should be able to see what's wrong and suggest a fix, surely? Do I have to use one of my support incidents and waste the first 30 minutes confirming my day is going well, thank you very much?

Hi. this isn't really a question for the developer forums. It's more of a product support question, and should really be asked at discussions.apple.com. However, this is how AirDrop works. If you want the photos to appear in your Photos library, add them to your Photos app rather than AirDropping them to the iPad.