Hi all, We submitted a request to update our organization's legal name on our Apple Developer Program account in early June, about two months ago. It is a simple name change. Our company, D-U-N-S number and account holder are all the same, and the D-U-N-S record has already been updated with the new name. Since then: We've contacted Developer Support over 10 times The replies we get say the request is "being reviewed," with no timeline The old name is still shown as the seller on our App Store listing, which confuses our users and doesn't match our invoices and contracts For comparison, we made the same change with Google Play Console and it was done within 48 hours. We have customers who cant get the latest version. We cant release a new version - and the old one is crashing. We are loosing customer on this. We understand Apple needs to verify legal entity changes, but two months with no update or estimate makes it hard to plan. We have [an app update / a launch / a partnership] that depends on the correct name being shown. Has anyone been through this recently? How long did your organization name change take? Is there a way to escalate a stalled request? Did you have to provide extra documents (business registration certificate, etc.) before it moved forward? Any advice is appreciated, and if someone from Apple sees this, we'd be grateful if you could look at it. Thanks, John

Is there dou mode on App Store like ipad store or Mac store?

We recently received an email about our account suspension but the reason is not clear in the email. We don't know what is the reason behind this and we can't get any response from the Contact page. Email: "This letter serves as notice of termination of the Apple Developer Program License Agreement (the “ADP Agreement”) and the Apple Developer Agreement (the “Developer Agreement”) between you and Apple effective immediately. Pursuant to Section 3.2(f) of the ADP Agreement, you agreed that you would not “commit any act intended to interfere with any of the Apple Software or Services, the intent of this Agreement, or Apple’s business practices including, but not limited to, taking actions that may hinder the performance or intended use of the App Store, Custom App Distribution, TestFlight, Xcode Cloud, Ad Hoc distribution, or the Program…” Apple has good reason to believe that you violated this Section due to documented indications of fraudulent conduct associated with your account."

Hello Apple, I have launched a chess variant game on the App Store, and I have no means in App Store Connect to register it as Chess, I can see other chess games and chess variant games being tagged as Chess in their tags. this one aspect reduces the games footprint in visibility as it is intended for a chess audience and cannot be searched for unless queried directly.

Has anyone successfully appealed an Apple Developer account termination under Section 3.2(f)? My individual developer account (about 50 live apps, all my own work, all revenue through StoreKit subscriptions) was terminated effective August 24, 2026 under Section 3.2(f) of the ADP Agreement. I believe it was triggered by internal tooling I built to automate my own App Store Connect workflow — metadata, build uploads, submissions — only on my own apps. I've filed an appeal through the official form, replied to the termination notice, and written to appstorenotices. For anyone who has been through this: Did your appeal succeed, and how long did Apple take to respond? Was the response you received a form letter or specific? Were you able to recover the withheld balance from legitimate sales, and through what channel? Is there any official channel I've missed beyond the appeal form, the termination-notice reply, and appstorenotices? Any firsthand experience would mean a lot. Thank you.

I am getting rejected from Apple because of subscription groups that I do not use. How do I solve this?

