Increased StoreKit errors “Unable to Complete Request”

Question

Created Jan ’26

Replies 3

Boosts 1

Participants 4

Since January 28, 2026, we’ve noticed an increase in StoreKit-related errors during purchase flows.

Specifically, we’re seeing a spike in errors reported as “Unable to Complete Request”, categorized as unknown StoreKit errors. This correlates with a noticeable drop in the overall purchase success rate.

A few observations:

The issue is not limited to the latest app version, it also affects older versions.

It appears to occur only on iOS 17+.

The impact seems country-specific: some regions are affected more heavily, while others show no significant change compared to previous days.

At the moment, there are no related incidents reported on Apple’s System Status page.

Given these symptoms, this looks like a potential StoreKit / Apple API issue, but we haven’t found any official confirmation yet.

Has anyone else observed similar StoreKit behavior recently on iOS 17+? Any insights or known issues would be greatly appreciated.

Answer 1

jeffctown OP

Feb ’26

We’re seeing this as well.

Starting January 28, 2026, our StoreKit1 purchase flows began showing a sudden spike in error codes, primarily:

ASDErrorDomain Code=500
With an underlying AMSErrorDomain Code=301

Answer 2

App Store Commerce Engineer OP

Apple

Apr ’26

Please file a feedback assistant ticket with whatever info/trend you have noticed (e.g. geo and iOS version breakdown) and the Apple ID of your app.

Thank you

Answer 3

chenglinque OP

1w

Adding another data point. Our production app (StoreKit 2, Product.purchase() called directly on device, no purchase controller) hit the same 'Unable to Complete Request' failures at very high rates from July 27, 2026 20:34 UTC to July 28, 2026 about 07:00 UTC. Roughly 95% of purchase attempts failed at the payment sheet: overnight we saw 43 attempts with only 1 completion, versus a stable 25-36% completion rate on every prior day. App Store Connect server reporting confirms the drop, so it was not a client-side telemetry artifact.

Observations that match this thread:

Nothing changed on our side: same binary throughout, no product or configuration changes, and it recovered on its own with no action from us.
Server-side subscription renewals continued normally through the whole window; only interactive purchases failed.
Product metadata loaded normally the entire time (no product load failures).
Failures spanned all products, all storefronts, and iOS 18.x and 26.5.x devices identically (so not tied to an OS release).
A small fraction of attempts (roughly 5-8%) still completed, so intermittent rather than hard-down.
We also saw a short burst of the same error on July 26 22:52-23:31 UTC, overlapping Apple's acknowledged App Store In-App Purchases incident that evening; the July 27-28 window itself shows no status page entry.

We filed a support case with full details and timestamps: Case ID 20000122298182. If an Apple engineer can correlate the window above server-side, we are happy to provide transaction-level logs.