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.

My app has been stuck in “Waiting for Review” since June 23, 2026. It has now been 10 days without moving to “In Review.” I have already contacted App Review through App Review Status, but I have not received an update yet. I also checked App Store Connect and do not see any missing metadata, Resolution Center messages, App Privacy issues, Age Rating issues, Export Compliance issues, or missing Review Notes. Is anyone else currently experiencing unusually long “Waiting for Review” times? Also, is there anything else I should check on my side before contacting App Review again?

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.

Hi everyone, I’m currently stuck with a blocking issue in App Store Connect and would really appreciate any guidance or insight. Issue: My app version (iOS App 1.0) is missing the “In-App Purchases and Subscriptions” section entirely. Because of this, I cannot attach my subscriptions to the version, which is preventing me from submitting the app for review. Additionally, I also do not have the option to create a new version, so I can’t work around the issue by moving to 1.0.1. What happened before this: I uploaded a build (Build 24) Submitted the app for review Then removed the submission After that, the IAP section disappeared completely Since then, I cannot attach subscriptions or create a new version Current state: Subscriptions are created and show “Waiting for Review” New Build is attached to Version 1.0 All metadata and screenshots are complete “In-App Purchases and Subscriptions” section is missing “Add Version” option is not available What I’ve tried: Removing and re-adding the build Waiting for UI refresh/processing Contacting Apple Developer Support (case has been escalated for 6 days with no response) Impact: This is currently blocking my app launch because I would be rejected since the subscriptions are not linked, as I cannot submit my first subscription with the app. Questions: Has anyone experienced a missing IAP section after removing a submission? Is there any way to force reset the app version state from the developer side? Is this a known App Store Connect issue? Any help or suggestions would be greatly appreciated. Thanks in advance.

I can sign into AppStore Connect from Chrome, not sometimes in Safari. I get an error dialog that says The operation couldn’t be completed. Unable to log in with account ''. An unexpected failure occurred while logging in (Underlying error code -1001). Apple servers all seem up, so it's just me apparently

I have been rejected twice under Guideline 2.1(b) because my In-App Purchase subscriptions are not submitted for review. I cannot figure out how to attach them to my submission. Here is my situation: I have 6 auto-renewable subscriptions fully configured in App Store Connect under "Barrel Pro Subscriptions" — all have screenshots, pricing, descriptions, and review notes My app is iOS only, built with React Native/Expo My current version is 1.1, Build 10 (1.1.0) The problem: The "In-App Purchases and Subscriptions" section does not appear anywhere on my version page. I have scrolled to the very bottom and it is not there. I cannot find any way to attach my subscriptions to my submission before clicking "Submit for Review." The blue info box on the Subscriptions page says: "Your first subscription must be submitted with a new app version. Select it from the app's In-App Purchases and Subscriptions section on the version page." But that section does not exist on my version page. What I have tried: Cancelling the rejected submission and starting fresh Creating a new version (1.1) manually Uploading a new build (Build 10) Checking both "In-App Purchases" and "Subscriptions" sections in the sidebar Has Apple removed this section from the version page? How do I attach my subscriptions to my submission in 2026? Any help is greatly appreciated. Thank you.

Same here. I have exactly the same issue. App: Stallkoll (Apple ID: 6758069449). Codemagic returns: HTTP 422: Beta contract is missing for the app. Contract is missing. TestFlight shows the latest build as Approved and Ready to Test, but installation fails with: “The requested app is not available or does not exist.” A previous build installed successfully, but all newer builds fail. All agreements, banking, tax information and DSA verification are complete. The build is valid and assigned to the TestFlight testing group. Could an Apple engineer please verify that the Beta Contract is correctly attached to my App ID and re-provision/re-attach it if necessary? This appears to be the same backend issue affecting other developers. Thank you.

Hi App Review team, I'm posting here as a last resort after7 weeks with no movement and 4 unanswered support requests. I'm about to lose my launch window next week and I need someone at Apple to look at this. The situation: App: BMH Themes — App ID 6763770421 — Bundle ID com.bringmedinahome.bmhthemes Version 1.0 (Build 24): reviewed and APPROVED, currently "Ready for Distribution". In-app purchases: 904 are APPROVED, but 1,134 have been stuck in "Waiting for Review" for 7 weeks. The 1,134 stuck items are the exact same type as the 904 already approved — so this is clearly not a content issue. None of the 1,134 show any rejection or "Developer Action Needed" message. Nothing is pending on my side. I have submitted 4 support requests over the past weeks. None received a substantive response. Why this is urgent: My company is now legally registered, my VAT number is being issued, my business bank account is active, and my full marketing campaign is finalized for a launch next week. I cannot launch with 1,134 of my products frozen — releasing a half-empty catalog would waste the entire launch. These stuck in-app purchases are the ONLY remaining blocker. My request: Could someone please check whether these 1,134 in-app purchases are correctly queued, confirm whether there is an internal processing issue, and escalate to the App Review / in-app purchase team? The app is already approved — only these items are stuck. Thank you very much for any help.

