invalidJWTResponse Swift API

Hi, I am getting and invalidJWTResponse when using WeatherKit Swift API, I have setup everything correctly including enabling WeatherKit in both Capabilities and App Services, Added WeatherKit" to Xcode Capabilities, and waited for more than one day! But still it's not working!

invalidJWTResponse(Optional(<NSHTTPURLResponse: 0x6000008d8300> { URL: https://weather-data.apple.com/v2/token } { Status Code: 401, Headers {

    Connection =     (

        close

    );

    "Content-Length" =     (

        0

    );

    Date =     (

        "Thu, 09 Jun 2022 18:24:24 GMT"

    );

    Server =     (

        "AppleHttpServer/5712591c84160e0cbbf19c8f434c32ab02f2a7f4"

    );

    "Strict-Transport-Security" =     (

        "max-age=31536000"

    );

    "X-Apple-Origin" =     (

        "01ca7adc-14e8-31f5-9654-4375b40868e2"

    );

    "X-B3-TraceId" =     (

        795fbfea426330d9

    );

    "X-Cache" =     (

        "TCP_MISS from a88-221-161-85.deploy.akamaitechnologies.com (AkamaiGHost/10.8.2-41841244) (-)"

    );

    "X-REQUEST-ID" =     (

        "3e6d21c8-ffa0-4c56-aa91-8466619a4993"

    );

} }))
Post not yet marked as solved Up vote post of FarouKz Down vote post of FarouKz
830 views

Replies

Same here, I followed all the instructions and waited 24hrs but I still have not had the sample app successfully load any weather data :(

This still doesn't work for me after a week. But I am seeing some posts that it is working for them. Is anybody having success with this?

Hello I'm experiencing the same issues too. How do we resolve this?

What ended up working for me was going back to certificates and identifiers page in developer.apple.com and going to the app id, there are TWO tabs to check WeatherKit on.

My mistake was not checking WeatherKit on both Capabilities AND the App Services page. I had only checked it under Capabilities. I was able to get WeatherKit running in 3 different apps after checking both boxes.

  • Good catch I did same too.

  • I was sure I had missed something, and I did. Once I added this it started working properly. Great catch.

Add a Comment