Post

Replies

Boosts

Views

Activity

Sunsetting an auto-renewable subscription with no way to reach existing subscribers
We have auto-renewable subscription products that we no longer want to offer going forward. Since there is no per-IAP "Remove from Sale" option anymore in App Store Connect, we disabled availability for this subscription in all storefronts/territories. As expected, this stops new purchases, but existing active subscribers keep renewing exactly as before. App Store Server Notifications continue to send regular DID_RENEW events for this product, with autoRenewStatus: 1. That part matches the documented behavior, so this isn't a bug report. Our actual problem is that we have no way to reach these subscribers directly (the app doesn't collect email or any contact info at purchase time, purchases are tied only to the App Store account), so we can't ask them to cancel manually, and there's no server-side API for a developer to end an existing subscriber's auto-renewal on our own. I already went through the standard support contact form and only received a generic pointer to the subscriptions help article, which doesn't cover this specific situation. Is there any supported mechanism via App Store Connect, the App Store Server API, or a specific Apple Support escalation path to: Notify active subscribers of a discontinued subscription product, or Have Apple end future renewals for a specific product ID going forward (without affecting the subscriber's ability to keep using what they already paid for in the current period)? To be clear about what we're asking for: subscribers should keep full access through the end of their current, already-paid period, we just want to prevent the next renewal from happening. We are explicitly not asking for any refunds to be issued. Product IDs: YEARLY_847658, MONTHLY_847658, moveto7, moveto8, moveto9 App Store Connect currently shows the products as "Developer Removed from Sales" with all territories deselected. Any pointers like official docs, prior threads, or "this isn't possible, here's the workaround developers use" would be very helpful.
1
2
425
Aug ’26
Seeking Advice on Unjust Review Rejection Due to Existing Identical App
I find myself in a predicament that requires help and advice from you. I have developed an app for the App Store, which has been successfully available for several years and generates revenue through subscriptions. In the past, multiple updates for my app were accepted and released, leading to a positive experience with Apple. However, I recently received a review rejection that presents a significant challenge. The rejection is based on the premise that an identical app already exists in the App Store. Theoretically, this is correct. However, the other app is also from me! The pre-existing identical app was unlawfully published by another developer using my code. This matter has already been legally resolved, and Apple officially confirmed it with Apple ref# APP152466. The other app has been deactivated by Apple and is no longer available in the App Store. Despite this clarification, I received only a cryptic response "We are unable to continue our review of your App Store submission because your app is identical to a previously submitted app, [...], which was involved in an App Store Notices dispute (reference number: APP152466)" to my inquiry regarding the review rejection, without a clear acknowledgment or an explanation that the situation was understood. Subsequently, I attempted to initiate a dispute through the appropriate Apple channel, but after several days, I have yet to receive a response. My primary issue is that I am incurring financial losses due to this ongoing rejection of Apple, even though my app is entirely legitimate and does not violate Apple's guidelines. My expectation is that Apple will recognize the situation, and proceed with the review in the normal way. _But I feel stuck and don't know how to proceed. It looks to me like I am at the mercy of the given system without anyone at Apple seriously looking into my case. _ Hence, I am turning to the developer community for guidance: Does anyone have an idea of what my next logical step should be? Or whom I can contact to professionally resolve this situation with Apple? Any advice or experiences you can share would be greatly appreciated and would go a long way in helping me navigate this difficult situation. Thanks in advance,
3
1
1.6k
Oct ’23
Sunsetting an auto-renewable subscription with no way to reach existing subscribers
We have auto-renewable subscription products that we no longer want to offer going forward. Since there is no per-IAP "Remove from Sale" option anymore in App Store Connect, we disabled availability for this subscription in all storefronts/territories. As expected, this stops new purchases, but existing active subscribers keep renewing exactly as before. App Store Server Notifications continue to send regular DID_RENEW events for this product, with autoRenewStatus: 1. That part matches the documented behavior, so this isn't a bug report. Our actual problem is that we have no way to reach these subscribers directly (the app doesn't collect email or any contact info at purchase time, purchases are tied only to the App Store account), so we can't ask them to cancel manually, and there's no server-side API for a developer to end an existing subscriber's auto-renewal on our own. I already went through the standard support contact form and only received a generic pointer to the subscriptions help article, which doesn't cover this specific situation. Is there any supported mechanism via App Store Connect, the App Store Server API, or a specific Apple Support escalation path to: Notify active subscribers of a discontinued subscription product, or Have Apple end future renewals for a specific product ID going forward (without affecting the subscriber's ability to keep using what they already paid for in the current period)? To be clear about what we're asking for: subscribers should keep full access through the end of their current, already-paid period, we just want to prevent the next renewal from happening. We are explicitly not asking for any refunds to be issued. Product IDs: YEARLY_847658, MONTHLY_847658, moveto7, moveto8, moveto9 App Store Connect currently shows the products as "Developer Removed from Sales" with all territories deselected. Any pointers like official docs, prior threads, or "this isn't possible, here's the workaround developers use" would be very helpful.
Replies
1
Boosts
2
Views
425
Activity
Aug ’26
Seeking Advice on Unjust Review Rejection Due to Existing Identical App
I find myself in a predicament that requires help and advice from you. I have developed an app for the App Store, which has been successfully available for several years and generates revenue through subscriptions. In the past, multiple updates for my app were accepted and released, leading to a positive experience with Apple. However, I recently received a review rejection that presents a significant challenge. The rejection is based on the premise that an identical app already exists in the App Store. Theoretically, this is correct. However, the other app is also from me! The pre-existing identical app was unlawfully published by another developer using my code. This matter has already been legally resolved, and Apple officially confirmed it with Apple ref# APP152466. The other app has been deactivated by Apple and is no longer available in the App Store. Despite this clarification, I received only a cryptic response "We are unable to continue our review of your App Store submission because your app is identical to a previously submitted app, [...], which was involved in an App Store Notices dispute (reference number: APP152466)" to my inquiry regarding the review rejection, without a clear acknowledgment or an explanation that the situation was understood. Subsequently, I attempted to initiate a dispute through the appropriate Apple channel, but after several days, I have yet to receive a response. My primary issue is that I am incurring financial losses due to this ongoing rejection of Apple, even though my app is entirely legitimate and does not violate Apple's guidelines. My expectation is that Apple will recognize the situation, and proceed with the review in the normal way. _But I feel stuck and don't know how to proceed. It looks to me like I am at the mercy of the given system without anyone at Apple seriously looking into my case. _ Hence, I am turning to the developer community for guidance: Does anyone have an idea of what my next logical step should be? Or whom I can contact to professionally resolve this situation with Apple? Any advice or experiences you can share would be greatly appreciated and would go a long way in helping me navigate this difficult situation. Thanks in advance,
Replies
3
Boosts
1
Views
1.6k
Activity
Oct ’23