Billing Problem while subscription renewal.

App & System Services StoreKit Subscriptions In-App Purchase StoreKit

jaybe__ OP

Created Apr ’25

Replies 20

Boosts 15

Views 1.1k

Participants 20

Hello, I'm currently experiencing issues with IAP subscription setup.

The following error appears:

"Billing Problem, There was a problem with your subscription renewal. To resolve, turn on Allow Purchases & Renewals, or leave off to test failed in-app purchase attempts and subscription renewals."

I'm testing with a sandbox account, and automatic subscription renewal is turned on in the sandbox settings.

A notification screen appears at the OS level, and consequently, a DID_FAIL_TO_RENEW error occurs on our payment server.

I cannot determine the cause at all, so I would appreciate your assistance in checking this issue.

Answered by DTS Engineer in 833088022

There was an App Store-Sandbox outage that is now resolved. Please try again and let us know if the issue still persists.

Boost

sue630 OP

Apr ’25

same! for me, it happens only when i apply a promo offer to the renewal

_dydus0x14 OP

Apr ’25

The issue delays releases. Please kindly fix it. Thanks!

NickTesla OP

Apr ’25

I've been testing in-app subscriptions in the Apple Sandbox environment for hours without success. Every attempt results in the same error:

"Billing problem: There was a problem with your subscription renewal."

I initially thought it was a mistake on my end—perhaps a missing step or misconfiguration—but after extensive debugging and testing with multiple sandbox accounts, it seems to be a widespread issue affecting the sandbox environment itself.

Please investigate and resolve this issue, or at least provide official guidance on how to work around it. It's currently impossible to validate automatic renewal flows or proper RevenueCat integration under these conditions.

Thanks in advance.

hideg9 OP

Apr ’25

I just checked and it has been improved.

DTS Engineer OP

Apple

Apr ’25

Accepted Answer

There was an App Store-Sandbox outage that is now resolved. Please try again and let us know if the issue still persists.