I am getting the same error, this started last night. I am using "RevenueCat SDK" and it was working fine. Now I get that message. I can't seem to find anywhere that would show if Sandbox is up and running or if its down..
jhoannarango
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Hollywood, FL
Post
Replies
Boosts
Views
Activity
I second that, it works with some colors such as red, but when I use white it won't change, it has that grey looking color that I want to get rid of, it does not go at all with the design of my app.
Hi, were you able to figure out what happened ? I am having the same issue.
On the only scenario that you can use Stripe, would be if your app sells physical goods. Subscriptions, digital goods and everything else has to be done through Apples in app purchases.
When saving to user defaults, you can set different values by using different keys. For example.
UserDefaults.current.set(value: true, forKey:”myKey”)
And you use said key to retrieve the value. Using different keys for different values will give
you the results you are looking for.
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"))
So it's the simulator the problem? Everything actually points to the simulator as the cause of this issue...
I am having this issue in both the iOS 17 Simulator and on my device running iOS 17 Beta.
Hopefully next betas fix this issue.