What's most unbelievable is the absolute disdain and contempt Apple shows to developers by not acknowledging what the developer experience with this API is like, offering their sincere apologies for what they are putting independent developers through, tell us of their plans for fixing it, etc. At this point, if you're using the API, you should absolutely have a fallback weather source in place.

This problem continues. Today, in Miami, FL the heat indices are over 100, but WeatherKit is reporting it just a couple degrees over actual temperature. At the same time, the NWS is issuing an alert "WHAT...Heat index values between 105 to 107 this afternoon and then again on Thursday." WeatherKit apparent temperatures are basically the same as the actual temperature. Something isn't right here.

An answer would be nice. As the OP said, the API is available and there is information from Apple on how to make (some) calls and encouraging developers to do so. Is V2 ready for production use?

Has this just been in the last two days (about 8/26/25)?