Fixed in Xcode beta 5, which released a day after iOS beta 5.

Waiting on this as well.

That worked! Do you know which result type opens a URL? I couldn't find one.

I'm unable to get the app to open with OpenIntent, even when my ControlWidgetButton's class is added to both the main app and the extension targets. What code did you use to get that to work?

Ah, I just figured out how to do this, but it's only on watchOS 11 and iOS 18 unfortunately - .widgetAccentedRenderingMode(.desaturated)

I'm seeing the same thing in WidgetKit on iOS 18. I wonder if this is a bug in WidgetKit, as I can't imagine this is working as intended. Are you doing this on watchOS 11? What's the behavior on watchOS 10?

In the last month or so (probably since the release of iOS 17.2), I've started getting a lot of reports of users losing all their NSUserDefaults as well. I never had a problem with the prewarming stuff from iOS 15 - this is a completely new issue. Has anyone else been experiencing anything like this on iOS 17? @eskimo - have there been any recent changes to iOS that might affected NSUserDefaults?

How did you manage to archive a build for visionOS? When I archive, it seems to always archive just the iOS version, even though I've added visionOS as a supported destination. When I try to archive for the visionOS simulator, it says "invalid run destination".

This appears to be fixed in the 10.1 beta.

I ran into this same issue as well. If you update your project to migrate to a single WatchKit target, you should be able to force immediate updates again. Be warned though, the migration introduced a bunch of build errors into my project that took a couple hours for me to fix, and there are other bugs that you will run into that are specific to a single target watch app: ClockKit complications will break and need to be reinstalled, and location updates will fail if you delete then reinstall your watch app. Quite a mess.

I am seeing this error all the time now when trying to test purchases on the sandbox. I'm using StoreKit 1. Only started happening in the last few weeks.

Any chance this is fixed in watchOS 10.0.1?

I am seeing the same error. Have you filed a feedback with Apple yet?

I'm seeing the same thing when trying to output speech to a buffer via writeUtterance:toBufferCallback.

Yes, this just started happening for me as well.