Hi everyone, I’m based in Europe, and I’m trying to fully understand the current App Store payment rules for an iOS app that sells digital services or premium functionality used inside the app. My goal is not to bypass App Store rules, but to implement the correct, compliant payment flow depending on the user’s region and the App Store requirements that apply there. The app would offer things like premium features, credits, or access to digital functionality inside the iOS app. The payment flow I would ideally like to support, where allowed, is: iOS app -> Cloud ahndling -> Stripe Checkout page -> user pays -> Stripe handling -> my backend marks the user as premium What I’m trying to understand is whether this flow is allowed, restricted, or prohibited depending on the user’s App Store storefront / region. My questions are: For digital goods, subscriptions, credits, or premium features used inside an iOS app, is Apple In-App Purchase still required by default? In which regions, exactly, can an iOS app use or link to an external payment provider such as Stripe for digital services used inside the app? For users in the United States, after the Epic Games v. Apple changes, can an app show an external payment option such as “Subscribe on the web” or “Pay with Stripe”? If yes, what are the exact requirements, limitations, wording rules, Apple fees, or reporting obligations? For users in the European Union, under the DMA-related rules, does Apple allow external purchases through Stripe or a web checkout? If yes, do I need specific Apple entitlements, StoreKit External Purchase APIs, Apple approval, transaction reporting, or payment of Apple fees? For the rest of the world, should I assume that Apple IAP is mandatory for digital content, subscriptions, credits, and premium app functionality unless Apple has a specific regional program allowing external payments? What is the correct way to determine which payment flow a user should see? Should this be based on the user’s App Store storefront / StoreKit storefront, rather than IP address, device locale, billing address, or country selected manually by the user? Would a regional routing approach like this be compliant? if App Store storefront == US: show Apple-compliant external purchase link / Stripe option if allowed elif App Store storefront is in the EU and the app has the required Apple entitlement: show Apple-compliant external purchase flow else: show Apple In-App Purchase only If a user pays through Stripe or another external checkout in a region where external payments are allowed, can my backend unlock premium features inside the iOS app? Or are there restrictions on granting access inside the app when the purchase was not completed through Apple IAP? For a first App Store release, is the safest approach to launch with Apple IAP only, then later add external payment options only in regions where Apple explicitly allows them? For developers who have recently submitted apps with external payment links for digital services: Which countries or storefronts were accepted? Did App Review require special entitlements? Were there specific wording or UI requirements? Did Apple require transaction reporting or apply additional fees? Were there differences between the US, EU, and other regions? In short, I’m trying to understand the practical compliant architecture: iOS app = Apple IAP by default external Stripe / web checkout = only where regionally allowed by Apple backend = unlock premium access after valid payment, whether Apple IAP or approved external payment payment UI = adapted based on App Store storefront / region I would really appreciate answers from developers, App Review experiences, or anyone familiar with the current Apple rules after the Epic ruling, DMA changes, and Apple’s External Purchase Link / StoreKit External Purchase programs. Thanks!

I recently noticed that an app called Private Browsing Web Browser has been ranking at the top for the keyword “browser” on the App Store for a long time, even ahead of well-known browsers like Chrome, Firefox, and Safari. This is not only the case in the U.S.; it also appears to rank top in many other regions. This app has not been updated for a long time, and both its interface and feature set seem extremely basic. There also appears to be nobody to discuss it on the internet, and some of the App Store ratings look very suspicious. I previously reported this to the Apple team by email, and questioning about the algorithm, but they consistently responded: The App Store ranking system has no problem, and it's working as expected.” I wanted to ask everyone: Do you think it is normal for this app to rank number one for “browser” on the App Store? Also, the same developer has another very similar browser app called Snowbunny Private Web Browser, which also ranked high.

I recognize that Apple has put out documentation on how to do things with the new Age APIs, but I have no idea what my apps are supposed to do to be in compliance with this law. Most of the law sounds like it applies to App Store developers like Apple, more than it pertains to individual app devs. If the age rating of an app changes, wouldn't we just put it in App Store Connect and have Apple disable those apps on the devices of the underage kids?

