“DID_FAIL_TO_RENEW”

I'm working in Apple's Sandbox environment to implement in-app purchase of an auto-renewable subscription. I followed the instructions at this link in order to Enable Billing Grace Period: https://developer.apple.com/help/app-store-connect/manage-subscriptions/enable-billing-grace-period-for-auto-renewable-subscriptions. However, when I receive an App Store Server Notification for when the user's billing method fails (DID_FAIL_TO_RENEW), it includes no information about the gracePeriodExpiresDate and we never get a GRACE_PERIOD_EXPIRED notification. Logs showing App Store Server Notification not reflecting Grace Period Enabled. I enabled grace period in App Store Connect like three weeks ago, so it's not a delay there. What can I do to test out Billing Grace Period? Is this just an Apple bug?

Greetings, New to iOS App Store connect - not new to engineering. We have a SaaS offering that we are building an iOS app version of. We are supporting IAP Auto-Renewing Subscription for users that find us through the app store. I am trying to understand the flow of the notifications so that we can effectively maintain subscription state across Web & iOS. Would be great if someone could validate or correct our understanding as follows: User subscribes to monthly auto-renewing subscription. Subscription information passed from app to server. Receipt is validated and transaction_id is stored with the users account. INITIAL_BUY s2s notification is received containing the corresponding transaction_id At this point the subscription is active and we won't receive any other s2s notifications unless the subscription is cancelled / not renewed. At some point in the future, we may receive one of which would indicate that the subscription is inactive and needs attention: CANCEL DID_FAIL_TO_RENEW In addition

Hello, I am currently implementing server-side handling for in-app subscription payments and using App Store Server Notifications V2 to receive notifications with a TestFlight account. However, I am not receiving EXPIRED notifications, although I am successfully receiving other notifications such as SUBSCRIBED, DID_RENEW, and DID_CHANGE_RENEWAL_PREF. Here are some details of my observations: Until a certain point, I was receiving EXPIRED notifications without any issues, but they stopped coming in after that point. Each subscription renews every 3 minutes in TestFlight account, and I receive DID_RENEW notifications 7 to 12 times. According to the official documentation, the subscriptions should renew up to 12 times, but I am not receiving exactly 12 DID_RENEW notifications. This inconsistency might be related to the issue. Other notifications (SUBSCRIBED, DID_RENEW, DID_CHANGE_RENEWAL_PREF) are received without any issues. Could anyone provide insight into why this might be happening and suggest any alternati