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

Hi all, We've been rejected four times under Guideline 2.5.2 with identical responses, despite providing detailed clarifications each time. Hoping someone here has dealt with a similar situation. What our app is: A B2B SaaS companion app for our platform (Setgreet). Our customers — product managers and designers — create in-app engagement content (onboarding flows, feature announcements, surveys) on our web dashboard. This companion app lets their teammates and stakeholders view that content on a real device for review and approval before it goes live in the customer's own app via our SDK. The content is structured UI data (text, images, buttons, layout) fetched from our REST API. No executable code, no app binaries, no runtime interpretation, no app distribution. The rejection (verbatim, repeated 4 times): The app appears to be designed for clients or users to preview apps prior to being submitted to the App Store for review. This type of design allows you to change the app's behavior or functionality to differ from the intended and advertised primary purpose of the app, which is not in compliance with App Review Guideline 2.5.2 and section 3.3.2… What we've tried: Detailed written replies explaining the app is a content viewer, not an app preview tool Comparisons to approved App Store apps that work the same way (Figma Mirror, InVision, Braze, Notion — all render remotely-created content via shared links/codes) Filed an App Review Board appeal (waiting for response) Requested a 30-min App Review video call — declined by Apple Each reply gets the exact same rejection text back, with no engagement on our explanations. My questions: Has anyone successfully resolved a 2.5.2 rejection where the reviewer pattern-matched a content viewer as an "app preview tool"? Is the QR-code-to-view-content interaction the likely trigger? Should we de-emphasize it in favor of a login + flow list as the primary UX? Any advice on getting a senior reviewer to actually engage with the explanation vs. copy-pasting the same response? Submission ID: 2f079345-04df-4701-8089-5e55e982f99a Any insights appreciated. Happy to provide more detail. Thanks!

Hi, Like many others here, I applied and paid for an Apple Developer account (April 2). Although I’m certain I used a different account during the process, it appears the payment was linked to an older account that I no longer have access to (specifically, I can’t access the email address associated with it). This means I may have missed any follow-up communication from Apple. Since then, I’ve updated my primary email to one I can access, submitted 3 support tickets, and spoken with Customer Support by phone. Unfortunately, I haven’t been able to resolve the issue. I’ve been told they cannot take action, that I need to wait for them to reach out to me, with no clear outcome — no escalation, no refund, and no concrete guidance on next steps. I’ve also seen mentions of a callback option from the Developer Account team, but I haven’t been able to find or access this anywhere. At this point, my account is still Pending, no response to my support tickets (despite a stated 2-business-day response time), and no clarity on how to proceed—while already being charged $100. I understand this has been asked before, but does anyone have suggestions on what I can do next? Thank you.