Apple 团队及各位开发者，你们好： 我是一名独立开发者，希望就开发者会员资格终止后的沟通渠道和恢复申请流程获得指引。 我的账号下共有九款 App，其中八款此前已在 App Store 上架。近期发生的情况如下： 2026 年 9 月 11 日： App Store Connect 显示依据《Apple Developer Program 许可协议》第 3.2(f) 条发出的待终止通知，账号下此前上架的 App 被下架。 2026 年 9 月 12 日： 我通过指定的 App Review Board 表单提交申诉。该表单当时最多允许添加五款 App，提交完成页面确认已收到这五款 App 的申诉请求。 2026 年 9 月 14 日： 我陆续在这五款 App 的通讯页面收到回复。每份回复都有不同的申诉编号，但实质内容相同，均表示调查已完成，并维持终止开发者会员资格的决定。 我理解，这些回复涉及的是账户级决定，而不只是某一款 App 的普通审核拒绝。回复同时告知，会员资格正式终止后，可以申请恢复。 目前最困难的是：通知列举了可能涉及的违规行为类别，但没有指出本次认定所依据的具体事例。 例如，我仍不清楚相关认定对应的是哪款 App、哪个版本或 Build、哪项功能、哪段元数据、哪次沟通回复，或哪项账号相关活动。 我对这一结论有异议。我没有故意隐藏功能，也没有设置以规避审核为目的的机制。我愿意提供相关记录，解释可能存在的事实理解偏差，并纠正确认存在的问题。但在缺少具体事例的情况下，很难准备有针对性、可验证的说明和改进计划。 我理解开发者论坛不能代替 App Review Board 处理账户申诉。我不是要求论坛参与者直接撤销决定，也不要求披露内部检测方法、审核人员身份或第三方保密信息。 希望获得以下流程方面的指引： 申诉已有结论后，应通过哪个官方私密渠道请求具体说明？ 我已有 Developer Support 案例，希望了解如何请求足以供我核实、回应和采取改进措施的信息。 在通知没有提供具体事例的情况下，应如何组织恢复申请？ 哪些材料最有助于区分事实澄清、已经完成的改进，以及尚待实施的计划，避免依靠猜测作出不准确的陈述？ 应如何确认正式终止的生效状态，以及何时可以提交恢复申请？ 对于涉及同一账户、分别关联五款 App 的申诉编号，后续请求应如何引用和关联？ 我可以通过 Apple 官方私密支持渠道提供申诉编号、支持案例编号及相关材料，因此没有在公开帖子中列出这些信息。 这件事对我的开发工作影响很大。我希望准确理解实际问题，通过合适的程序提供有针对性的证据，并争取恢复会员资格的机会。 感谢任何关于正确渠道和后续步骤的指引。 Hello Apple team and fellow developers, I am an independent developer seeking guidance on the appropriate communication channel and process for preparing a membership reinstatement request. My account contains nine apps, eight of which had previously been available on the App Store. The timeline is as follows: September 11, 2026: App Store Connect displayed a Pending Termination Notice citing Section 3.2(f) of the Apple Developer Program License Agreement. My previously available apps were removed from the App Store. September 12, 2026: I submitted an appeal through the designated App Review Board form. The form allowed me to add a maximum of five apps at that time, and the confirmation page acknowledged receipt of the appeal request for those five apps. September 14, 2026: I received responses in the communication pages for all five apps. Each response has a different appeal ticket number, but the substantive wording is identical. The responses state that the investigation is complete and maintain the decision to terminate my developer membership. I understand that these responses concern an account-level decision, rather than an ordinary review rejection for an individual app. They also state that I may request reinstatement once the membership is formally terminated. My main difficulty is that the notifications list categories of potentially prohibited conduct without identifying a specific example underlying the finding in my case. I do not know which app, version or build, feature, metadata, communication, or account-related activity led to the decision. I disagree with the conclusion. I have not deliberately hidden functionality or implemented a mechanism intended to evade App Review. I am willing to provide relevant records, address possible factual misunderstandings, and correct any confirmed deficiencies. However, without a specific example, it is difficult to prepare a targeted, verifiable explanation and improvement plan. I understand that the Developer Forums cannot replace the App Review Board’s account appeal process. I am not asking forum participants to overturn the decision or disclose internal detection methods, reviewer identities, or third-party confidential information. I would appreciate guidance on these procedural questions: After an appeal has been decided, which official private channel should I use to request actionable clarification? I already have a Developer Support case and would like to understand how to request enough information to investigate, respond, and take appropriate corrective action. How should a reinstatement petition be organized when the notification does not identify a specific example? What evidence would best distinguish factual clarification, completed improvements, and proposed changes, without relying on speculation or making inaccurate statements? How should I confirm the effective status of formal termination and when I may submit a reinstatement request? How should I reference and associate the five app-specific appeal ticket numbers in a follow-up concerning the same membership? I can provide the appeal references, Developer Support case number, and relevant materials through an official private support channel, so I have not included those details publicly. This decision has significantly affected my development work. My goal is to understand the actual concerns, provide focused evidence through the appropriate process, and seek an opportunity to restore my membership. Thank you for any guidance on the correct channel and next steps.

