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.

I added an alternative app icon to my latest iOS build for A/B testing. However, after submitting the build for review, only the main app icon is showing under Build > Included Assets. I expected the alternative icon to be visible there. Am I missing something? Thanks in advance.

Hello, I understand that App Store Connect allows us to perform A/B testing on app icons. Since user preferences often vary by region, is it possible to apply different winning icons to different localized storefronts once an A/B test concludes? Thank you.

Hi, I'm trying to hook up some test in app purchases to test purchase code between our app and our app's backend. When I try to load products (requestProductData) with my Sandbox account, my product identifiers come back in the invalid product identifiers member of the response. My product says it's in "waiting for review" status in app store connect, and I'm logged in to the app store with my sandbox account on my device. We just accepted the paid apps agreement as well--is there some propagation time to that? The product ID I'm using (both in app store connect and in-app) is test_durable. Do I need to append the package name to that or something? I've dug through the docs and through the forums here and come up empty. I tried using the Xcode storekit test harness and the issue there is that because that doesn't actually talk to the store apis, I can't use that to test my backend correctly validating/processing the transactions. Thanks!

Hello, I recently received a Pending Account Termination Notice for my Apple Developer Program account. The notice refers to section 3.2(f) of the Apple Developer Program License Agreement and says the account may have been involved in dishonest or fraudulent activity, including possible concept or feature switching after review. I have already submitted an appeal to the App Review Board. The difficult part is that the notice does not mention a specific app, bundle ID, version, or behavior. I have multiple apps under the account, so I am trying to identify what may have caused the issue. During my review, I found one possible area: one app uses different API server endpoints depending on the user’s IP region or network location. This was only done to improve connection speed and reliability. For example, overseas users may connect to an overseas server because access to Mainland China servers can be slow or unstable. The app is not intended to show different features, menus, content, or user flows across those servers. The server routing only changes the API endpoint for performance reasons. It is not used to detect App Review users or hide any functionality. I also have several other apps under the same developer account. These apps were previously reviewed and approved through the normal App Review process, and I did not intentionally implement any mechanism to mislead App Review, hide features, or change the app concept after approval. Because the notice applies at the account level but does not identify a specific app, bundle ID, version, or behavior, I am having difficulty understanding what exactly triggered this enforcement action. I am willing to review and correct any issue, but I need to understand whether the concern is related to regional server routing, a specific app implementation, App Store metadata, server-side configuration, or something else. My questions are: Can regional API routing based on IP or network location be misunderstood as dynamic content or feature switching after review? What kind of documentation or evidence is most helpful to provide in an appeal to show that different server endpoints provide the same app experience? Should I provide side-by-side API responses, backend configuration screenshots, and screen recordings from different regions? If the termination notice does not identify a specific app, is there any way to request clarification about the app, bundle ID, version, or behavior that caused the concern? Is there any recommended way to document multiple apps in an appeal when the notice is account-level rather than app-specific? I understand that nobody here can make a decision on my account. I am only looking for general advice on how to clearly explain this type of server routing, how to review multiple apps under the account, and what evidence is usually useful. Thank you.

Hello, Our Test Flight internal user limit is stuck at 100/100 users and I couldn't reduce the number and free seats no matter what I tried. What I tried so far: Reduced number of people in Users and Access to 98 (excluding customer support which does not count for internal users anyway) Reduced number of internal testers in the only internal Test Flight group to 38 Testers. Reduced number of all testers for the app to 97 (including external test only users) Made sure that deleted users from Users and Access list have no emails in the internal test group. More importantly, no matter how many users I delete from both Users and Access or only internal tester group, the limit always shows 100/100. I appreciate any help. This feels like a bug. I am unable to contact Apple support, I waited for almost an hour on the phone but nothing. I waited for days for potential caches to clear up, still no luck.