We have utilised the KeyChain Framework for Adding items into KeyChain. We have Generated KeyPair using 'SecKeyGeneratePair' API as below (OSStatus)generateAssymetricKeyPair:(NSUInteger)bitSize{ OSStatus sanityCheck = noErr; SecKeyRef publicKeyRef = NULL; SecKeyRef privateKeyRef = NULL; NSString *appGrpIdentifier = @"group.com.sample.xyz" // Set the private key attributes. NSDictionary *privateKeyAttr = @{(id)kSecAttrIsPermanent: @YES, (id)kSecAttrApplicationTag: [TAG_ASSYMETRIC_PRIVATE_KEY dataUsingEncoding:NSUTF8StringEncoding], (id)kSecAttrCanEncrypt:@NO, (id)kSecAttrCanDecrypt:@YES, (id)kSecAttrAccessGroup: appGrpIdentifier }; // Set the public key attributes. NSDictionary *publicKeyAttr = @{(id)kSecAttrIsPermanent: @YES, (id)kSecAttrApplicationTag: [TAG_ASSYMETRIC_PUBLIC_KEY dataUsingEncoding:NSUTF8StringEncoding], (id)kSecAttrCanEncrypt:@YES, (id)kSecAttrCanDecrypt:@NO, (id)kSecAttrAccessGroup: appGrpIdentifier }; // Set top level attributes for the keypair. NSDictionary *keyPairAttr = @{(id)kSecAttrKeyType: (id)kSecAttrKeyTypeRSA, (id)kSecAttrKeySizeInBits: @(bitSize), (id)kSecClass: (id)kSecClassKey, (id)kSecPrivateKeyAttrs: privateKeyAttr, (id)kSecPublicKeyAttrs: publicKeyAttr, // MOBSF-WARNING-SUPPRESS: (id)kSecAttrAccessible: (id)kSecAttrAccessibleAfterFirstUnlock, // mobsf-ignore: ios_keychain_weak_accessibility_value // MOBSF-SUPPRESS-END (id)kSecAttrAccessGroup: appGrpIdentifier }; // Generate Assymetric keys sanityCheck = SecKeyGeneratePair((CFDictionaryRef)keyPairAttr, &publicKeyRef, &privateKeyRef); if(sanityCheck == errSecSuccess){ NSLog(@"[DB_ENCRYPTION] <ALA_INFO> [OS-CCF] CALLED Assymetric keys are generated"); } else{ NSLog(@"[DB_ENCRYPTION] <ALA_ERROR> [OS-CCF] CALLED Error while generating asymetric keys : %d", (int)sanityCheck); } if (publicKeyRef) { CFRelease(publicKeyRef); } if (privateKeyRef) { CFRelease(privateKeyRef); } return sanityCheck; } KeyPair is added into the KeyChain (BOOL)saveSymetricKeyToKeychain:(NSData *)symmetricKeyData keyIdentifier:(NSString *)keyIdentifier { NSString *appGrpIdentifier = [KeychainGroupManager getAppGroupIdentifier]; NSDictionary *query = @{ (__bridge id)kSecClass: (__bridge id)kSecClassKey, (__bridge id)kSecAttrApplicationTag: keyIdentifier, (__bridge id)kSecValueData: symmetricKeyData, (__bridge id)kSecAttrKeyClass: (__bridge id)kSecAttrKeyClassSymmetric, // MOBSF-WARNING-SUPPRESS: (__bridge id)kSecAttrAccessible: (__bridge id)kSecAttrAccessibleAfterFirstUnlock, // mobsf-ignore: ios_keychain_weak_accessibility_value // MOBSF-SUPPRESS-END (__bridge id)kSecAttrAccessGroup: appGrpIdentifier }; // Now add the key to the Keychain status = SecItemAdd((__bridge CFDictionaryRef)query, NULL); if (status == errSecSuccess) { NSLog(@"[DB_ENCRYPTION] Key successfully stored in the Keychain"); return YES; } else { NSLog(@"<ALA_ERROR> [DB_ENCRYPTION] Error storing key in the Keychain: %d", (int)status); return NO; } } Post App Transfer, we are able to retrieve the Public & Private Key Reference without rebuilding the keychain Query:- Is this attribute "kSecAttrAccessGroup" helping us to retrieve the KeyChain items without having to rebuild on App Transfer to New Apple Account as described in this set of guidelines. Could you please explain in detail on this. https://developer.apple.com/help/app-store-connect/transfer-an-app/overview-of-app-transfer Keychain sharing continues to work only until the app is updated. Therefore, you must rebuild the keychain when submitting updates. If your keychain group is defined in the Xcode project, replace it with a group created by the recipient, incorporating their Team ID for continued keychain sharing. After the update, users must re-login once as the app cannot retrieve the authentication token from the keychain.

20 days passed since I released the app. According to Trends it has 30+ installs and 10 In-App purchases. When will I finally get analytics? Can't wait to see it, because I'm actively promoting my app and I wish to know the marketing performance. All that I see now in App Store Connect is this message: Other apps have no signs of this issue, I assume that the analytics is missing because the app is new. The question is "when"? :)

My iOS app is getting repeatedly rejected under Guideline 4.3(b) Spam. Apple says the app is astrology / horoscope category, but the app is actually a B2B partner dashboard for verified consultants and contains no horoscope content. We already: Removed astrology keywords Renamed the app Changed metadata Restricted login Removed China region Explained multiple times to App Review Still getting same rejection again and again. Has anyone successfully resolved 4.3(b) spam rejection for astrology / consultation / marketplace apps? What exact change finally worked? Should we appeal? Request call? Change bundle? New app? Different category? Need expert advice urgently.