Since our 1.3.20 update reached users on Sept 11, 2026, a handful of devices terminate at launch right after the App Store auto-update. Restarting the device does not help; deleting the app and reinstalling it from the App Store does. Filed as FB24755993 with 9 crash reports, the delivered package's SC_Info/Manifest.plist and a per-binary fingerprint. What the crash reports say (all identical) Exception Type: EXC_CRASH (SIGABRT) Termination: namespace DYLD, code 1, "Library missing" (terminated at launch; ignore backtrace) Library not loaded: @rpath/FBSDKCoreKit.framework/FBSDKCoreKit Referenced from: <DDB434B7-...> /Volumes/VOLUME/*/Runner.app/Runner Reason: tried: '/private/var/containers/Bundle/Application/<UUID>/Runner.app/Frameworks/FBSDKCoreKit.framework/FBSDKCoreKit' (could not register fairplay decryption, mremap_encrypted() => -1) Backtrace: dyld4::prepare -> dyld4::halt -> abort_with_payload Devices so far: iPhone XR / iOS 18.7.10 (22H374), iPhone 16 / iOS 26.6, iPhone 16 / iOS 18.7.7, plus one more not yet identified. The same package launches normally on the large majority of the ~12,000 devices that updated that day. Delivered Info.plist: DTAppStoreToolsBuild 27A261, DTXcodeBuild 17F113, MinimumOSVersion 15.0. What we established The main executable decrypts fine (dyld reaches dyld4::prepare); the failure is on the first @rpath framework in the load order, which is also the first FairPlay-encrypted embedded binary. It is not specific to the Facebook SDK. The package Apple delivers (pulled with Apple Configurator) is structurally consistent: every binary with LC_ENCRYPTION_INFO_64 has cryptid 1 and SC_Info/<name>.supp/.supf/.supx/.v4.supp/.v5.supf (main executable, App, Flutter, FBSDKCoreKit, FBAEMKit, FBSDKCoreKit_Basics, objective_c, sqlite3, the widget appex); the Firebase/Google frameworks are cryptid 0. SC_Info/Manifest.plist has SinfPaths = [SC_Info/Runner.sinf] and SinfReplicationPaths for all 12 binaries. Only the main Runner.sinf ships; the framework-level .sinf files have to be produced at install time from SinfReplicationPaths. The symptom looks like that replication not being applied to the frameworks after the delta update on the affected devices, while a fresh full install performs it. Nothing in our bundle changed between 1.3.19 and 1.3.20 except Dart code (App.framework): same Xcode 26.6 (17F113), same Flutter engine, byte-identical Facebook SDK 18.1.1 binaries (the only fat arm64+arm64e binaries in the bundle), same Firebase SDK. Both versions run normally from TestFlight and Xcode. The 1.3.20 encrypted variant carries SC_Info timestamps about 18 h after Ready for Sale, coinciding with the start of the auto-update wave. We could not obtain the delivered 1.3.19 package for comparison. Questions Has anyone seen this class of failure since early September, or with packages processed by DTAppStoreToolsBuild 27A261? Is there anything about a bundle (fat arm64+arm64e embedded frameworks? many encrypted frameworks?) that makes the framework .sinf replication on the delta-update path fragile? Is there any developer-side mitigation other than telling users to delete and reinstall? The closest earlier report I found is thread 718950 (2022, iOS 15.7–16.1, ~1 in 200 installs, "reinstall fixes it"); this looks like the same failure but concentrated on one update. fingerprint-1.3.20.json

I’m looking for advice on App Store positioning for a slightly unusual developer-tool workflow. I have: Reality Prep Pro — macOS Prepares, validates and optimizes spatial assets. Reality Prep Preview — visionOS Verifies the resulting USDZ on Vision Pro and returns device evidence to the Mac workflow. The value is primarily in using them together: prepare on Mac → verify on Vision Pro → return evidence → detect when the asset changes and needs re-testing. Both apps can stand alone, but they were designed as complementary tools. For anyone who has marketed companion apps across Apple platforms: would you position the App Store pages primarily around each individual app, or make the cross-platform workflow the central story? I’m especially interested in approaches that remain clear to users without making either product page dependent on the other app.

Hi everyone, I'm an iOS developer based in Türkiye. Over the years, some of my Apple Developer accounts have been blocked/terminated, and I was never able to regain access or find out the reason — even the termination emails didn't give me a clear explanation. Right now I'm a member of three teams: my personal (individual) account and two organization accounts belonging to companies I work for. I regularly update and release apps on all of them, so losing access again would put me and my employers in a very difficult position. Support hasn't been able to tell me why the previous accounts were closed, and I feel quite alone in this. Has anyone been through something similar? What steps do you recommend to: Avoid account termination in the first place, and Get a proper response from Apple Developer Support if it happens again? Any advice would be appreciated. Thank you!