Hello Applet, I’m experiencing an issue with StoreKit on a TestFlight build. My app uses auto-renewable subscriptions through StoreKit and RevenueCat. Configuration already verified: App installed through TestFlight (not debug). Bundle Identifier: com.ciborgu.vytalai Paid Applications agreement is active. In-App Purchase capability is enabled. Three auto-renewable subscriptions exist in App Store Connect. Product IDs match exactly between App Store Connect, RevenueCat and the application. RevenueCat initializes successfully. A Sandbox test account has been created. Tested on a physical iPhone. Device restarted and app reinstalled from TestFlight. VPN and iCloud Private Relay disabled. When attempting to purchase a subscription, the Apple payment sheet never appears. Our diagnostics indicate that StoreKit does not return any available products for the configured Product IDs, preventing the purchase sheet from opening. Expected Product IDs: vytalai_premium_monthly vytalai_premium_yearly vytalai_premium_yearly_intro Could you please verify if there is any issue with the App Store Connect configuration, StoreKit availability, or the processing state of these subscriptions on Apple’s side? If additional logs or diagnostics are required, I can provide them. Thank you. I have already contacted Apple Developer Support regarding this same issue. Previously, I was advised to schedule a technical support meeting. However, when I requested the meeting, my request was declined because of the subject of my issue, so I was unable to speak with an Apple engineer. Since I have now completed all the recommended troubleshooting and the issue still persists, I would greatly appreciate it if this case could be reviewed by the appropriate technical team or a StoreKit engineer. Thank you for your assistance.

Hi everyone, I want to start by saying that I genuinely appreciate the work Apple’s reviewers, support teams, engineers, and testers do. The volume and variety of apps they have to evaluate must be enormous, and I understand why Apple has to be careful about protecting users and the App Store from deceptive or unsafe apps. I’m posting because I’m looking for guidance from anyone who has navigated a Pending Account Termination appeal. This is for my first iOS app submission. The app is a location-based social planning app for adults to create and join nearby plans. It is a real product, not a template/spam app, and I have been trying to make review as straightforward as possible. Timeline: Submitted / Ready for Review: June 10, 2026 In Review: June 15, 2026 I also had a TestFlight external testing review delayed for about a week I submitted support requests and an expedited review request, but did not receive any responses 19 days after submission, I received a Pending Account Termination notice alleging dishonest or fraudulent activity under the Developer Program License Agreement I have submitted an appeal to the App Review Board. The web page confirmed receipt, but I did not receive a separate email or appeal case ID. I also opened a Developer Support case just to confirm the appeal is in the queue. I want to be very clear: the app is honest and there was no intent to evade App Review. Because the app depends on nearby user-generated plans, I had created demo/test data and a review account so reviewers would not see an empty app in a location with no users. After TestFlight external testing was approved and before sharing the public link with real testers, I removed the synthetic test/demo data so production would contain real user activity only. I have already taken corrective steps: Removed automatic review/demo reseeding behavior from the backend Removed synthetic demo users and content related to them from production Current production data is real user data only I understand Apple has to protect users and the App Store from deceptive apps, spam, and fraud, and I appreciate how difficult that job must be at scale. I’m trying to handle this carefully and respectfully. For anyone who has been through a Pending Account Termination appeal: Is it normal not to receive an appeal case ID by email? How long did the App Review Board take to respond? Is there any appropriate way to provide clarifying information after submitting the appeal, or should I wait for Apple to reply? Thank you for any guidance.