We are looking to do affiliate marking for our apps. This is basically where we give influencers a promo code and pay them a fee each time a user signs up with promo codes. Is this possible and within App Store guidelines?

Two weeks in a loop and hoping a staff member can step in. I'm enrolling my company, Zawaya GCC Advertising & Marketing (Kuwait), as an organization. My D‑U‑N‑S Number is active and correct, and the legal entity details match. The problem: when I first submitted, the applicant name and verification contact on the enrollment form were entered incorrectly. Both are locked on the submitted application.. there's no field for me to edit them, and my Apple Account name itself is already correct, so this isn't something I can fix on my side. Instead I'm stuck in an automated loop: I get an email asking me to upload documents, I upload them, and the response comes back that the applicant name and verification contact are wrong and must be changed.. the exact thing I can't change. Upload → rejected for the locked fields → asked to upload again. Two weeks, no progress. What I've already tried: Requested the correction through support multiple times (no action taken) Re-uploaded the requested documents several times Requested a phone callback three times.. held 2+ hours each with no answer My ask is a single, simple one: please withdraw/cancel this pending enrollment so I can start a fresh one with the correct applicant name and verification contact. I'm the company owner and haven't been charged, so re-submitting is no problem on my end. Case Number: 102912899650 Enrollment ID: PXJF4634XK I'll update this thread the moment anything moves. Thank you to anyone at Apple who can take a look.

Hello, I'm building an unreleased game and testing it on both iOS 26.5.2 and iOS 27.0 Developer Beta, and getting the same error when trying to interact with GameKit. It doesn't seem to matter whether the game is deployed directly through Xcode or Testflight. The local player authenticates properly upon booting the game, but when trying to claim an achievement using the following code: try { var inProgressAchievements = await GKAchievement.LoadAchievements(); var gkAchievement = inProgressAchievements.FirstOrDefault(ach => ach.Identifier == "NEW_CASE"); if (gkAchievement == null) gkAchievement = GKAchievement.Init("NEW_CASE"); gkAchievement.PercentComplete = 100; await GKAchievement.Report(gkAchievement); } catch (GameKitException e) { Debug.LogError($"Failed to report achievement {achievement.IOSAchievementID}, error {e.Code} : {e.Message}"); } I get the following error: [Platform] [21.598] Failed to report achievement NEW_CASE, error -1003 : Code=-1003 Domain=NSURLErrorDomain Description=Aucun serveur ayant le nom d’hôte précisé n’a été détecté. Manavoid.Core.<<UnlockAchievement>gDoAsync|0>d:MoveNext() (at ./Library/PackageCache/com.manavoid.core@824a3b70b55f/Runtime/Platform/IOSSubsystem.cs:69) Apple.GameKit.GKAchievement:OnLoadAchievementsError(Int64, IntPtr) (at ./Library/PackageCache/com.apple.unityplugin.gamekit@1ebe01ff0665/Source/GKAchievement.cs:139) [Platform] [21.59859] Failed to report achievement , error -1003 : Code=-1003 Domain=NSURLErrorDomain Description=Aucun serveur ayant le nom d’hôte précisé n’a été détecté. Manavoid.Core.<<UnlockAchievement>gDoAsync|0>d:MoveNext() (at ./Library/PackageCache/com.manavoid.core@824a3b70b55f/Runtime/Platform/IOSSubsystem.cs:69) Apple.GameKit.GKAchievement:OnLoadAchievementsError(Int64, IntPtr) (at ./Library/PackageCache/com.apple.unityplugin.gamekit@1ebe01ff0665/Source/GKAchievement.cs:139) I currently have 18 achievements set up in Game Center. Some of them are still strictly IDs and have no localization data or artwork yet, if that matters. Opening the Game Center overlay in-game works, but I can't see any achievements listed. I did manage to see them once (with missing localization as expected), but I couldn't reproduce it consistently, most of the time Game Center simply says "0 out of 0 achievements". My Testflight build metadata looks like this: ***.app*** application-identifier: **********.com.***.*** get-task-allow: false beta-reports-active: true com.apple.developer.team-identifier: ********** com.apple.developer.game-center: true Help!

