Hi Quinn — I'm hitting this exact Code=2 failure, but in my case it looks team-level rather than a single stuck App ID. Team ID: Q2UJCHMHJ7. In-app WeatherKit (WeatherService.shared.weather(for:)), physical iPhone 14 Pro. The difference from the original poster: I tested TWO App IDs on my team — com.newtendrelstudios.KazeDiorama (WeatherKit enabled since July 12) and a fresh com.newtendrelstudios.KazeWeather — and BOTH fail with Code=2. I also ran Apple's own sample ("Fetching weather forecasts with WeatherKit," WWDC22 10003), signed with my team and App ID, reduced to a single weather(for:) call, and it fails identically — so it's not my code. Verified on my side: entitlement com.apple.developer.weatherkit is present in the provisioning profile and in the signed on-device binary (codesign -d --entitlements -); WeatherKit enabled under both Capabilities and App Services, persists across login; App ID Prefix equals the Team ID; membership active; reproduced on cellular with no VPN/Private Relay/custom DNS. Since even a fresh App ID on this team fails (unlike the sibling that worked here), I suspect a stuck WeatherKit auth-service registration at the team level for Q2UJCHMHJ7. Could you check whether JWT minting is provisioned server-side for this Team ID? I also have Developer Support case 102947846095 open on this, and I've filed FB23939578 with the full details (including a sysdiagnose). Happy to provide logs, identifiers, or a screen recording. Thanks!