We applied to the Small Business Program on 14 August and got the "We've received your request" email at 01:36. Three weeks later, nothing. No approval, no rejection, nobody asking us for more information. If I try to apply again the form just returns a 500, which I take to mean the application is sitting open somewhere. What's bugging me is that the discount isn't retroactive — "your proceeds will be adjusted fifteen (15) days after the end of the fiscal calendar month in which your enrollment is approved". So every month that goes by is a month billed at 30% that we never get back, and there's nothing we can do from our side to speed it up. It's cost us something concrete too. We just submitted a new version with 122 in-app purchase products after a 3.1.1 rejection, and every one of those prices had to be worked out at 30% because we had no answer. Our iPhone customers are paying noticeably more than our web customers because of a form nobody has looked at. If it gets approved next month, we get to reprice all 122 of them. I've read here that people normally hear back in 6-10 days, and also that the "contact us" button on the program page lands on support who can't help because a different team handles the review. So has anyone actually got a stuck application moving? Did asking for a tier 2 advisor work, or a phone callback? Or is it just waiting?

Yesterday I posted here after receiving 66 separate, identical Guideline 4.3 removal notices. I received no explanation or response, so I am asking again, more simply. Apple has removed the full extent of my software company from the App Store. 66 applications. Years of work. Thousands of development hours. Previously reviewed and approved apps. Different products with different purposes, functionality, designs, and users. Every single one received the same statement saying it shares a similar “binary, metadata, and/or concept” with other apps. But Apple has not told me: What binary? What metadata? What concept? What apps are supposedly similar? I am not asking Apple to waive Guideline 4.3. I am asking for enough information to understand what I allegedly did wrong. When an enforcement action removes 100% of a developer’s software portfolio, I believe the developer should at minimum be able to understand the factual basis for that decision. Can someone from App Review please answer one question: What specifically caused all 66 independently developed applications in my account to be classified as spam simultaneously? I want to comply. I want to correct anything that genuinely violates the guidelines. But I cannot correct an unidentified issue. I am asking for an explanation.

Hello, Our organization's Apple Developer Program account was terminated on 23 August 2026 under Section 3.2(f) of the Apple Developer Program License Agreement. All of our apps were removed from the App Store the same day. The notice did not identify any specific app, submission, date or transaction, so we have not been able to determine what triggered it. We submitted a reinstatement request through developer.apple.com/contact/apple-account/ on 24 August 2026. It has now been more than two weeks with no response. We also cannot use the normal Contact Us page: developer.apple.com/contact/ redirects to developer.apple.com/register/agree/ and that page loads blank, presumably because a terminated account cannot accept the Developer Agreement. Is there another way to follow up on a reinstatement request, or to confirm that it has been received? I can provide the Team ID and account details privately to anyone from Apple who is able to look into it. Thank you.

My Apple Developer Program membership expired on September 4 and all my apps have been removed from the App Store. I cannot renew through any path: The expiration banner says to renew via the Apple Developer app. I reinstalled it and signed in again — there is no Renew button, only expired membership details. On the developer website there is no billing/payment section at all — no option to add a payment method or renew. The phone callback form on my support case page is broken: tapping Call opens the confirmation page and immediately redirects back (desktop and iPhone Safari — same result). Background: I relocated to Armenia and changed the country on both my developer account and my personal Apple Account. I reported the missing payment option to Developer Support on August 17 — three weeks before expiration. Support replied that having a payment method on my Apple Account was all that's needed. It was already there and works for App Store purchases — yet no renewal charge was ever attempted, and the membership expired. Support case: 20000139749968, still unresolved. I am ready to pay right now. Could someone from Apple please check the renewal/billing state of my account or arrange a callback? It looks stuck after the country change.

