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.

Filed as FB9484119 with a sample project showing the issue.

The Xcode release notes say that this issue was fixed in beta 3. It definitely was not - just tried building on the just-released beta 5 and am still seeing the same thing with 3,500 warnings in my project.

Filed as FB9452624.

The same thing was happening to me on beta 3. The time-sensitive tag wasn't getting applied to my notifications until I restarted my phone. Spent over an hour trying different things to get it to work 🤦‍♂️