I have a submission that has been stuck in “Waiting for Review” significantly longer than expected, while other apps submitted from the same developer account during the same period were reviewed and approved quickly (under 2 days). Current pending submission App Store Connect ID: 6760300948 Waiting for Review - Mar 9, 2026 at 4:50 PM Related history (previous record for the same app functionality) App Store Connect ID: 6759011698 Status history: Waiting for Review - Feb 11, 2026 at 1:22 AM Developer Rejected - Feb 28, 2026 at 10:18 AM Ready for Review - Feb 28, 2026 at 11:31 AM Waiting for Review - Feb 28, 2026 at 11:31 AM Developer Rejected - Mar 9, 2026 at 3:13 PM I withdrew that earlier submission out of frustration after attempting to reduce review friction (first by changing metadata/review notes, then by withdrawing it altogether). The current pending submission (ID 6760300948) uses very conservative metadata and includes demo mode to allow straightforward testing. Can the App Review team check why submission ID 6760300948 is not progressing from “Waiting for Review”, and advise what the problem is or what information is needed to move it forward? Related similar thread: https://developer.apple.com/forums/thread/782319

Hello, My app “DeepTone” has been fully approved and is marked as Ready for Distribution in App Store Connect. However, the app is not available in EU countries due to Digital Services Act (DSA) compliance still showing “In Review”. details: DSA verification was submitted and confirmed as completed by Apple Developer Support (case ID available). App Review has already approved the app. The app is currently live in non-EU regions but blocked in the EU. App Store Connect still shows: Digital Services Act (DSA) compliance – In Review Encryption Self-Declaration (France) – In Review This appears to be a backend compliance status issue rather than an app review issue. Has anyone experienced a similar situation where DSA compliance remained “In Review” after approval? Is there a known escalation path or expected resolution timeframe for this? Thank you for any guidance.

I see a yellow banner on my App Store Connect page with the following message: Apple Developer Program License Agreement Updated The updated Apple Developer Program License Agreement needs to be reviewed. In order to update your existing apps and submit new apps to the App Store, the Account Holder must review and accept the updated agreement by signing in to their account on the Apple Developer website." I am the account owner and I don't see any option to accept the license agreement. I see that the last agreement was signed on 13th December 2021 and it is accepted. I don't see any other agreements anywhere. I am unable to release any apps due to this issue. Does anyone know how to resolve this?

We are stuck in AppStoreConnect limbo. We have a new subscription group + two Subscriptions in Ready To Review state in appstoreconnect, but Apple Review rejected our latest app version because they weren't included with the version. Our app version has been rejected for a few issues before this which maybe broke something. When I go to edit the version, there is no Subscriptions & Purchases section to add them for review. I tried editing the subscriptions and subscription group localization to see if that got it out of Waiting For Review state or showed the version section but no luck. So we can't add the Subscriptions for review and we are rejected from App Review if we don't. I submitted an Apple support email 8 days ago and haven't received any response. Does anyone know of a way to get this unblocked?

Hi everyone, I am facing an issue while configuring an App Clip in App Store Connect, and I am unable to proceed due to a UI crash. Issue When I navigate to the App Clip section under my app version and click on the Subtitle field, the page immediately shows: “We can't process your request.” I am unable to enter any metadata for the App Clip experience. Console Error Previously, I observed the following error in the browser console: TypeError: Cannot read properties of undefined (reading 'appClipDefaultExperience.id')