Hello, I’m currently dealing with an App Review situation that has been stuck with no real progress and no useful feedback from Apple. App Name: Juego de Impostor: Palabras Apple ID: 6757995242 Bundle ID: com.rgioia.impostorwords Version: 1.8.0 Current Status: Ready for Review Previous Version: 1.7.0 Ready for Distribution Timeline: The app/update has been waiting for review for an unusually long time. There has been no clear movement, no rejection, no explanation, and no actionable feedback from the review team. This is especially frustrating because this is not a new experimental app or an unclear submission. The app is already prepared for release/update, and I need to push fixes and improvements for users. What I already did: Requested expedited review → approved Contacted Apple Developer Support multiple times Followed up several times Waited without receiving any meaningful update The only response I received was that the expedited review request was accepted, but after that nothing actually happened. Impact: The app/update is completely blocked I cannot release fixes or improvements There is no rejection reason to fix There is no communication from App Review I have no visibility into whether this is a review queue issue, an account issue, or a pipeline problem At this point, this does not feel like a normal App Review delay. It feels like the submission is stuck somewhere internally with no owner and no progress. Questions: Is anyone else experiencing this kind of delay recently? Is there any real way to escalate a stuck App Review case after an expedited review was already approved? Could this indicate an issue with the App Review pipeline or my account/app status? How can I get someone from Apple to actually look into the submission instead of receiving generic support replies? I understand that delays can happen, but having an app/update blocked for this long with no feedback, no rejection, and no progress is not acceptable for developers trying to maintain a live product. Any help, visibility, or escalation path would be appreciated. — Ramiro Gioia

I submitted my new app on Friday evening (5/29) and still haven’t heard anything back and it’s been 4 days. It says it should be 24-48 hours and at my old company we would get reviewed within hours, granted that app was being updated and not new. How long does it usually take for new apps to get approved? It seems like this is happening to a lot of people now, is there anything we can do? I had a goal to get this released end of May and feeling a little helpless on how to move forward. Thanks!

I'm developing a sandboxed clipboard history manager for macOS. When a user selects an item from their clipboard history, the app: Writes the data to NSPasteboard.general Posts a ⌘V keystroke via CGEvent.post(tap: .cgSessionEventTap) This requires the user to grant permission under System Settings > Privacy & Security > Accessibility (kTCCServicePostEvent). The app does not use any Accessibility framework APIs (AXUIElement, AXIsProcessTrusted, etc.) — only Core Graphics event posting. The app has been rejected twice under Guideline 2.4.5, with the reviewer stating that Accessibility features should not be used for non-accessibility purposes. My understanding is that kTCCServicePostEvent (used by CGEvent.post) is a separate TCC service from kTCCServiceAccessibility (used by AXUIElement APIs), but both appear under "Accessibility" in System Settings, which may be causing confusion. My questions: Is there an approved way for a sandboxed Mac App Store app to simulate a keystroke (specifically ⌘V) after writing to the pasteboard? If CGEvent.post is not appropriate for App Store apps, what alternative API should clipboard managers use to provide a "paste" action? Is there a way to use CGEvent.post that is compliant with Guideline 2.4.5? I have a minimal sample project (single Swift file, sandboxed) that demonstrates the behavior. I can share it if helpful. I was referred here by DTS (Case-ID: 19088416).

I'm getting repeatedly rejected under Guideline 2.1(b) - App Completeness, with the message that the in-app purchase products "failed to load." This has happened on multiple submissions now, and I'm stuck because everything works fine on my end. My setup: 2 auto-renewable subscriptions + 1 in-app purchase, all in "Waiting for Review" status and attached to the current version (1.0.0). All three products load and purchase successfully when I test via TestFlight with a Sandbox account. No errors at all. Paid Apps Agreement, banking, and tax forms are all Active. I have another app on the same account where IAPs are live and working, so I don't think it's an account/agreement issue. Review device was iPad Air 11-inch (M3), iPadOS 26.5. One detail that might be relevant: this account was migrated from an individual to an organization account a while back, and there were some app transfers involved on the account (though not for this specific app). What I've already tried/confirmed: Product IDs in code match App Store Connect exactly. Products are attached to the build (there's no separate section to re-attach them on resubmit, which I understand means they're already linked). Resubmitted multiple times with the same result. My questions: Has anyone seen IAPs load fine in Sandbox/TestFlight but consistently fail in App Review specifically? What was the root cause? Could the individual-to-organization migration or prior app transfers cause IAPs to fail loading only in the review environment, even when agreements show Active? Is there anything region/storefront-specific that would make SKProductsRequest / Product.products(for:) return an empty list for the reviewer but not for me? Any pointers would be hugely appreciated. Thanks!

