I enabled the WeatherKit capability on my App ID (com.saimcan.darkweather, Team 6SWSD6V4ZC) about 12 hours ago. The entitlement is embedded in the binary and the provisioning profile authorizes it, but every request fails at the JWT generation step.
Error from the logs:
Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 "(null)"
Relevant log excerpt (iOS 26.4 Simulator, same result on a physical device):
[AuthService] Calling process is 3rd party process and has the correct entitlement ... accepting the connection
[AuthService] Received proxy request for generating a jwt token. url=https://weatherkit.apple.com
[WeatherDataService] Starting to generate JWT token request. bundleIdentifier=com.saimcan.darkweather
[AuthService] Signed successfully
[WeatherDataService] Make new JWT token request. requestIdentifier=...
[AuthService] Failed to generate jwt token ... Code=2
What I have verified:
- Active Apple Developer Program membership (renewed through April 2027)
- All agreements accepted
- WeatherKit capability enabled on the App ID
codesign -d --entitlementsconfirmscom.apple.developer.weatherkitin the built binaryembedded.mobileprovisionalso includescom.apple.developer.weatherkit- App Group (group.com.saimcan.darkweather.shared) correctly bound to both the app and widget App IDs
Since "Signed successfully" is logged, the device-side auth plumbing is working. The rejection appears to be server-side. Could someone from the WeatherKit team check whether JWT minting is enabled for this Team ID / Bundle ID?
Team ID: 6SWSD6V4ZC Bundle ID: com.saimcan.darkweather