Okay, without any confirmation from Apple - who have created this artificial limit - I'll just inform my users that Apple are to blame for a degraded experience.

No. As per https://developer.apple.com/download/applications/ "Note: Developing for visionOS requires a Mac with Apple silicon."

If you release an app update that supports iOS 17 and watchOS 10 as a minimum, then the App Store won't offer the upgrade to someone who's iOS device and watchOS device don't match the minimum requirements. So, no, the App Store won't let someone upgrade the main iOS app if the companion watchOS app isn't going to be supported.

You cannot develop apps for visionOS without an Apple Silicon-based Mac. It's that simple. Sorry.

You don't actually state where the error is, but it looks like you're trying to create an object and the the init() method is deprecated, so you need to use the init(configuration:) method instead.

What dates come back in the forecast? Is it tomorrow, t+1, t+2, t+3 and t+4? Or is it tomorrow, t+1, t+2, t+3? Can you print out the response and see what's coming back? Have you tried fiddling with the dates? Maybe try 6 * 24 * 3600?

Here's one way of doing it: struct ContentView: View { var body: some View { if #available(iOS 17, *) { // If iOS 17 or greater is in use, these symbols will be used let kSymbolMedikamente: String = "syringe" let kSymbolBPR: String = "point.bottomleft.forward.to.arrowtriangle.uturn.scurvepath" let kSymbolInvasiveMassnahmen: String = "heart.text.square" } else { // Anything lower than iOS 17 will use these symbols let kSymbolMedikamente: String = "syringe" let kSymbolBPR: String = "point.bottomleft.forward.to.arrowtriangle.uturn.scurvepath" let kSymbolInvasiveMassnahmen: String = "heart.text.square" } TabView { Group { Medikamente() .tabItem { Image(systemName: kSymbolMedikamente) Text("Medikamente") } BPR() .tabItem { Image(systemName: kSymbolBPR) Text("BPR") } InvasiveMassnahmen() .tabItem { Image(systemName: kSymbolInvasiveMassnahmen) Text("Maßnahmen") } } } } }

Where are your Watch complications stored? Are they in a WidgetKit Extension target? When you added the Watch App target to your main iOS app, did you then add a new WidgetKit Extension (watchOS) and select to embed it inside the Watch app? That's what you need to do. If you don't have the complications as a separate extension target, you can easily add a new one and move the code over. I had issues with Xcode always creating iOS extensions rather than watchOS ones, but a reinstall of Xcode fixed it.

When you add your app in App Store Connect, there is a keywords field for you to enter words your app can be found using.

How were you downloading Xcode? If you download it through Safari you can simply press the orange retry button in the downloads window and it picks up where it left off. In my experience the Simulators have always downloaded fine. Seeing as you had to download them a few times to get a full version, why didn't you go to a cafe or somewhere else with free Wi-Fi? You don't explain how the simulator you downloaded isn't "functioning properly" so no one can help you there. Your post isn't really about developing for Apple's operating systems; it's more of a moan that you had to spend time setting things up.

These are the Developer Forums, where developers ask each other for hints and tips on coding. Your question is more of a support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

Ah, hold on. That's a typo. The large one should be kWidgetKind_Large. I've just changed it to that, and now the widget isn't editable. So, I guess that was the issue... Thanks!

We're going to need more info on this. What is the error in the preview view on the right? That little stethoscope symbol will give you more info.

Since you say this is a new view inside an existing project, if you comment out that new code, do you still get the error? I'm just trying to figure out whether it's in this code or some other code, as I've just added your simple code into my project and there are no issues.

Hi @radox1, no I didn't manage to migrate them in the way you suggest. Xcode never offered me that option. Here's how I've done it: Make sure your Home Screen and Lock Screen Widgets are in one iOS WidgetKit Extension target. Add a new watchOS WidgetKit Extension target and ensure you embed it in your Watch App. Put your complications in this new target. You can add code that's shared between targets into a folder at your project's root level, i.e. not within a specific target, and mark those files as available to the appropriate targets. For example, I have a shared functions Swift file that my Complications, Widgets and Watch App can use, and I put my localised strings into that folder, too. Use ConfigurationAppIntents to configure dynamic widgets and complications. The old way of using SiriKit is an annoying nightmare that Apple should never have forced onto us.