Just to give a clearer picture of what I’m observing. FYI, notifications are triggered based on the user’s selected UV index threshold. Here’s an example timeline: Alert at 8:30 AM – “UV index near 4 between 9:30 AM and 5:00 PM. Peak: 4” Alert at 11:30 AM – “UPDATED: UV index near 4 and above between 9:30 AM and 3:30 PM. Peak: 5” Alert at 2:15 PM – “UPDATED: UV index near 4 between 9:30 AM and 5:00 PM. Peak: 4” Alert at 2:30 PM – “UPDATED: UV index near 4 and above between 9:30 AM and 3:30 PM. Peak: 5” It is as if Apple Weather pulls from two alternating weather services. If anyone has insights into why the forecast keeps toggling like this, I’d appreciate the explanation.

More details, this is what the error is: Failed to generate jwt token for: com.apple.weatherkit.authservice with error: Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 "(null) Couldn't read values in CFPrefsPlistSource<0x1294c0f00> (Domain: group.com.darkMatter.SafeTan, User: kCFPreferencesAnyUser, ByHost: Yes, Container: (null), Contents Need Refresh: Yes): Using kCFPreferencesAnyUser with a container is only allowed for System Containers, detaching from cfprefsd Again, this is just for a few select devices 🤔

More insights. Turns out my Apple Developer certificate expired today and was reissued, which must have triggered a regeneration of provisioning profiles and entitlements. Even though the entitlements are now correctly set in Xcode, the updated entitlement data may not have fully propagated to some of my iPhones that are configured in Developer Mode, especially the ones I haven’t rebooted or reinstalled the app on since the change. Other devices without Developer Mode enabled are still working fine. That's my hypothesis.

For what it’s worth, I’m experiencing a similar issue, but only on certain devices. The one thing they have in common is that they show the Beta Updates option under Software Update. Aside from that, everything else is consistent, including the fact that they’re all running the latest iOS 18.5. Interestingly, my Apple Developer certificate expired and was renewed around the same time I started seeing the error. Like the original poster, all entitlements, capabilities, and certificates are correctly configured. This setup was working fine before, and there haven’t been any code changes related to WeatherKit. Here's my post that may be related to this: https://developer.apple.com/forums/thread/788811

I've written to Apple today, there is a growing number of developers reporting the same issue on the forum. It’s clear that this needs Apple's attention and investigation. Many apps, including mine, rely heavily on Apple Weather. Just today, I received a one-star review, likely due to the app's inability to retrieve the UV index forecast. These are all the recent threads with related topics, including this one: 789157, 789900, 789564,789319,786126,788811

@DTS Engineer - Thank you! Although when I am clicking on the link, it brings me back to this thread. Can you repost the link please?

No worries and thank you!

My thoughts: In my view, Apple may want to reconsider how it interprets users force-quitting apps. Closing an app from the App Switcher isn’t necessarily a sign that the user dislikes it or finds it unhelpful. Many users simply prefer to keep the switcher uncluttered. A force-quit app can still serve an important purpose, and because Apple has not clearly communicated how background behavior works after a manual terminate, many apps are unintentionally penalized by this misunderstanding. Users already have better tools for signaling preference, such as disabling notifications. Ultimately, deleting an app is the only meaningful indication that a user truly does not want it. Just my two cents.

My thoughts: In my view, Apple may want to reconsider how it interprets users force-quitting apps. Closing an app from the App Switcher isn’t necessarily a sign that the user dislikes it or finds it unhelpful. Many users simply prefer to keep the switcher uncluttered. A force-quit app can still serve an important purpose, and because Apple has not clearly communicated how background behavior works after a manual terminate, many apps are unintentionally penalized by this misunderstanding. Users already have better tools for signaling preference, such as disabling notifications. Ultimately, deleting an app is the only meaningful indication that a user truly does not want it. Just my two cents.

Thank you!

Thank you @DTS Engineer !