Hello Apple Developer Support Team, I would appreciate your assistance regarding a prolonged review delay for my app. App Name: Chat Mate for Messenger App ID: 6762255821 My app was previously rejected, and after addressing the review feedback, I resubmitted the update. However, it has now been 14 days and the app remains in "Waiting for Review" status without any further communication or review activity. This project is extremely important to me and my team. We have worked diligently to resolve all issues raised during the previous review and are very eager to launch the app. The extended delay is significantly impacting our planned release schedule and ongoing work. Could you please investigate the status of this submission and help move the review process forward if possible? We would greatly appreciate any update or assistance in getting the app reviewed and, if approved, made live as soon as possible. Thank you for your time and support. Best regards, Muhammad Ahmed

Hello Apple Developer Support, Our app, GluAI (Apple ID: 6757767664), is currently live and available on the App Store. The direct App Store URL works correctly: https://apps.apple.com/app/id6757767664 However, the app does not appear in App Store search results when searching for the exact app name "GluAI". The app has been live for approximately 3 weeks, so we would appreciate it if you could verify that the app has been properly indexed and is eligible to appear in App Store search results. App Name: GluAI Apple ID: 6757767664

Title: Unable to upload app after App Transfer – ITMS-90076 Team ID mismatch (Keychain access issue) Body: Hello, I am experiencing an issue when uploading an iOS app after an App Transfer between two developer accounts. Current situation: The app has already been transferred to a new Apple Developer Team The app appears correctly under the new team in App Store Connect The Bundle Identifier remains the same I am building the app using the new Team's Apple Distribution certificate A new App Store provisioning profile has been created for the new Team However, when attempting to upload via Xcode Organizer (Distribute App → App Store Connect → Upload), the upload fails with the following error: ITMS-90076: Possible loss of keychain access. From my understanding: The previous app versions were signed with the old Team ID The new build is correctly signed with the new Team ID This seems to indicate that although the App Transfer is complete from a UI perspective, the App Store backend still compares against the previous Team ID. Questions: Is this expected behavior immediately after an App Transfer? Is there any required step to fully synchronize or refresh the app’s Team ID internally? Should it be possible to upload successfully after transfer without changing the Bundle ID? Is there a known delay or internal process before uploads from the new Team are accepted? Additional info: Xcode version: [your version] Newly created archive after transfer Certificates and provisioning have been recreated under the new Team Any guidance or similar experiences would be greatly appreciated. Thank you. 日本語 現在、App Transfer後のアプリをアップロードする際に問題が発生しています。 【状況】 ・アプリは新しいApple Developer Teamへ移転済み ・App Store Connect上でも新しいTeamに表示されています ・Bundle Identifierは変更していません ・新TeamのApple Distribution証明書でビルドしています ・新しいApp Store用Provisioning Profileも作成済みです しかし、Xcode Organizerからアップロード（Distribute App → App Store Connect → Upload）を実行すると、以下のエラーで失敗します。 ITMS-90076: キーチェーンアクセスの喪失の可能性 【認識】 ・旧バージョンは旧Team IDで署名されている ・新ビルドは新Team IDで正しく署名されている 【疑問点】 App Transfer直後にこの現象は仕様として起こるものでしょうか？ 内部的にTeam IDの同期や再反映を行う必要はありますか？ Bundle IDを変更せずにアップロードは可能な想定でしょうか？ App Transfer後にアップロードが可能になるまでタイムラグはありますか？ 【補足】 ・アーカイブはTransfer後に新規作成しています ・証明書およびプロビジョニングは新Teamで再作成済みです 同様の事象や解決方法をご存じの方がいらっしゃいましたら、ご教示いただけますと幸いです。 よろしくお願いいたします。