Summary My app "Hibika" has been completely absent from App Store search results since launch on May 25, 2026 — now over 5 weeks. This includes searching for its exact, unique brand name, which should be the most trivial search match possible. App details App name: Hibika App ID: 6760477185 Bundle ID: com.chrisbc.hibika Version: 1.2.0, status: Ready for Distribution Category: Health & Fitness / Habit tracker What's broken Searching "Hibika" in the App Store app or on apps.apple.com returns zero results — not even a distant match — in every storefront I've tested (Spain, US, UK, Germany, France, Mexico, Japan). The app's direct product page loads correctly and is fully functional: https://apps.apple.com/us/app/hibika/id6760477185 Search by keywords/subtitle terms also returns nothing, which is expected since those aren't indexed for a brand-new app with low install volume — but the complete absence for the exact brand name is not normal behavior and does not match any documented ASO ranking factor. What I've verified so far Not a device/cache issue — reproduced across multiple devices, regions, and by independent third parties (including an Apple Developer Support advisor who confirmed the same result on their end). Not a regional listing gap — app availability is confirmed active in all major storefronts. A separate issue with user reviews not appearing on the product page self-resolved after a few weeks, but the search indexing issue persists. Apple Developer Support case history Case escalated to a Senior Advisor in early June. Escalated to Engineering team on June 17 (ticket 180061872). As of July 2, no update or resolution provided, despite multiple follow-ups. Question for the community Has anyone experienced total invisibility in App Store search (including exact brand name matches) that lasted this long? If so: Did it resolve on its own, or did something specific fix it (title/subtitle change, rebuild, resubmission)? Any idea what backend indexing bug could cause a brand-new app to be excluded even from exact-name search? Any insight from developers who've hit this — or from Apple engineers who might see this — would be hugely appreciated. Happy to share more diagnostic details if useful.

Hi, I'm having a problem because my app stuck in "waiting for review" status since Friday (June 26th). Today is the fifth day we've been waiting for Apple to review the app. We had an app lunch scheduled for today and are stuck with no information. We contacted Apple via the standard contact form and requested expedited app review, but unfortunately, nothing has changed; we haven't received a response to our messages. The app is still "waiting for review." What should I do? Is there another way to contact Apple to expedite the review, or at least get information about the review date? App Name: Genie Vault App ID: 678469924

My app (RunWeather) is live on the App Store, but its two auto-renewable subscriptions have never reached Approved, so the StoreKit paywall returns no products and users can't subscribe. Subscriptions: com.iustinn.runweather.pro.monthly com.iustinn.runweather.pro.annual Both show "Pending Binary Approval". The English (U.S.) localization on each is stuck in "Rejected", and App Store Connect won't let me edit or delete that localization (the fields are locked), so I can't correct the copy and resubmit. I never received a clear reason for the localization rejection. History: each time I submitted a build with these subscriptions, the build was rejected for an unrelated reason; I resubmitted, the build was eventually approved, but the subscriptions stayed behind in this stuck state. I also created duplicate subscription products (…monthly2/3/4, …annual2/3/4) as a workaround; those just sit in "In Review" indefinitely. What I've tried: Editing / deleting the Rejected U.S. localization -> blocked, fields locked. Re-submitting builds -> app approved, subscriptions not. Questions: How do you unstick a subscription whose Rejected localization can't be edited or deleted? Is an App Review support ticket the only path to reset it? For "Pending Binary Approval" subscriptions, does attaching them to a NEW app version (reusing the existing build, no new binary) and submitting force them back through review? Has anyone cleared this exact locked-localization state another way? I've also opened an App Review case. Posting here in case someone hit the same locked-localization state. Thanks.

I want to delete an app from App Store Connect, but I've been unable to do so. App Information: App Name: Need to be removed-MI Apple ID: 6742525904 Current Status: Prepare for Submission I have already followed Apple's official guidelines for removing the app: https://developer.apple.com/help/app-store-connect/create-an-app-record/remove-an-app/ The following operations have been completed: App information has been reset; All in-app purchases have been deleted/cleared; All subscriptions and subscription groups have been deleted/cleared; The app has been removed from all sales regions; App Review Submission has been removed; The submission record in the App Review page now shows as Removed; Logged out and re-logged into App Store Connect; Browser cache and history have been cleared; Attempted to repeat the process using Safari for Mac and different network environments. Currently, when deleting the app, a prompt still appears: “This app is unable to be removed right now. This app cannot be removed. Learn more about removing apps. This app has in-app purchases that are in review. Please try again once these in-app purchases are no longer being reviewed.” The previous error message also included: “Some items related to this app are currently in review. To remove this app, you must first cancel the submission.” However, after removing the App Review Submission, this section has disappeared, and only the prompt related to "in-app purchases that are in review" remains. Currently on the App Store Connect front-end page: The In-App Purchases page is empty; The Subscriptions page contains no subscription items or subscription groups; App Review submission history has been removed; The app is currently in the Prepare for Submission state; No IAPs, subscriptions, or submissions currently under review can be found. Previously, the Subscriptions page displayed a notice: “One or more of the subscriptions listed below requires your attention.” However, the page does not display any subscription items or subscription groups. I'd like to ask if anyone has encountered a similar situation: the front-end page no longer shows any IAP or subscription items, yet when deleting the app, it still prompts that in-app purchases are under review? Is this situation due to residual IAP/Subscription review statuses left behind by Apple's backend, requiring contact with Apple Developer Support for cleanup? Or is there another hidden entry in App Store Connect that can be used to remove these lingering items?