SUBJECT eMenu Pro Plus (Apple ID 6476978160) - version 36.3 is not served to iOS 12 devices via Apple Business Manager / MDM; the store returns an empty asset with no fallback to the previous compatible version 1.⁠ ⁠SUMMARY Since we released eMenu Pro Plus For Restaurants 36.3, the app can no longer be installed on our iOS 12 iPads through Apple Business Manager device-assigned licences deployed by our MDM. The device requests the app, the store returns an HTTP 200 success, but the response contains no asset metadata at all - no bundleID, no softwareVersionExternalIdentifier, no download URL. The install is therefore queued and then stalls permanently in the "Installing" state; nothing is ever downloaded. Critically, the store does not fall back to the previous compatible version (36.1.3) - it returns nothing. Our two other apps assigned to the same device in the same MDM session resolve and install normally, so this is specific to this one Apple ID, not to the device, the VPP token, the account, or the storefront. We would like to understand (a) what makes 36.3 ineligible on these devices, and (b) how to get 36.1.3 delivered to them in the meantime. 2.⁠ ⁠ENVIRONMENT AND IDENTIFIERS App: eMenu Pro Plus For Restaurants Apple ID (adamID): 6476978160 Bundle ID: com.conceptic.eMenuPlus Current version: 36.3 (build 20260901), external version ID 890653216 Previous version: 36.1.3 - still present in App Store Connect, not removed from sale Declared minimum OS: iOS 12.0 (IPHONEOS_DEPLOYMENT_TARGET = 12.0), iPad-only (TARGETED_DEVICE_FAMILY = 2) Distribution: Apple Business Manager, device-assigned (device licence) VPP, pushed by our own MDM 3.⁠ ⁠SYMPTOM On the affected iOS 12 device, the MDM InstallApplication command for Apple ID 6476978160 is accepted, the app shows as "Installing", and it never completes. No download begins, and no error is surfaced to the user or reported back to the MDM. 4.⁠ ⁠EVIDENCE 4.1 Affected device - the store returns an empty asset Unified log, appstored, 3 September 2026, times in UTC+7: 17:52:14.334955 appstored [ManagedApplicationOperation]: Preflight complete app with bundleID: com.conceptic.eMenuPlus itemID: 6476978160 free: 1 owned: 0 17:52:14.632155 appstored StoreURLOperation: Received 200 response: .../MZFinance.woa/wa/volumeStoreDownloadProduct 17:52:14.637141 appstored [ManagedApplicationOperation]: No app to attempt an inline update of app with itemID: 6476978160 17:52:14.637229 appstored [ManagedApplicationOperation]: Install itemID: 6476978160 with metatdata: { } with bundleDisplayName: (null) 17:52:14.922161 appstored [ManagedApplicationOperation]: Installing vpp application with itemID: 6476978160 evid: (null) 17:52:14.927694 dmd Set state: Installing, for bundle identifier: com.conceptic.eMenuPlus volumeStoreDownloadProduct answers 200 with an empty metadata dictionary and bundleDisplayName: (null). There is no softwareVersionExternalIdentifier and no evid, so installd is never asked to install anything and the state never leaves "Installing". 4.2 Same device, same session - the other two apps resolve correctly 17:51:53.142472 appstored [ManagedApplicationOperation]: Install itemID: 911323177 with metatdata: { bundleDisplayName = "eMenu wine list"; bundleID = "com.conceptic.eMenuWine"; is32bitOnly = 0; softwareVersionExternalIdentifier = 852152575; uncompressedSize = 31519744; } with bundleDisplayName: eMenu wine list ... eMenu Wine (911323177) and eMenu Pro (483325367) are assigned from the same ABM organisation, over the same VPP token, in the same 60-second window, and both return a full asset and install. Only 6476978160 comes back empty. 4.3 Reference device (iPad 5th generation) - the same assignment succeeds 23:12:07.356426 appstored bundleDisplayName: eMenu Pro Plus For Restaurants metatdata: { bundleID = "com.conceptic.eMenuPlus"; softwareVersionExternalIdentifier = 890653216; } 23:12:16.675301 appstored Evaluating download, size = 23.2 MiB 4.4 The two OS versions use different Apple backend services The endpoints used by the two devices are completely disjoint. The affected device (iOS 12.5.8) contacts only: p23-buy.itunes.apple.com/WebObjects/MZFinance.woa/wa/volumeStoreDownloadProduct mzstorekit.itunes.apple.com/inApps/v1/receipts/renewVppReceipt It makes no request to amp-api.apps.apple.com, downloaddispatch.itunes.apple.com, or the iosapps.itunes.apple.com asset CDN. The reference device (iPadOS 16.7.15) contacts only: amp-api.apps.apple.com/v1/catalog/th/apps/6476978160?l=en&platform=ipad downloaddispatch.itunes.apple.com/ent/download iosapps.itunes.apple.com/itunes-assets/... (asset CDN) mzstorekit.itunes.apple.com/inApps/v1/receipts/renewVppReceipt It never calls volumeStoreDownloadProduct or any other MZFinance endpoint. So the affected device performs a single legacy MZFinance call and receives the empty asset shown in 4.1, while the reference device performs a catalog lookup for the same Apple ID, then a signed download dispatch, and then downloads the package. 5.⁠ ⁠QUESTIONS What makes 36.3 ineligible on iOS 12.5.8? Please confirm whether external version ID 890653216 of Apple ID 6476978160 is flagged incompatible with iOS 12.x, and which attribute drives that - the binary's MinimumOSVersion, the SDK it was built against, UIRequiredDeviceCapabilities, the architecture slices, or the available app-thinned variants. We declare IPHONEOS_DEPLOYMENT_TARGET = 12.0 and expect the app to remain installable on iOS 12. We would also like to know whether a variant the legacy service can serve exists at all for this version. Why an empty asset instead of a fallback to 36.1.3? Our logs show iOS 12.5.8 resolving apps exclusively through the legacy MZFinance volumeStoreDownloadProduct service, while newer iPadOS uses amp-api.apps.apple.com and downloaddispatch.itunes.apple.com and never calls MZFinance (see 4.4). Is version selection - including the last-compatible-version fallback - implemented on the legacy path, or only on the modern AMS path? And is that fallback supported at all for device-assigned (device licence) VPP installs initiated by MDM, as opposed to user-initiated App Store downloads? We could not find this documented either way. Returning HTTP 200 with an empty dictionary and no error also leaves the MDM with nothing to report, which we would ask you to treat as a defect regardless of the compatibility outcome.

