Sorry, took a little bit as i needed to get back to where i could load to a physical device instead of the simulator. But I was able to confirm the error persists. Received authentication failure for request: F0F85280-0C4A-46C6-A947-1AF14B2C3B00 Type: Error | Timestamp: 2026-08-21 07:50:59.827988-07:00 | Process: TripVault | Library: WeatherDaemon | Subsystem: com.apple.weather | Category: WeatherDataService | TID: 0x6205

I appreciate the update nevertheless and the effort/attention. I was able to get weather working on a different app that i'm currently building an update for which is encouraging to know I can get it to work in a real app i've built!

I appreciate the help once again. I just submitted a bug report - FB23888627

Great test — the new project works. WeatherTest (bundle ID com.hof.WeatherTest, same team 634Q7K5DN8) fetched weather successfully on the first try on my physical device: "Success: 82.18°F" for the Jackson Hole coordinates. It worked almost immediately, well within any propagation window. Hopefully this helps isolate it. I believe my code is fine and WeatherKit JWT minting works for my team. The failure is specific to the TripVault App ID (com.davidfrauenhofer.TripVault). That one App ID has failed with Code=2 for several weeks despite both tabs enabled and the entitlement confirmed in the signed binary, while a sibling App ID on the same team works instantly. Since you mentioned TripVault's configuration matches what you see in your internal systems, could there be a stuck or incomplete WeatherKit registration on the backend for that specific App ID? Happy to provide anything else useful.

Figured i'd attach some screenshots too. I appreciate the help!

Thanks Quinn. I have both enabled — WeatherKit is checked under both the Capabilities tab and the App Services tab on the App ID (com.davidfrauenhofer.TripVault, Team 634Q7K5DN8), saved and confirmed. I'd verified this before posting. To rule out the client side entirely, codesign -d --entitlements - on the installed binary confirms com.apple.developer.weatherkit = true, with application-identifier = 634Q7K5DN8.com.davidfrauenhofer.TripVault and matching team-identifier. Fresh provisioning profiles, clean build, deleted/reinstalled on a physical device. App ID Prefix equals the Team ID. This has persisted for several weeks. Given both tabs are enabled and the entitlement is confirmed in the signed binary, is there a way to verify whether JWT minting is actually provisioned server-side for this Team ID / Bundle ID? I'm wondering if there's a stuck or incomplete WeatherKit registration on the backend for this App ID that wouldn't be visible from my side.