I'm seeing the same thing on my end. No other changes on my side. Everything in developer portal indicates my keys are active and I have I have decoded and validated JWTs that are being sent. In addition, the Apple Developer Status page (https://developer.apple.com/system-status/) indicates no problems 🤷‍♂️

Should be available here: https://developer.apple.com/account/resources/services/weatherkit

Haven't found that info anywhere in the REST docs... I've been using the same values they provide in the Swift docs for WeatherCondition: https://developer.apple.com/documentation/weatherkit/weathercondition In case it's useful, I put the following Gist together previously based on the docs linked above: https://gist.github.com/mikesprague/048a93b832e2862050356ca233ef4dc1#file-weatherkit-condition-codes-ts

This issue seems to be getting worse, not better. It's clearly on Apple's side, it's well past time for someone on their team to comment. I don't recall ever having this level of instability with the Dark Sky API.

I filed a request through the Feedback app prior to my original posting - and just like this post, it hasn't gotten any response from Apple. This weather alert behavior change, combined with constant instability (401s coming and going), and the other differences (only metric data and loss of summaries to name a couple) have made the experience of switching from Dark Sky very painful. When you add to it that Apple support won't acknowledge or address any of these things, it becomes insulting to the developers that pay membership fees and put their time into using these services.

I would not plan for them to support that. The getting started docs have a whole section related to transitioning from Dark Sky and many fields simply say "none" meaning there is no equivalent and it is not supported. Full list about halfway down this page: https://developer.apple.com/weatherkit/get-started/