Today I received 66 separate, identical App Review notices, one for every live app in my developer account, stating that each app will be removed from the App Store under Guideline 4.3. These apps were previously reviewed, approved, and live. They are not 66 versions of one product. They span substantially different concepts and functionality, including games, utilities, productivity tools, social tools, and video tools. Every notice says the app shares a similar “binary, metadata, and/or concept” with apps submitted by other developers, but does not identify what specifically triggered the finding. Because all 66 notices arrived together with identical language, this appears to be a portfolio-level re-evaluation. Could someone from App Review please clarify: Is there a way to request a review of the developer portfolio as a whole rather than appealing 66 identical decisions individually? Can App Review identify whether the finding is based primarily on binary/source similarity, metadata, concepts, or another factor? What is the correct appeal path when every previously approved app in an account is affected simultaneously? I want to comply fully with Guideline 4.3. I am holding off on new submissions because I do not want to guess at the cause or inadvertently make the situation worse. Any guidance from App Review or developers who have experienced a comparable account-wide action would be greatly appreciated.

this is happening real time, please somebody send updates. I just got 100+ notifications saying all my apps have been removed from App Store. what happened

Dear readers, dear Apple team, I hope this finds some attention here. I have developed a truly innovative app for creating virtual tours, which allows you to create a virtual tour entirely on your iPhone. To put it plainly, you do not need subscription services, no servers, etc. for creating a virtual tour, saving hundreds of euros. Moreover, the app has only a one-time price. Apple itself does not provide any marketing support, which is not expected. But when a user enters the full name of the app in the search, one would at least expect that their own app appears, right? What do you think? What are your experiences? Look for Panovo Virtual Tour Maker https://apps.apple.com/us/app/panovo-virtual-tour-maker/id6793510575

[Appname] was taken, despite the name itself not appearing in App Store unless accompanied by a 3 word description like "AppName: Your Personalized Thing". If I took that same approach and made it "Appname: A different thing", Apple permits it, which to me doesn't make much sense. Is this normal? It's as if I told you "Shmapp: A dating app" already existed and "Shmapp: A calculator app" is available for naming. Unless it shouldn't be and it's a bug on their end. Can an app be re-named after it's been submitted? I would have loved if I could see a preview of what it might look like on the App Store before submitting it because it's still quite grey to me.

We offer a monthly subscription and an annual subscription with a 3-day free trial. Most of our trial users are not converting. They don't cancel — auto-renew stays on, Apple attempts the charge, and it fails with a billing error. The subscription goes into billing retry instead of converting. Our monthly product converts fine. Only the annual with the trial is failing. We've audited our implementation. We use an introductory offer only — no promotional offers, no signatures, no StoreKit configuration overrides. The initial purchases all complete successfully in the payment sheet. Nothing on our side participates in the renewal charge. Two questions: Has anyone seen this pattern, and is there anything on the developer side that can influence it? What actually happens to these subscriptions? Does Apple eventually collect and we get paid, or is this revenue simply lost? What percentage typically recovers during the billing retry period?