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.

And now I just got this myself at my home location.

I was just able to reproduce this using the following request: /v1/weather/en-US/41.925/-87.64?dataSets=currentWeather,forecastNextHour,forecastHourly,forecastDaily Tried again a little later and it worked just fine.

It seems to always be the same users, but I even tried having them go through a proxy server and they are still getting the error. Whenever I try the same request for the same location, though, it loads just fine. So I'm not really sure what's going on. Here's one of their requests in case it helps: /v1/weather/en-US/42.047/-96.163?dataSets=currentWeather,forecastNextHour,forecastHourly,forecastDaily And I submitted this as FB11577100 in case you need the ticket for internal tracking purposes.

The API limits definitely haven't been exceeded - I have subscribed for 2m calls per month and have used just 40k of them so far. And calls from other users are going through just fine.

I am seeing the same thing. Works fine without using a token, gives an error when the token is included.

I'm seeing the same thing for the Modular Duo face now on the Series 7.

Same issue here. I did just notice that one of my alternate icons had an extra pixel in height, so I'm going to see if that fixes the warnings on next submission, but I wouldn't be surprised if that was just a coincidence.

I just realized this isn't happening solely with Intents-related code. I had added a little Swift file so that my Obj-C code could call out to the new Swift-only AppStore class that lets you open the subscription management screen in-app - the auto-generated Swift bridge has a bunch of nullability warnings for that code as well.

Very strange that this works just fine when adding the image to a UIImageView, but using the exact same image in drawRect does not. Using hierarchical or multicolor symbols in drawRect works as well, just not the palette images.