An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.

Hello, I am new for apple developer. I see the problem and I think apple show me very few error message and I do not know to start with it. I was created my app by python and build to .app then package it to pkg by the pkgbuild. I have problem to upload the pkg file to app store connect by transporter both CLI and GUI. when I try to upload it by GUI, I see this message. Cannot find the ITMSP file: (null). (11)` and when I upload my pkg by the CLI, I found more message but still cannot start with it as well. [2026-08-23 09:57:58 ICT] <main> DEBUG: Registered file for monitoring: /Users/xxxxxxxxx/.itmstransporter/temp/tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp with action CANCEL_ALL [2026-08-23 09:57:58 ICT] <main> DEBUG: Started file monitor for 1 file(s) [2026-08-23 09:57:58 ICT] <main> INFO: Starting upload for package b7ac46de-45fe-4fa6-b0f6-6fea35038d8f-tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp. [2026-08-23 09:57:58 ICT] <main> INFO: Computing total size of files to upload ... [2026-08-23 09:57:58 ICT] <main> DBG-X: adding file for % complete logging: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp , size: 7704460 [2026-08-23 09:57:58 ICT] <main> DEBUG: Setting total size of files for upload to: 7704460 [2026-08-23 09:57:58 ICT] <main> INFO: Done computing total size of files to upload. [2026-08-23 09:57:58 ICT] <main> INFO: Starting checksum calculations for 1 file(s) using up to 1 thread(s)... [2026-08-23 09:57:58 ICT] <main> INFO: Checksum calculations are complete, elapsed time: 0 d 0h 0m 0s. [2026-08-23 09:57:58 ICT] <main> INFO: Creating reservations for build upload: b7ac46de-45fe-4fa6-b0f6-6fea35038d8f [2026-08-23 09:57:58 ICT] <main> DEBUG: creating upload file... [2026-08-23 09:57:58 ICT] <main> DEBUG: SMART-CLIENT: getCurrent(); using pinned data center = contentdelivery01.itunes.apple.com [2026-08-23 09:57:58 ICT] <main> INFO: Package upload progress: 0.00% completed [2026-08-23 09:57:58 ICT] <main> INFO: Transfer Metrics Summary: [2026-08-23 09:57:58 ICT] <main> INFO: bytes transmitted: 0 [2026-08-23 09:57:58 ICT] <main> INFO: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp transfer metrics: [2026-08-23 09:57:58 ICT] <main> INFO: bytes transmitted: 0 [2026-08-23 09:57:58 ICT] <main> INFO: Starting checksum calculations for 1 file(s) using up to 1 thread(s)... [2026-08-23 09:57:58 ICT] <main> INFO: Checksum calculations are complete, elapsed time: 0 d 0h 0m 0s. [2026-08-23 09:57:58 ICT] <main> INFO: Creating reservations for build upload: b7ac46de-45fe-4fa6-b0f6-6fea35038d8f [2026-08-23 09:57:58 ICT] <main> DEBUG: creating upload file... [2026-08-23 09:57:58 ICT] <main> DEBUG: SMART-CLIENT: getCurrent(); using pinned data center = contentdelivery01.itunes.apple.com [2026-08-23 09:57:59 ICT] <main> DEBUG: Stopped file monitor [2026-08-23 09:57:59 ICT] <main> DEBUG: Transport HTTP failed after 0 bytes, trying next transport. Error: could not upload file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp [2026-08-23 09:57:59 ICT] <main> DEBUG: Upload phase transition: CLOSED -> INITIAL [2026-08-23 09:57:59 ICT] <main> ERROR: All transport types failed for file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp Package Summary: 1 package(s) were not uploaded because they had problems: /Users/xxxxxxxxx/xxxxxxxxx/../xxxxxxxxx_Image/xxxxxxxxx.pkg - Error Messages: All transport types failed for file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp [2026-08-23 09:57:59 ICT] <main> DBG-X: Returning 1 Not too sure if anyone ever see my issue and how you solved it?

Hi, My Digital Services Act trader verification has been stuck "In Review" since July 9, 2026 — nearly 7 weeks now, against the stated typical review time of ~5 business days. Current state in App Store Connect: Business → Compliance: Digital Services Act | 27 Countries | Last Updated: Jul 9, 2026 | Status: In Review Pricing and Availability: 148 Available / 27 Cannot Sell — all EU territories show "Trader status is required for distribution on the App Store in the European Union" App is live on all non-EU storefronts (verified via apps.apple.com/us), not found on any EU storefront including Poland where I'm based All agreements, bank accounts and tax forms: Active No request for additional documents received at any point App: BirthMinder: Birthday Reminder, Apple ID: 6789108105 Support case filed: 20000148065826 (August 26) I've seen several threads describing the identical situation, including cases where the verification was already approved on Apple's backend but never reflected in App Store Connect. Could someone from Apple please check the status of this verification? Almost two months of blocked EU distribution for an indie developer is a serious problem. Thank you.

Hi all, My app has been stuck in the "Waiting for Review" status since August 13 (US Time), and today is August 23. It has been 10 days without any status updates or messages from the App Review team. App ID: 6800282515 Submission Date: Aug 13, 2026 Developer Support Request Submitted: Aug 19 (No response yet) Expedited Review Requested: Aug 20 (No response yet) Current Status: Waiting for Review Since both support inquiries and expedited requests haven't received a reply after several days, I am concerned there might be an internal system hold or communication breakdown regarding this submission. Could someone from Apple please look into this or advise if any additional documentation/action is needed from my side? Thanks for your help!

App: AI RunCoach — App ID 6782097197, bundle ID com.airuncoach.app, Team ID 4N3X74Y2LF When adding a new build to our External Testing group, TestFlight shows: "Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership." Our membership is not expired: the Membership Details page shows renewal date 20 June 2027, auto-renew ON, and the €99 fee already paid. We've also checked Agreements, Tax, and Banking — nothing shows as pending or requiring action anywhere. In the meantime, our app has been stuck in "In Review" status since August 3, and TestFlight installations also seem to be blocked. A request for an expedited review produced no result, and a request for a phone consultation did not lead to any contact either. Did anyone else experience this, and could someone advise on how to contact Apple about this? Thanks in advance for any pointers.

I'm trying to submit my app's first-ever subscriptions for review, and I'm stuck in a loop between two different App Store Connect submission flows that seem to conflict with each other. Setup: App: HeyFlat (bundle au.com.heyflat) Subscription group "HeyFlat Casa" with 3 auto-renewable subscriptions (monthly/semiannual/annual), all status "Ready to Submit" App version 1.0 has been rejected multiple times (most recently for Guideline 2.1(b) — "In-App Purchase products have not been submitted for review") What I've tried: On the Subscriptions page, I click "Add for Review" on the subscription group → it opens a "Draft Submission" panel (breadcrumb "Submissions") listing the group as an item ready to submit. That panel shows: "Unable to submit for review — Add an app version for the selected platform." I uploaded a brand-new, never-before-submitted build (build 31, version 1.0) via CI and manually attached it to the App Store version page (Distribution → App Store Version 1.0 → Build). Went back to the Draft Submission — same error persists, plus a new one: "New subscription groups must be submitted with an auto-renewing subscription from that group." The item listed is just the subscription group itself, not the individual subscriptions. Separately, the legacy per-version thread (App Review → iOS Submission) now shows build 31 as "Ready for Review" — but that thread only lists 1 item (the app version itself), no subscriptions attached, even though they're marked "Added for Review." So I have: a subscription group with 3 ready subscriptions, and a fresh unreleased build attached to the app version — but no path in the UI actually lets me submit them together. This exact same "In-App Purchases not submitted" rejection has now happened twice, with the subscriptions in this same "ready" state both times. Has anyone run into this specific mismatch between the "Submissions" draft flow and the legacy per-version "App Review" thread? What's the correct way to get a first-time subscription group submitted alongside an app version right now?

Hello. Despite making my membership payment (and accidentally twice!), my membership is still not activated even after 62 hours. I contacted their support system but received no response. Does anyone have any suggestions?

Good day, I'm trying to resolve the EU "Digital Services Act" compliance for my employer's Apple Developer account, but I'm stuck on verifying the phone number. The email verification code came through without any issue. We are located in South Africa, with a "+27" area code and the number I need to use here is a landline that comes through to the receptionist at our head office. This number does not have the ability to receive text messages, so I selected the "Didn't get a verification code?" link and chose the receive a phone call instead, however the call never comes through. Calling the number from my cellphone goes straight through to the receptionist, there are no digital switchboard prompts for the caller to select from. I tried this numerous times this Friday just past, and again twice now today, still no luck. I've requested an official document from my manager to see if I can go that route to verify the details, but so far nobody seems to be able to find an appropriate document for me to use... :( Is there anything else that I can do here?

Hi everyone! I'm back again! 😄 A few months ago I posted here after submitting my first iOS app, after previously publishing it on Google Play. That experience was really helpful, so I'm hoping to get some advice from the community again. I've just submitted my new app, Vaqui, and it's currently Waiting for Review. Vaqui is an expense-sharing app for groups, mainly designed for trips. For example, three friends travel together and pay for different things: Pepe pays for the hotel. Sandra pays for groceries. Marcos pays for dinner. Everyone participates in different expenses. Vaqui calculates the resulting balances and suggests who should transfer money to whom. The app supports multiple currencies and stores the exchange rate used when an expense is recorded. The important part is that Vaqui does not process or hold money. It doesn't provide a wallet, banking account, payment processing, cards, or financial transactions. If someone owes another person money, Vaqui simply tells them something like: "Marcos owes Sandra $15,000." They make the actual transfer themselves using their bank or payment provider, outside Vaqui. The users can then mark the payment as made/received inside the app so the group knows what has already been settled. This made me wonder about something before the review starts: Would an app like Vaqui normally be considered a financial-services app by App Review, simply because it calculates debts/balances between users? Or is it generally treated as an expense-management / expense-sharing utility as long as it doesn't actually process, hold, or transfer money? I'm asking because I want to make sure I've understood the relevant App Review guidelines correctly rather than discovering during review that I've misunderstood something obvious. 😅 The current App Store Connect information is: App: Vaqui Bundle ID: mobi.todoapp.vaqui Apple ID: 6802352647 Status: Waiting for Review Platform: iOS / Flutter If anyone has submitted an app with similar functionality, I'd really appreciate hearing about your experience. Thanks! Greetings from Córdoba, Argentina 🇦🇷 And yes... once again I'm waiting for that little "In Review" notification. 🤞😂

Update: received a response, but it appears to misapply Guideline 3.1.1, looking for input Following up on my earlier post about a stuck submission (Submission ID: 1522a8de-defd-44f8-92e8-9edbb0d85c28). After a week of silence, we finally got a response on Aug 25, but it's a rejection under Guideline 3.1.1 that we believe misreads our app. The reviewer flagged our business/organization account registration screen, stating: "The app includes an account registration feature for businesses and organizations, which is considered access to external mechanisms for purchases or subscriptions to be used in the app," and asked us to remove business/org registration entirely. The screenshot they attached shows only our Company Registration screen, just a work email and password field with a "Create Account" button. There's no purchase flow, pricing, or payment mechanism on that screen or reachable from it. Our app is a B2B marketplace connecting NYS-licensed security agencies with security guards for real, in-person shift coverage. Billing (a subscription for platform access) happens separately, later, and only for agencies that choose to subscribe, similar to how any B2B SaaS tool (Slack, Notion, etc.) lets a business create a free account before selecting a paid tier, without that account-creation step needing to go through in-app purchase. Has anyone dealt with a similar 3.1.1 rejection for a B2B/enterprise account registration flow, where the reviewer seems to conflate account creation with an external purchase mechanism? Curious whether this is a known pattern and what resolved it, a specific citation to reference, particular wording in App Review notes, or an actual call with Apple that got it unstuck. Is there anything else we should try, or can someone from the App Review team take a look at this case? Happy to provide any additional information needed — we just want to understand what's needed to move forward. Apple ID: 6799377443 Submission ID: 1522a8de-defd-44f8-92e8-9edbb0d85c28 Appreciate any insight.

We are experiencing an issue when inviting a user to join our Apple Developer Program team through App Store Connect Users and Access. The purpose of adding this user is to include them as an internal TestFlight tester after the invitation is accepted. The invited user received the Apple Developer invitation email and clicked the "Accept invitation" link. The invitation link opens the following page: https://appstoreconnect.apple.com/activation_ds?key=... The page displays "Sign in to accept your invitation" and asks the user to sign in with an Apple Account. After the user signs in successfully, the page redirects back to the same sign-in page and asks the user to sign in again. The invitation cannot be accepted, and the user cannot join the Apple Developer Program team. Steps to reproduce: Go to Users and Access in App Store Connect. Add a new user and send an invitation to join the Apple Developer Program team. The invited user receives the Apple Developer invitation email. The invited user clicks the "Accept invitation" link. The page opens appstoreconnect.apple.com/activation_ds. The user signs in with an Apple Account. After signing in, the page redirects back to the same sign-in page. Repeating the sign-in process results in the same redirect loop. Expected result: The invitation should be accepted after the user signs in, and the user should be added to the Apple Developer Program team. Actual result: The page keeps redirecting back to the sign-in page, and the user cannot accept the invitation. Troubleshooting already tried: Safari and Chrome Private browsing mode Clearing browser cookies Signing out of Apple ID before opening the invitation link again Opening the link directly in the browser instead of an email app embedded browser The issue still occurs.

Hello, I apologise for posting here. I know this forum is not a support channel, and I would not have posted if I had another way to reach App Review. Apple ID: 6759336435 Submission ID: 59a73f4a-e83b-4fa4-96dc-4c4b6a0ebcc4 Version reviewed: 1.0 (3) In review since: August 10, 2026 Rejection received: August 20, 2026 Our first submission was rejected under Guideline 4.3(a), on the basis that the app shares a similar binary, metadata or concept with apps previously submitted by a terminated Apple Developer Program account. We have no connection to any terminated developer account. RocketIO is not related to any other app, including the other apps on our own account. It is a separate product that we have been designing and writing for several years, on a different technical foundation: 114,817 lines of Dart across 139 files in Flutter, plus the Swift we wrote for the iOS tunnel host and the Network Extension, 187 tests, and 32 fully translated languages. We believe the binary match is a false positive. RocketIO statically links a publicly available open-source proxy core, as every app in this category does. That core is the largest part of the compiled binary, so any two apps linking the same open-source library will share a large amount of identical compiled code no matter how different their own source is — exactly as apps linking OpenVPN or WireGuard do. We cannot remove it, because it is the reason the app exists. RocketIO is also a bring-your-own-configuration client rather than a VPN service. It ships with an empty server list and does nothing until the user supplies a configuration for infrastructure they already own. We operate no servers, sell no subscriptions and carry no traffic. Among the protocols we have implemented are several that very few clients support on any platform, including DNSTT (DNS tunnelling), AnyTLS, ShadowQUIC, Mieru and Juicity, some of them added only recently. We replied in Resolution Center with all of this in detail, and asked which app or account the similarity was matched against, so that we could respond to the specific finding rather than guess. We are still waiting for a response. We have deliberately not resubmitted. We did not want to place another submission in the queue while this conversation is open, and we did not want to send back something that could reasonably be read as unchanged. We have been waiting since August 10, and we will be honest that it has been a difficult wait. We put years of work into this app and we have users who are looking forward to it, and at the moment we cannot tell them anything, because we do not know what specifically we are being asked to change. Could someone from App Review please reply to us there? We are glad to provide our source repository and its full commit history, to take a call at any time convenient to you in English, and to demonstrate the app live. Thank you for your time.

I specifically requested a Developer Support callback for an active App Review rejection, not general Apple Support. My issue wasn’t with my Apple ID, billing, or my account—it was about an App Review clarification that appears to be stuck in a loop. The rejection itself wasn’t because of a crash or missing functionality. It was another request for information that I had already provided in previous App Review responses. It genuinely felt like the reviewer was only looking at the latest message instead of the full review history and previous attachments. To try to resolve it, I called Developer Support and selected the App Review option. I waited on hold for over 3 hours. When someone finally answered, instead of helping with App Review or escalating the case, they transferred me to Apple Account Support. The representative there immediately told me they couldn’t help because my issue had nothing to do with Apple accounts, and they also couldn’t transfer me back to the App Review queue. So after waiting more than three hours, I was effectively back at square one and had to start over. Has anyone else experienced: Reviewers seemingly not seeing previous App Review responses or attachments? Being stuck in repeated clarification requests for information you’ve already provided? Being transferred from Developer Support to the wrong department after waiting hours? I’m trying to figure out whether this is an isolated incident or whether the App Review support process has been breaking down recently.

StoreKit 2 returns zero subscription products in Sandbox/TestFlight — FB24199369 I’m experiencing an issue where StoreKit 2 returns zero subscription products in both Sandbox and TestFlight for my iOS app. App: Bundle ID: com.sleeplessnight.naengbiseo Subscription group: Naengbiseo Premium Product IDs: naengbiseo_premium_monthly naengbiseo_premium_yearly Although the production app uses RevenueCat, I reproduced the same issue in a separate minimal native SwiftUI app using StoreKit 2 directly, with no RevenueCat, Expo, React Native, or other third-party SDK involved. Native StoreKit 2 call: let products = try await Product.products(for: [ "naengbiseo_premium_monthly", "naengbiseo_premium_yearly" ]) Current native test result: STOREKIT_COUNTRY_CODE: KOR STOREKIT_STOREFRONT_ID: 143466 DIRECT_STOREKIT_COUNT: 0 Returned products: None Test environment: Physical iPhone StoreKit Configuration: None Sandbox Apple Account signed in Storefront: KOR In-App Purchase capability enabled Correct Bundle ID and Product IDs I have rechecked the following configuration: The subscriptions are available in the test storefront Subscription pricing is configured Subscription localization is configured Paid Apps Agreement, banking, and tax information are active App ID has In-App Purchase enabled The App Store/TestFlight build has the expected Bundle ID, provisioning, and signing configuration I also created a StoreKit Configuration file using “Sync this file with an app in App Store Connect”. The sync completed, but the resulting configuration contained: products: [] subscriptionGroups: [] The same subscriptions also fail to load in TestFlight. The subscription products currently show Rejected in App Store Connect because the associated app version was rejected. App Store Connect states that the subscriptions were returned because the associated app was rejected and will remain Rejected until resubmitted for review. However, App Review also stated: “In-App Purchase products do not need prior approval to function in review.” I have reviewed TN3186 and have not found a remaining developer-side configuration issue that explains why Product.products(for:) returns zero products. Since the issue reproduces in a minimal native StoreKit 2 app, this does not appear to be caused by RevenueCat or another third-party SDK. Feedback Assistant: FB24199369 Could an App Store Commerce / StoreKit engineer advise whether there is any remaining developer-side configuration that could cause this, or whether the subscription catalog / app association may need to be reprocessed on Apple’s side? Thank you.

Hello Apple Developer Team, I’m reaching out regarding a significant delay with the App Review of my new app, Alsaqar. The app has been stuck in “Waiting for Review” for several days, even though I have already completed all the actions requested by the App Review team. App Review previously contacted me under: Guideline 2.1 – Information Needed – New App Submission I provided all the requested information, including: A screen recording of the app A physical-device test recording Demo account credentials Tested device and iOS version Detailed information about the app's purpose and functionality Information about external services and SDKs Details regarding the live auction, bidding, and in-app chat functionality The submission is still showing “Waiting for Review” and has not moved to “In Review”. For reference: Apple ID: 6802453859 Submission ID: bc2f6a16-72cd-4c13-91a0-6622596e8a60 Support Case ID: 20000143841837 I have also contacted Apple Developer Support regarding this issue and received confirmation that my support request was received, but I have not received any further response or update. This delay is significantly affecting me and my business, as the application is ready for review and I have already completed everything requested by the App Review team. Could someone from Apple please check whether there is any issue with my submission or whether it is correctly queued for App Review? I would greatly appreciate it if the submission could be reviewed or escalated to the appropriate team. Thank you for your time and assistance.

Hello, I am currently implementing External Purchase Link and External Purchase Custom Link and am encountering an issue where both ExternalPurchaseLink.canOpen and ExternalPurchaseCustomLink.isEligible always return false under all test conditions. I would like to confirm whether my setup is missing any required steps or whether this behavior is expected. Below are the details of my current environment and configuration: 🔧 1. Development Environment Xcode: 16.3, 16.4, 26.0 beta 4 Devices: iPhone running iOS 26.2 beta iPhone running iOS 16.7.12 macOS 15.5 (real device testing) Simulator iOS 18.0 Build Type: Local development build using a Developer Provisioning Profile Sandbox account signed in during testing 🔑 2. Entitlements (Developer site & Xcode) In Certificates → Identifiers → App ID, both capabilities are enabled: StoreKit External Purchase StoreKit External Purchase Link The .entitlements file in Xcode includes: com.apple.developer.storekit.external-purchase = YES com.apple.developer.storekit.external-purchase-link = YES The Provisioning Profile also contains both entitlements (confirmed via codesign -d --entitlements :-). 📄 3. Info.plist Configuration Both keys are configured with correct region codes according to documentation: SKExternalPurchase SKExternalPurchaseCustomLinkRegions 🌍 4. Test Storefront Device storefront verified as United States (US) or Portugal (PT) (US = target region for External Purchase Link, PT = EU region) But despite all the above configuration, both API calls consistently return false: ExternalPurchaseLink.canOpen // false ExternalPurchaseCustomLink.isEligible // false So I cannot proceed to testing the remaining flow (token retrieval, link opening, etc.) ------ Questions ------ ❓ Q1) Local Development Build Limitation Is it expected behavior that Developer-signed local builds always return canOpen = false / isEligible = false for External Purchase Link & Custom Link? Is there a technical or policy restriction that prevents eligibility in local dev builds? ❓ Q2) App Store Connect Configuration Requirement Are there mandatory App Store Connect settings (such as external purchase URLs, support URL, disclosures, or country configuration) that must be enabled before eligibility becomes true? Currently, no External Purchase Link or Custom Link menu is visible in my App Store Connect app settings. Is this menu only available after certain approvals or under specific conditions? ❓ Q3) TestFlight Requirement Do External Purchase Link and Custom Link only return eligibility = true on: TestFlight builds, or Distribution-signed builds? Or should eligibility also work on developer builds? Formal confirmation would be helpful. ❓ Q4) Developer Account Type Limitation We are using an Individual Developer Account (not Organization). Can Individual accounts fully request, test, and ship apps using: External Purchase Link External Purchase Custom Link Or are there limitations on account type? 🙏 Request We have completed all documented setup steps (Entitlements → Provisioning → Info.plist), but eligibility remains false, blocking feature validation. Please clarify which of the following is the cause: Local development builds do not support eligibility Missing App Store Connect configuration (not visible to us) Account type restriction Region rollout or entitlement approval requirement Any additional setup not documented publicly Thank you for your assistance.

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 first submitted my app for App Review on 16 July 2026 and the review process has now been ongoing for more than 5 weeks. During that time, the submission has gone through multiple review cycles. I have made every requested change and answered every question from App Review immediately. The problem is that after waiting several days, I am repeatedly asked a very basic question about how the app works. I answer immediately, but then it takes several more days for the review process to move forward again. I have also: Contacted Developer Support multiple times Opened support case 20000135457439 Had the submission added to the expedited review queue Been told by Developer Support that review times are currently “extremely extended” At this point the submission does not appear to be progressing toward a final decision. Each basic information request seems to result in another lengthy delay before anything happens. Submission ID: 27e289bf-307a-44e9-a285-d8ad94f82be1 Could an Apple App Review staff member please check whether this submission is stuck and escalate it if necessary?

Urgent: App Store review pending with event starting in 2 days — expedited review form shows “No App Information” I am the developer/admin of an existing iOS app for an upcoming college festival at IIT Guwahati. I have submitted a new version of the app for App Store review. This is an update to an already-published version, and the new build has been successfully tested through both internal and external TestFlight testing. The festival starts in approximately 2 days, and the app contains critical festival functionality such as digital entry passes and attendee access. Therefore, having the updated version available before the event is important. I currently have Admin access to App Store Connect, but I do not have access to the Apple Developer account/team's Certificates, Identifiers & Profiles section. Current situation: Existing app is already live on the App Store New version is submitted for review New version has passed internal/external TestFlight testing Festival starts in ~2 days Critical functionality includes digital entry passes Expedited Review form shows “No App Information” What is the correct way to request an Expedited App Review in this situation? Is there another Apple support channel I should use when the expedited review form cannot associate the app with my account? Any guidance on the correct escalation process would be greatly appreciated.

Hello, my first submission for a new app has been in "Waiting for Review" for 12 days, with no status change and no message in App Store Connect. Details: App Apple ID: 6790097966 Version: 1.0 (build 7) Submitted: August 2, 2026 Submission ID: ea22d38a-1444-450e-b335-83d4628d6829 Current status: Waiting for Review (never moved to In Review) There is no rejection, no request for additional information, and nothing in the Resolution Center. Review notes include everything needed to test the app. I also completed an outstanding Digital Services Act trader declaration on my account on 12 August, in case that was blocking the submission although is a free app, but there has been no change since. Is there anything on my side that could be holding this submission in the queue, or is this the current backlog? Any guidance would be appreciated. Thank you.

Hi everyone, I submitted my new dating app and requested an expedited review because we have a launch event planned in a couple of days. Apple accepted the expedited review request, but the app is still “Waiting for Review.” If it isn't reviewed in time, we'll unfortunately have to cancel or postpone the event. Does anyone know if there is a way to contact the App Review team or a reviewer directly, or an email/support channel I can reach out to about the status of an already-approved expedited review?£ Thanks!