I haven't updated my app in months, but I discovered my app icon color recently changed entirely on its own, and it displays inconsistently in App Store, App Store Connect, and TestFlight. Everything works fine locally during development. It's all as expected in Icon Composer and Xcode. Typically, the icon shows a white symbol on a blue background. But now, online, the white symbol is a dark red color, and there seem to be additional Liquid Glass and shadow effects that I never chose. So, somewhere in Apple's backend processing of my .icon file, it's getting malformed and rasterized with different parameters than expected? And different cached versions are being displayed in different places? On web, it's showing the incorrect version. Same in App Store Connect and TestFlight. In App Store on iOS, the incorrect version is shown in search results, but the correct version is shown on the product page. I've attached some screenshots. Store link: https://apps.apple.com/us/app/kitchenkit-grocery-organizer/id6754018760 Related threads: https://developer.apple.com/forums/thread/812852 https://developer.apple.com/forums/thread/811770 https://developer.apple.com/forums/thread/823078

Could you help clarify the expected behavior in downgrade scenarios during a Free Trial period? Does Apple trigger billing immediately for the downgraded plan, or does the change take effect only after the Free Trial window completes?

To the App Review and Developer Support Teams, I am writing this post to bring an ongoing and time-sensitive App Review issue to your attention, as my submission has remained in “Waiting for Review” for an unusually long period of time and standard support channels have not yet provided a clear update or resolution. Issue Summary: My app, Cupie, was submitted for review on May 21, 2026. However, the submission has remained in “Waiting for Review” since then and has not moved to “In Review” after several days. I have already submitted an expedited review request and also contacted Apple Support regarding the delay. However, I have not yet received any clear explanation, actionable feedback, or confirmation on whether there is an issue with my account, metadata, build, agreements, or submission queue. Lack of Communication: I have opened the following support cases regarding this issue, but I have not received a meaningful update so far: Case IDs: 102900823761 102901498888 The current lack of communication makes it difficult for me to understand whether my submission is properly queued for review, whether it is stuck, or whether there is any action required from my side. Impact: This is our first public launch submission, and the delay is directly affecting our launch schedule, business operations, and user onboarding plan. We are ready to provide any additional information, test accounts, explanations, or compliance materials required for App Review. Request: I respectfully request that the App Review or Developer Support team help confirm the current status of this submission and clarify whether there is any issue preventing it from moving forward. Specifically, I would appreciate confirmation on the following: Whether my app submission is properly queued for review. Whether there is any issue with my account, metadata, build, agreements, or in-app purchase configuration. Whether the submission is delayed due to additional manual review or review queue congestion. Whether any action is required from my side to proceed. App Name: Cupie - 語音視訊、聊天交友 App ID: 6768550401 Current Status: Waiting for Review Submitted Date: May 21, 2026 Related Case IDs: 102900823761 102901498888 I would sincerely appreciate a prompt update or escalation from an Apple representative, as the submission has been waiting for review for an extended period without clear communication. Thank you for your assistance. Sincerely, Cupie Development Team

Hi everyone, My new app, was recently approved and its status changed to "Ready for Sale" in App Store Connect. Everything seems to be working fine technically: I can download the app perfectly using the direct App Store link, and it also appears correctly when I click on my Developer Name. However, when I search for the exact and unique name in the App Store search tab, it doesn't show up at all. I am aware that search indexing can usually take anywhere from 24 to 72 hours, but I wanted to ask if anyone else is experiencing unusual delays with the search index right now? Is there anything else I can do to trigger the indexing process besides waiting or pushing a new update?

Hello, I would like to understand the possible end-user journey when a subscription transitions into the DID_FAIL_TO_RENEW state. During this period—when the App Store continues to retry billing for up to 60 days, or until the user resolves the billing issue or cancels the subscription is the user allowed to purchase the same subscription again? If so, my understanding is that this would follow a resubscribe flow, rather than an initial purchase flow. Could you please confirm and provide further details on how this scenario is expected to behave?