I've been experiencing two critical issues with App Store Connect for several weeks and have contacted Developer Support multiple times by email with no response. Environment: macOS (Sequoia), tested on Chrome and Safari, multiple devices and networks. US-based organization account. ISSUE 1 — BUSINESS PAGE NOT FUNCTIONING (ongoing for weeks) The Business > Agreements/Tax/Banking page does not work correctly. After filling in all required information and clicking Submit, the page silently refreshes back to the unfilled state. No success message, no error message. This happens consistently across all browsers and devices. The browser console shows the following error on page load: [maison] No route found https://appstoreconnect.apple.com/business/atb/[entity-id] This suggests the SPA router fails to initialize the page, which would explain why submit has no effect. Both my Free App and Paid App agreements are stuck in pending status ("Waiting for Tax/Bank Info"), and I cannot complete the required identity verification through the UI. WHAT I'VE TRIED Multiple browsers (Chrome, Safari) Multiple devices and networks Cleared all cookies and cache Disabled all browser extensions Contacted Developer Support by email — no response after 7+ days IMPACT I cannot launch my paid app because the Paid App Agreement cannot be completed. Has anyone encountered the [maison] routing error on the Business page? Any workarounds would be greatly appreciated.

Hello everyone, We’ve recently noticed an issue with our app’s ratings and reviews on the App Store. Some users have informed us that they left ratings and/or reviews, but these never appeared. Additionally, we’ve observed some reviews disappearing after they were initially visible. We contacted Apple Support, and while they pointed us to the App Store terms and conditions—indicating that Apple has discretion over review removal—we’re trying to determine if there might be a technical reason behind this behavior. Here are some specifics: It has been a while since we’ve seen any new ratings or reviews, even though users have confirmed submitting them. Some reviews that were previously approved and visible have disappeared without explanation. We’ve ensured—to the extent possible—that our app complies with all guidelines and policies, so we’re ruling out violations as the cause for now. Since the app is still new, even a few ratings or reviews missing is quite impactful. Has anyone else experienced similar issues? Could this be related to a known bug or technical limitation? For example, could regional settings, delays in processing reviews, or other factors be affecting visibility? We would greatly appreciate any advice on how to investigate this further or escalate the matter effectively. If you’ve encountered this before, what steps did you take to resolve it? Thank you for your help!

Hi everyone, My app has been rejected twice under Guideline 2.1(b) - App Completeness because the reviewer says the In-App Purchase does not trigger a purchase flow when tapping the purchase button. However, I have tested it on a physical iPhone (iOS 18.6.2) and the StoreKit purchase dialog appears and completes successfully. I have confirmed: Paid Apps Agreement is active In-App Purchase product (non-consumable) is configured correctly Sandbox test account works fine Purchase flow works on physical device with screen recording as proof The reviewer tested on iPad Air 11-inch (M3) with iPadOS 26.4. My app uses Flutter with the in_app_purchase package (v3.2.0). The purchase implementation: Calls InAppPurchase.instance.isAvailable() Queries product details with queryProductDetails() Calls buyNonConsumable() when user taps purchase button I found and fixed a potential null reference issue in the purchase completer that could cause the purchase to fail silently, but I'm not sure if this was the exact cause since I cannot reproduce the issue. Has anyone experienced a similar situation where IAP works on device but fails during App Review? Any suggestions on what might be different in the review environment? Thank you.

Hi everyone, I am experiencing an unusual delay with my app update. I submitted version 1.0.3 of my app, "MarketNow", on March 12, 2026, but it has been stuck in the "Waiting for Review" status for 9 days now. Typically, updates are reviewed within 24–48 hours, so this 9-day wait is quite concerning. I have already sent a formal inquiry through App Store Connect but haven't received a specific update yet. Is anyone else seeing long wait times for updates this week? Could this be related to a backlog before the April SDK deadline, or is there a known issue with the Finance category review queue? Any insights would be helpful. Thanks!

Hello everyone, On my iPad when I press upload to App Store Connect, It tells me uploaded successfully to App Store Connect. When I go to App Store Connect and to Build section, My app is not there. Am I looking in the right place?