I’m having an issue with the Apple Developer Program. I received a notification that the Apple Developer Program License Agreement has been updated and must be accepted in order to continue submitting and updating apps. The problem is that after signing in to my Apple Developer account, I don’t see any option to accept the new agreement. Instead, I’m shown a “Join the Apple Developer Program” screen, as if I’m not enrolled in the program, even though I have active apps on the App Store. In App Store Connect, I can see the agreement status as “Active (New Agreement Available)”, but there is no visible way to actually review or accept the updated version. Has anyone experienced a similar issue and knows how to fix it?

Hi everyone, and hopefully Apple Staff, I am looking for some advice or assistance regarding an unusually long App Review delay for our game. On June 23 (Tuesday), we submitted a comprehensive appeal and build (v1.0.5). It has been 7 days and our app is still not in the "In Review" state. This unexpected delay is severely impacting our marketing schedule in Turkey. We have pre-launch campaigns, offline events, and schedules with about 30 local KOLs that are being continuously delayed, causing significant financial and operational impact. I have already submitted an Expedited Review Request, but I haven't received any updates yet. Has anyone else experienced similar delays recently after an appeal? Are there any Apple representatives here who could kindly take a look at our Submission ID? Any advice on how to proceed would be greatly appreciated. Here are the details of our submission: App Name: Era Online: Şeref Savaşı App ID: 6773240689 Bundle ID: com.ark.xhmzxqteq.ios Submission ID: d19cb33a-b179-4f82-85e7-4acc77f46968 Thank you so much for your time.

Hi, I am setting up my first Paid Apps agreement as an individual developer based in Germany, and a few things appear to be stuck. Current status in Agreements, Tax, and Banking: Paid Apps agreement: Pending User Information Bank account (German bank, EUR payout in USD): Processing U.S. Form W-8BEN: Tax information missing My main question is about the address. My Membership Details and the legal entity address still show an old "c/o" mail forwarding address. I submitted an update through "Update Information" more than a week ago, but the displayed address has not changed. How do I actually update the legal entity / membership address? Is there a self-service option, or does this require contacting Developer Support and selecting Legal Entity Information? Is the displayed address simply not refreshing after an update, or did my change not go through? Does a "c/o" mail forwarding address as the account address cause any problem for the Paid Apps agreement or the banking verification? I understand the W-8BEN is still outstanding and I plan to complete it next, with my actual residence address on line 3. I just want to confirm the address on the account is not a separate blocker before I submit. Thank you in advance for any guidance. best regards!

I have a Capacitor (web-based) iOS app. All UI strings are localized in the JavaScript layer at runtime, so the app bundle has no per-language storyboard or .strings resources. I want the App Store product page's "Languages" section to list every language we support (en, de, es, fr, it, pt-BR, tr) — right now it only shows English. In our last release I added a CFBundleLocalizations array to Info.plist with all 7 codes. That build is live, but the product page still shows only "English." My questions: Does the App Store "Languages" list derive from CFBundleLocalizations, from the actual .lproj folders compiled into the binary, or both? If .lproj folders are required, is adding empty/stub .lproj folders (registered in the project's knownRegions) enough, or do they need real localized content? After a build with the correct setup goes live, how long until the list refreshes? Thanks — I want to confirm the correct approach before shipping the next build.

