We are seeing consistent 502 BAD GATEWAY errors from Weatherkit. Looking over the stack trace we see Connection refused: weatherkit.apple.com/23.45.233.25:443.
This doesn't happen to all of our requests so it seams like one of the WeatherKit IP addresses has some issues.
Any one else effected by this?
Often the exact same request will go through on retry.
I can testify with this. The exact same request may fail or go through randomly. Out of 5 request we get this error at least 2 times.
Today is the last day we can use DarkSky. It's going to render my app useless for weather, affecting all my current users.
This is the error I get when debugging:
[WeatherService] Encountered an error when fetching weather data subset; location=<+26.07166672,-80.14969635> +/- 0.00m (speed -1.00 mps / course -1.00) @ 3/31/23, 2:02:14 PM Eastern Daylight Time, error=responseFailed(<NSHTTPURLResponse: 0x600001f05ce0> { URL: https://weather-data.apple.com/v3/weather/en/26.072/-80.150?timezone=America/New_York&dataSets=currentWeather,forecastHourly,forecastDaily&hourlyStart=2023-03-31T18:02:14Z&hourlyEnd=2023-04-01T18:02:14Z&country=US } { Status Code: 502, Headers {
"Cache-Control" = (
"max-age=0, no-cache, no-store"
);
Connection = (
"keep-alive"
);
"Content-Length" = (
150
);
"Content-Type" = (
"text/html"
);
Date = (
"Fri, 31 Mar 2023 18:02:15 GMT"
);
Expires = (
"Fri, 31 Mar 2023 18:02:15 GMT"
);
Pragma = (
"no-cache"
);
Server = (
Apple
);
"Strict-Transport-Security" = (
"max-age=31536000; includeSubdomains"
);
"X-Cache" = (
"TCP_MISS from a23-204-105-89.deploy.akamaitechnologies.com (AkamaiGHost/11.0.2.2-47519392) (-)"
);
"X-Content-Type-Options" = (
nosniff
);
"X-Frame-Options" = (
SAMEORIGIN
);
"X-XSS-Protection" = (
"1; mode=block"
);
} }, Optional("<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body>\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>Apple</center>\r\n</body>\r\n</html>\r\n"))
We're experiencing this exact same issue, and it's very negatively affecting our API service. I thought Apple would fix it shortly after shutting down DarkSky, but it's still as bad of a problem, if not worse. I'm currently doing workarounds such as increasing the number of retries, and allowing manual retries as well, but this really needs to be fixed by Apple.
How can we get Apple to prioritize this more highly? It seems like there's been no action taken yet.
-
—
sarkonovich
Add a CommentYes. Many people have posted about this. And 401 and 404. Often the exact same request will go through on retry. This is an issue with the API. It's not ready for production traffic.