I recently turned on the enhanced security options for my macOS app in Xcode 26.0.1 by adding the Enhanced Security capability in the Signing and Capabilities tab. Then, Xcode adds the following key-value sets (with some other key-values) to my app's entitlements file. <key>com.apple.security.hardened-process.enhanced-security-version</key> <integer>1</integer> <key>com.apple.security.hardened-process.platform-restrictions</key> <integer>2</integer> These values appear following the documentation about the enhanced security feature (Enabling enhanced security for your app) and the app works without any issues. However, when I submitted a new version to the Mac App Store, my submission was rejected, and I received the following message from the App Review team via the App Store Connect. Guideline 2.4.5(i) - Performance Your app incorrectly implements sandboxing, or it contains one or more entitlements with invalid values. Please review the included entitlements and sandboxing documentation and resolve this issue before resubmitting a new binary. Entitlement "com.apple.security.hardened-process.enhanced-security-version" value must be boolean and true. Entitlement "com.apple.security.hardened-process.platform-restrictions" value must be boolean and true. When I changed those values directly in the entitlements file based on this message, the app appears to still work. However, these settings are against the description in the documentation I mentioned above and against the settings Xcode inserted after changing the GUI setting view. So, my question is, which settings are actually correct to enable the Enhanced Security and the Additional Runtime Platform Restrictions?

Hello everyone, I’m running into a situation in App Store Connect that appears to be a backend lock related to an approved version, and I’m looking for confirmation or similar experiences. Context: App had version 1.2.6 Version progressed to Pending Developer Release Before releasing to users, I chose Developer Reject I then edited the version number (to 1.2.7) Current State / Issue: After this, App Store Connect is effectively blocked: ❌ Cannot associate any builds to the version ❌ Uploading a build with the same version and higher build number does not help ❌ Cannot create a fresh version (no “+ Version” button is visible) ❌ App Store Connect API returns: ENTITY_ERROR.RELATIONSHIP.INVALID ❌ Remove Version / Delete Version is not available Even attempting brand‑new version numbers does not work. It looks like App Store Connect still considers the previously approved Pending Developer Release version to be active and locked internally. What I understand so far From my understanding: Once a version reaches Pending Developer Release, the appStoreVersion record becomes finalized Editing the version number does not truly create a new version Developer rejection does not unlock the version–build relationship Only one approved / pending version is allowed per app This seems to leave the app in a state where no new versions can be created without backend intervention. Question Can anyone confirm: That once a version reaches Pending Developer Release, it can only be reset or removed by App Store Connect Support, and That there is no self‑service workaround (UI, API, CI, or Transporter) to recover from this state? If anyone has gone through this and successfully had Apple reset the appStoreVersion record, I’d appreciate confirmation or tips on getting it routed correctly. Thanks in advance.

Hi, I received this message recently, but after completing the process and uploading the KRS document for my company in Poland, it doesn’t seem to save. The same message keeps appearing again. I’ve tried around 50 times, but it just loops back to the same step. All agreements, tax forms, and compliance requirements are already active. I contacted the support but no reply. Anyone have any suggestion ?

Hello everyone, I am trying to understand whether this is a normal delay or if there may be an account-level review issue affecting my submissions. I am an individual developer. I submitted my first app for review on March 14, 2026. It remained without a meaningful response until March 31, 2026. During this time, I sent three expedite review requests, but none of them helped. Because nothing moved, I withdrew the previous submission and uploaded a third build for the same app. However, the app is still stuck in review flow. At the same time, I submitted my second app on March 22, 2026. I also requested an expedite review for that app, but it is still in Waiting for Review as well. So currently: • App 1 was first submitted on March 14, 2026 • Multiple expedite requests were sent • The original submission was withdrawn and a new build was submitted • App 2 was submitted on March 22, 2026 • Both apps have been heavily delayed • One is still in review flow, and the other is still Waiting for Review I would like to ask: 1. Has anyone experienced this kind of delay on an individual account, especially with multiple apps at the same time? 2. Could this indicate an account-level issue, manual queue hold, or some kind of hidden review flag? 3. Is there any effective way to escalate this beyond normal expedite requests? 4. Would contacting App Review again help, or is there another correct channel for this situation? 5. If I withdraw and resubmit again, is there any chance that it makes the delay worse? I am not asking for special treatment. I am only trying to understand what may be causing such an unusual delay and what the most effective next step is. Any insight from developers who faced a similar situation would be very helpful. Thank you.

I have submitted my app and it has been waiting for review. I am the owner of the App and I applied for expedited review, but it didn't work. The version we submitted updated the information of the App. We consulted Apple and asked to continue waiting by using "Contact Us". I also submitted the information and they said to wait further. So we can only seek help from the reviewers here. Application ID: d6479289380