Thank you! This is it - the problem was that at https://developer.apple.com/account/resources/identifiers/list → my app, I had to check WeatherKit not just in Capabilities tab, but under App Services as well! During the beta I had only Capabilities checked, and that seemed to work until Friday, when apparently the check for App Services was activated. Everything is working now for me :).

Same here, I have decoded the JWT token and ensured it contains the exact same items as the sample token at https://developer.apple.com/documentation/weatherkitrestapi/request_authentication_for_weatherkit_rest_api { "alg": "ES256", "kid": "ABC123DEFG", "id": "DEF123GHIJ.com.example.weatherkit-client" } { "iss": "DEF123GHIJ", "iat": 1437179036, "exp": 1493298100, "sub": "com.example.weatherkit-client" } The key and service id used to work on friday, and then since then I am getting 403 error for every request. The response from WeatherKit API is like this: {"timestamp":"2022-09-13T07:19:17Z","status":403,"error":"Forbidden","message":"Access Denied","path":"/api/v1/availability/47.87/-94.28"} Reported as FB11495570

Hello, the issue is still happening - here is how it looks: https://imgur.com/a/LmAAdK5 (Note that all phases of archive have finished, and the running time of build (6+ hours) - usual time is 20-30 minutes for a clean build)

Thank you, looking forward to a fix.

It seems now that even build manually archived on my macbook and uploaded are now stuck on "Processing", so I can't release any new version of app.

Also filed as FB10058545, but I am hoping that maybe I'm just doing something wrong? I tried adding ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES, that didn't help. It seems that the problem is that libswiftCloudKit.dylib inside a simulator is wrongly linked (while other *.dylib in a same folder are binaries, not links.)

Same here, since yesterday.

Same here, all apps in my account.