Search results for

DID_FAIL_TO_RENEW

33 results found

Post

Replies

Boosts

Views

Activity

Reply to missing unified_receipt in server notifications
Here are more examples of the complete notification body received affected by this bug, I only filtered some data with [Filtered] keyword: { auto_renew_product_id: [Filtered], auto_renew_status: true, bid: [Filtered], bvrs: [Filtered], environment: PROD, notification_type: INITIAL_BUY, password: [Filtered] } { auto_renew_product_id: [Filtered], auto_renew_status: false, auto_renew_status_change_date: 2021-07-15 14:10:14 Etc/GMT, auto_renew_status_change_date_ms: 1626358214000, auto_renew_status_change_date_pst: 2021-07-15 07:10:14 America/Los_Angeles, bid: [Filtered], bvrs: [Filtered], environment: PROD, notification_type: DID_CHANGE_RENEWAL_STATUS, password: [Filtered] } { auto_renew_product_id: [Filtered], auto_renew_status: false, auto_renew_status_change_date: 2021-07-15 10:48:29 Etc/GMT, auto_renew_status_change_date_ms: 1626346109000, auto_renew_status_change_date_pst: 2021-07-15 03:48:29 America/Los_Angeles, bid: [Filtered], bvrs: [Filtered], environment: PROD, notification_type: DID_CHANGE_RENEWAL_STA
Topic: App Store Distribution & Marketing SubTopic: General Tags:
Jul ’21
Unexpected notificationType in App Store Server Notifications V2 when free trial ends
In my app’s IAP products, before enabling free trials, the App Store Server Notifications V2 callbacks all returned the correct notificationType. For auto-renewable subscriptions, when they were about to expire, the notificationType was either DID_RENEW or EXPIRED. A small number of cases(DID_FAIL_TO_RENEW) failed to renew due to billing issues, which was expected. However, after I enabled a 7-day free trial for the auto-renewable products, I noticed that in the App Store Server Notifications V2 callbacks, almost all users (except those who manually turned off auto-renewal) received notificationType = DID_FAIL_TO_RENEW. According to the documentation, DID_FAIL_TO_RENEW indicates a billing issue renewal failure, but in this case it seems like all renewals are being marked as failed. I’ve observed that for users who cancel during the free trial, the callbacks look normal: first a DID_CHANGE_RENEWAL_STATUS notification, then an EXPIRED notification when the trial ends. That flow seems
Topic: App & System Services SubTopic: StoreKit Tags:
3
0
78
3d
v2 server notifications meaning (renewal & grace)
I received the following notifications (in this order) for the subscription: date, type, subtype 2023-10-09 10:49:17,SUBSCRIBED,INITIAL_BUY 2023-10-16 03:46:44,DID_CHANGE_RENEWAL_STATUS,AUTO_RENEW_DISABLED 2023-10-16 10:49:19,DID_FAIL_TO_RENEW,GRACE_PERIOD 2023-10-16 13:14:36,EXPIRED,BILLING_RETRY What do these mean? Why is there a DID_FAIL_TO_RENEW GRACE_PERIOD notification when the user already disabled auto-renew? Why did it expire in 2.5 hours? Why isn't there a GRACE_PERIOD_EXPIRED notification?
Topic: App & System Services SubTopic: StoreKit Tags:
1
0
692
Oct ’23
Testing In App Purchase Server to Server Notifications Sandbox
I have been testing server to server notifications but I am not sure of getting the following notifications on sandbox. I have enabled the grace period on my app store connect account but how to fall the billing to be failed to renew and test grace period concept. Can any one help me on the actions to be performed for getting following notifications on Sandbox? 1, DID_CHANGE_RENEWAL_STATUS -> AUTO_RENEW_ENABLED, AUTO_RENEW_DISABLED 2, EXPIRED -> BILLING_RETRY 3, GRACE_PERIOD_EXPIRED 4, DID_FAIL_TO_RENEW -> GRACE_PERIOD 5, DID_RECOVER 6, REVOKE
Topic: App & System Services SubTopic: StoreKit Tags:
2
0
1.9k
Mar ’22
AppStore Server Notification sent a different type from the real one
Recently I got CS. The customer paid for a subscription renewal but he didn't get a benefit from the subscription. I looked up for server notification logs and saw the latest server notification type was did_fail_to_renew. Also, i requested a transaction history from AppStore Server API(GET https://api.storekit.itunes.apple.com/inApps/v1/history/{originalTransactionId}). The auto_renewable_subscription_purchase was successfully purchased. I don't know why AppStore sent the wrong notification type. Can you answer the question? Thanks
Topic: App & System Services SubTopic: StoreKit Tags:
2
0
736
Apr ’23
Can sandbox renew subscription now?
I tried multi sandbox account and read this post: https://forums.developer.apple.com/thread/130456We have the same problem for some accounts: DID_FAIL_TO_RENEW and the expiration_intent = 4 (The product was not available for purchase at the time of renewal.)While if we tried a new account or simply buy the goods manually, it works and gives us a new transaction id.Because of the experience, I can't test the auto subscription. I read the document and it said the transaction id is unique for buying and renewal, but I never see new transaction-id except manually buy.Is it a regular performance?
Topic: App & System Services SubTopic: StoreKit Tags:
0
0
510
Mar ’20
Billing Problem while subscription renewal.
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.
Topic: App & System Services SubTopic: StoreKit Tags:
20
0
1.1k
Apr ’25
Server Notification for Auto Renewal
When does Apple plan to support a server notification for when a subscription auto renews? Best I can tell from the documentation and online articles there doesn't appear to be a notification type for this scenario. There are notifications when a renewal fails because of billing issues (ie DID_FAIL_TO_RENEW), when a previously expired subscription gets renewed (ie DID_RECOVER), and when a user interactively triggers a renewal (ie INTERACTIVE_RENEWAL). But nothing for when a user transitions from say a trial to an automatic renewal. Seems like a pretty big gap for a subscription-based notification system.
Topic: App & System Services SubTopic: StoreKit Tags:
0
0
519
May ’20
App Store Server Notification Issue
Hello, I am writing this because the behavior of the App Store Server Notification that our server receives is problematic in the Sandbox environment. I have two questions in total. When purchasing a Free Trial subscription, after receiving the SUBSCRIBED / INITAL_BUY Notification, DID_RENEW should be sent when it expires, but DID_FAIL_TO_RENEW/GRACE_PERIOD is sent. The EXPIRE Notification is sent after the subscription expires or DID_CHANGE_RENEWAL_STATUS/AUTO_RENEW_DISABLED is sent, but it does not arrive. The first problem is that I recently heard that automatic payments after a free trial require the user's consent via email. Is this the reason? If so, I am curious about how I can test it in the Sandbox environment. Is the second problem a bug?
Topic: App & System Services SubTopic: Notifications Tags:
0
0
100
Apr ’25
Status notification reception transition
We received a notification DID_FAIL_TO_RENEW(subtype:(Empty)) from App Store when the subscription failed to renew because of a billing issue. After this case, we predict that we will receive the notifications based on the following two cases. If the user resolves a billing issue: Receives notification DID_RENEW(subtype:(BILLING_RECOVERY)) If the user does not resolve the billing issue and cancels the subscription: Receives notification EXPIRED(subtype:BILLING_RETRY) Based on the above， I would like to ask two questions Are the above two cases and the notification types we expected correct? If wrong, please tell me what is wrong. If there are other than the above two cases, please tell me the case and notification type.
Topic: App & System Services SubTopic: StoreKit Tags:
0
0
570
Mar ’24
How to test server-to-server (S2S) notifications
I don't know how Apple expects us to verify that the code that handles server-to-server notifications is working correctly. I can't think of how to test that the full cycle of operation is correct, because I don't want to test the code directly in production, and in the sandbox not all notifications are handled. For example, I don't know how to simulate that a user asks AppleCare to revoke a subscription. On the other hand, in the test purchases I have made I have received DID_RECOVER notifications, which are not supposed to be available (as indicated in https://developer.apple.com/documentation/appstoreservernotifications/notification_type#3694879 ), but also the DID_RECOVER is not preceded by a notification of failure to charge (DID_FAIL_TO_RENEW). Does anyone have any suggestions on how to test? Thank you very much, Oscar
Topic: App Store Distribution & Marketing SubTopic: General Tags:
1
0
1.2k
Apr ’21
Handling grace periods for failed service-level downgrades
I'll preface by saying I'm very new to working with Apple subscriptions and my question is probably quite silly, but I can't find any information on this topic. What I am currently stumped about is the handling of grace periods for service-level downgrades that have experienced billing failure. As an example, the user wants to downgrade from Product B to Product A. The products are in different service levels and have different durations, so the downgrade is scheduled for the next renewal. When that time comes, billing fails and our server receives a DID_FAIL_TO_RENEW notification. How should such a case be handled? If a grace period is in place, should that grace period apply to the original subscription (to Product B), the new subscription (to Product A) or both? Thanks in advance
Topic: App Store Distribution & Marketing SubTopic: General Tags:
0
0
580
Jan ’21
Subscription status mismatch
Hi, some day ago I got these webhook events for a subscription: 2024-01-06 10:40:47 SUBSCRIBED subtype INITIAL_BUY 2024-01-20 03:02:29 DID_RENEW subtype BILLING_RECOVERY 2024-01-20 03:52:08 DID_CHANGE_RENEWAL_STATUS subtype AUTO_RENEW_DISABLED 2024-01-20 10:41:03 DID_FAIL_TO_RENEW (no subtype was received) When I get the subscription status form appstore server API, status is 1 (active). We don't have grace period enabled in our app. I'm not sure how to interpret this result; from our perspective we should remove access to the user.
Topic: App & System Services SubTopic: StoreKit Tags:
3
0
1k
Jan ’24
Connection between isInBillingRetryPeriod and gracePeriodExpiresDate
Hi. We have recently switched to server notification V2. Based on this documentation (notificationType): If the subtype is GRACE_PERIOD, continue to provide service through the grace period. If the subtype is empty, the subscription isn’t in a grace period and you can stop providing the subscription service. Also, base on another documentation (StoreKit): Throughout the billing grace period, the value of isInBillingRetry is true, which indicates that Apple is attempting to automatically renew the subscription. Now, I'm receiving DID_FAIL_TO_RENEW server notification with GRACE_PERIOD subtype where gracePeriodExpiresDate is in the future, but isInBillingRetryPeriod is false (additional note: user has been in trial period and now must be charged as trial has ended). The question is: Is this situation a valid Grace Period even if user is not in billing retry period? And if yes, please elaborate why this is the case. Thank you!
Topic: App & System Services SubTopic: StoreKit Tags:
3
0
955
Apr ’24