Since some time now, when users try to buy my App on the Mac App Store or want to start the trial, the system dialog to confirm the purchase is not working correctly. The dialog is sticking to the upper border of the screen behind the menubar and can‘t be moved. And - this is the real problem - users can not confirm the purchase, because the button (or Touch ID field) is not shown. Only the cancel button is there and clickable. Usually (where the arrow points) there is the Touch ID symbol, the password field or purchase button. Any ideas?

Hi, we're urgently trying to resolve the changing of our account membership details. We need our app developer name to match our business name as it's currently wrong. All the information can be found under the case number 102893432961. Could this please be urgently looked into?

This happens way too often (see the image below). Especially today. I used this snippet from the offical Rust website to install rustup: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y Run ci_post_clone.sh script Run command: 'cd /Volumes/workspace/repository/apps/app/ios/ci_scripts && /Volumes/workspace/repository/apps/app/ios/ci_scripts/ci_post_clone.sh' info: downloading installer warn: curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org curl: (6) Could not resolve host: static.rust-lang.org error: command failed: downloader https://static.rust-lang.org/rustup/dist/x86_64-apple-darwin/rustup-init /var/folders/6h/_32gb9js77g6c54h3q7g6q1h0000gn/T/tmp.yave38jqWa/rustup-init x86_64-apple-darwin Error: Command exited with non-zero exit-code: 1 Warning: Running ci_post_clone.sh script failed (exited with code 1). Executable scripts are run using the interpreter specified in the shebang line.

[Repost: Somehow my original thread from Jan was deleted. I called dev support and they said to post again, if there's a better channel to get answer for this, please let me know.] I’m an indie dev with a paid, one-time-purchase app (Dash Calc, $4 USD), and sales have been rough. In a crowded category, an upfront-paid app feels like a tough sell without a way to try it first. I’d like to offer a simple 7-day free trial followed by a single lifetime purchase, but App Store Connect still doesn’t officially support trials for paid apps. In Jan 2023, an App Store Commerce Engineer recommended the $0 non-consumable IAP + paid non-consumable IAP workaround: https://developer.apple.com/forums/thread/722874 I haven’t implemented it yet, but the subsequent discussion suggests the approach is overly complex. Handling refunds, reinstalls, activation timing, and purchase history requires non-obvious logic, and some developers report customer confusion and drop-off when presented with a $0 trial IAP. Has anything improved since 2023? Any new StoreKit APIs or App Store Connect changes that make this simpler or less error-prone? Is the $0 non-consumable IAP still the recommended approach in 2026? Any updated policy guidance for time-limited access on one-time purchases? I’m happy to use the workaround if it’s still the official path—I just want to confirm there isn’t a better option now.

Hi Apple, I hope you are doing well. I am posting here regarding my app, Subscription & Expense Manager (App ID: 6759901202), which has been stuck in the “Waiting for Review” state since March 4, 2026 at 2:45 PM. It has now been an extremely long time without any update, review progress, or communication from the App Review team, and I am becoming increasingly concerned about this unusual delay. I completely understand that review times may vary depending on workload and internal processes, but this duration seems far beyond normal review timelines. Our team has invested substantial time, effort, and resources into developing this application, and the continued delay is significantly affecting our launch plans and business timeline. We have carefully followed all App Store Review Guidelines and ensured that every required detail, asset, permission, and compliance item was properly submitted. At the moment: There are no rejection messages No metadata issues are shown No additional information requests are pending The app simply remains stuck in “Waiting for Review” We have also already contacted Apple regarding this matter but unfortunately have not yet received a response. I would sincerely appreciate it if someone from Apple or the developer community could guide me on: Whether this kind of delay is currently common If there is any way to escalate the issue Whether there may be an unseen issue causing the review to not start We are fully prepared to provide any additional information or make immediate changes if required from our side. This app is very important to us, and we are genuinely worried because of the extended delay after putting so much hard work into the project. Any help, advice, or update would be greatly appreciated. Thank you. HR Apps