Apple has repeatedly rejected or iOS app (we have the app on Android as well) for an assumed violation of the IAP guideline. There is nothing to purchase. The app was accepted for almost 3 years without this objection. On the registration screen it said "unlock code" for one field and email for the other. We changed unlock code to User identity and they continued to reject it. I am the point where I may not be employed any longer over the repeated rejections. Each time I have noted the app is free. There is no paid content. This is impacted me, not paid yet, my client, current version is broken on iOS because of a mandatory server API change, and our apps users, who now have a non functioning app. Anyone else run into this, by now seemingly malicious, app review black hole? Did you resolve it?

My In-App Purchase Localizations got rejected and I don't know why they got rejected. I submitted a new build and I submitted my in-app products. I only changed the localizations descriptions for each of my in-app products. The new build got approved and is ready to publish and one day later the in-app purchase localizations descriptions got rejected. I have not yet published my iOS game in the Apple App Store. Can I publish my game even if the localizations descriptions got rejected? Guideline 2.1(b) - Performance - App Completeness Issue Description We have returned the In-App Purchase products as the required binary was not submitted. Next Steps Once you have resolved all the outstanding issues that were identified and are ready to submit the binary, resubmit the In-App Purchase products with the binary.

If I change an app's age rating to a higher age in App Store Connect, what happens to existing installs on devices where users are not of that age? Are parents notified about this via the OS? Are they required to re-approve the app by the OS? Is it the app's responsibility, even though this can be propagated via ASC?

Hi everyone, I’m having an issue where my TestFlight build cannot load auto-renewable subscription products from App Store Connect. The app is built with Flutter and uses StoreKit 2 through an in-app purchase implementation. The same subscription system works correctly on Google Play Billing and returns product details/prices there, but on iOS StoreKit returns no subscription products. I tested this on a real iPhone installed from TestFlight, not from Xcode debug and not using a local StoreKit configuration. The app requests four auto-renewable subscription product IDs. The IDs in code exactly match the product IDs in App Store Connect. The app diagnostics show: Platform: iOS StoreKit mode: StoreKit 2 Store available: true Requested IDs: 4 subscription product IDs Returned IDs: none Missing IDs: all requested product IDs Error source: app_store Error code: storekit_no_response Error message: StoreKit: Failed to get response from platform. Store note: The store accepted the query, but did not return details for these product IDs. Things I have already checked: Product IDs match exactly between Flutter code and App Store Connect Bundle ID matches the App Store Connect app record In-App Purchase capability is enabled Subscriptions are in one subscription group Subscription availability is set for all countries/regions The TestFlight build is installed on a real device Local StoreKit configuration was removed StoreKit reports store availability as true App Store Connect / In-App Purchase keys are configured for backend verification The same product-loading flow works on Google Play The current App Store Connect status for the subscriptions is: Subscriptions: Ready to Submit / Ready for Review Localizations: Prepare for Submission Also, the bank information is not submitted yet. My question is: can StoreKit in TestFlight return subscription product details while the first auto-renewable subscriptions are still only “Ready to Submit” and have not yet been submitted with an app version for review? Or will StoreKit return no products until: The first subscriptions are attached to an app version and submitted for review Subscription localizations are fully prepared/submitted Paid agreements, tax, and banking are fully completed Since StoreKit is available and accepts the product query, but returns zero products, I’m trying to understand whether this is expected App Store Connect behavior or if there is another configuration issue I should check. Thanks.

My Non-Consumable IAP was rejected with Guideline 3.1.1 and now has status ‘Developer Action Required’. The problem: On the version page in App Store Connect, the ‘In-App Purchases and Subscriptions’ section does not appear at the bottom. I cannot link the IAP to a new version submission. Every time I submit a new binary, Apple approves the app version but rejects the IAP afterward — even though I have no way to attach it to the version in the first place. This seems to be a circular issue: the IAP doesn’t appear on the version page because of its current status, but the only way to fix the status is to submit it with a new version. Has anyone experienced this and found a solution? Any help appreciated!​​​​​​​​​​​​​​​​