Hi everyone, We are facing a critical blocker with our macOS app processing. Since March 5, 2026, every single build we have uploaded (8 builds total) has been stuck in the "Processing" state for over 4 days. For our project, due to the large binary size, processing usually takes about 4 to 6 hours normally. However, we now have a long queue of builds that haven't transitioned to "Ready to Submit" for up to 80+ hours. Stuck Builds List: 1.0.0 (444): Mar 8, 3:09 PM (Processing) 1.0.0 (443): Mar 8, 5:36 AM (Processing) 1.0.0 (440): Mar 7, 6:37 AM (Processing) 1.0.0 (438): Mar 6, 5:01 PM (Processing) 1.0.0 (434): Mar 6, 12:04 AM (Processing) 1.0.0 (433): Mar 5, 6:26 PM (Processing) 1.0.0 (432): Mar 5, 10:51 AM (Processing) 1.0.0 (431): Mar 5, 6:11 AM (Processing) (Note: The last successful build was 1.0.0 (429) on March 4, which processed within the expected 6-hour window.) There have been no changes to our project settings, Info.plist, or entitlements since the last successful build. This is completely halting our scheduled update release. Is anyone else experiencing a similar backlog with large macOS binaries? Or is there a known issue with the App Store Connect pipeline for the macOS platform recently? Any help or investigation from Apple engineers would be greatly appreciated. (Feedback ID: FB22156358)

NB Dev Support ticket has been open for 9 days 102922985821 We are experiencing significant roadblock as macOS app are stuck 'Processing' after uploading. Current 10 days stuck. It's now affecting our release roadmap, and this is even before we have to wait for the usual extended TestFlight and Production review times that exist for macOS (compared to iOS). The .pkg app is uploaded via Transporter. Transporter reports it has uploaded ok, but in App Store Connect shows it is stuck 'Processing'. Subsequent upload has the same effect. Two previous builds for this build number were rejected (Invalid Binary = signing) but have been fixed - we shouldn't have to bump the build number to free the slot to try again... Note there were a flurry of these issues in Jan 2026, but also at least one other ticket now: https://developer.apple.com/forums/thread/818208 Anyone else seeing this, or been able to resolve? Cheers!

Guideline 1.4.3 rejection for a cigar journal app — multiple apps with identical functionality are live on the App Store Hi all, My first submission (a cigar humidor/tasting journal app) was just rejected under Guideline 1.4.3 (Safety – Physical Harm) for "content or features related to the use of tobacco... products." The rejection states the app's concept is "not appropriate because it is focused on these products or activities." The issue: my app doesn't sell tobacco, doesn't facilitate purchasing it, and doesn't encourage consumption any more than a whiskey-tasting log encourages drinking. It's a personal tracking/journal tool — users log cigars they already own, rate them, track humidor inventory, etc. There is no e-commerce, no social sharing of consumption, no promotional content. There are currently multiple apps live on the App Store with functionally identical (in some cases nearly indistinguishable) feature sets: My Humidor – Cigar Journal — https://apps.apple.com/us/app/my-humidor-cigar-journal/id6639582700 Humidor Journal Pro — https://apps.apple.com/us/app/humidor-journal-pro/id6751737114 Ember: AI Cigar Companion — https://apps.apple.com/us/app/ember-ai-cigar-companion/id6761503587 Whiskey and Cigar Pairing — https://apps.apple.com/us/app/whiskey-and-cigar-pairing/id6762530184 Cigarbase: AI Cigar & Humidor — https://apps.apple.com/us/app/cigarbase-ai-cigar-humidor/id6761301449 Leaf Enthusiasts — https://apps.apple.com/us/app/-/id6757314729 Cigar Journal & Tracker: Puro — https://apps.apple.com/us/app/cigar-journal-tracker-puro/id6760948482 ASHD – Cigar Social — https://apps.apple.com/ca/app/ashd-cigar-social/id6759581213 All of these are humidor/cigar journaling or social apps built around cataloging and tracking tobacco products — the exact category my app was rejected for. Several even use AI companion/recommendation features, which is a superset of what my app does. Full rejection text for reference: Guideline 1.4.3 - Safety - Physical Harm Issue Description: The app includes content or features related to the use of tobacco, nicotine-related, or vaping products, including but not limited to cigarettes, pipes, hookahs, or e-cigarettes. Apps with content or features related to consuming tobacco are considered to encourage the consumption of tobacco. Since these products pose a risk of physical harm to users, it is not appropriate to encourage their use. Next Steps: Your app's current concept is not appropriate because it is focused on these products or activities. It would be appropriate to revise the app or submit a new app that is not focused on these products or activities. My questions for the community: Has anyone successfully appealed a 1.4.3 rejection for a tobacco tracking/journal app (as opposed to a marketplace or vaping-hardware app) by citing comparable live apps? Is there a meaningful distinction reviewers are drawing between "journal/inventory" apps and something else, and if so, what specific wording or framing helped get it approved? Is the right move to reply in App Store Connect citing these examples, or file a separate appeal with the App Review Board? Any input from developers who've navigated this — especially in adjacent categories like whiskey, wine, or other regulated-but-legal-consumable tracking apps — would be hugely appreciated. This is my first submission, so I want to handle the response the right way rather than burning an appeal on the wrong approach. Thanks in advance.

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.