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

We recently ran into an issue where our submission was rejected due to references to an API that we are not using but that was present in the code. Guideline 2.5.1 - Performance - Software Requirements Issue Description The app uses the Clinical Health Records API but the app does not appear to include any primary features that require the Clinical Health Records API. Next Steps To resolve this issue, please remove the Clinical Health Records API from the app, as well as any references to this app’s interactivity with Clinical Health Records from the app or its metadata. And as it turns out, we actually did have references to that API that we had missed and did have to remove them. Usually, I would recommend to just resubmit the new build and see if it gets accepted, then hold it until the powers that be approve it for publication. For this client, though, their QA team forces us into more of a waterfall-ish approach, where we are not allowed to submit production builds ahead of time (i.e. until after all manual testing has concluded, test evidence has been filed and the required documents have been updated and approved). And if after resubmission we find something else that needs to be fixed, we get to restart the process all over again. That's ... slower. We do have a workaround in place where we submit a development build for review and check whether that would get accepted, then retract that version and submit the production build once we are allowed to. But that means more work for Apple (the App has to be reviewed twice) and more risk for us (if the submission team accidentally publishes a development build, the consequences would be severe). Is there a tool that allows us to check for guideline violations without having to submit a build to the App Store Connect? I'm not looking for a "yes, this will get approved" kind of guarantee, just a "well, the review team may find something else to question / reject, but as far as automated checks go, this looks ready for submission".

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

I am submitting a new app, so the subscription has to be submitted as part of the overall app review at first, I can't submit it directly on its own. I didn't know this at first, and submitted the subscription directly. It obviously got rejected with the status "developer action needed". Now no matter what I change I cannot seem to get the status to update from "Developer Action Needed" to a more favorable status. This is obviously a problem because until I can get the status to update, I cannot attach it to submit with my app. Any ideas on how to get the status on my subscription to update to "Ready to submit" so that I can attach it with my binary and submit it with my overall app submission?

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

Hi everyone, I’m dealing with a strange App Review delay and would appreciate any advice from people who faced something similar. My app was released on January 20. A small update was approved quickly on January 28, and another one on January 29. So far everything looked normal. Then I submitted another update on February 6. This submission stayed in “Waiting for Review” for 3 weeks with no progress. During that time, I contacted Apple Support to ask if something was wrong with my submission or the review queue. The response took quite a while, and since nothing was changing, I assumed the queue got stuck. So I decided to remove the update and resubmit it. Later Support replied and told me that I removed my own update, and that the queue was working normally and there was nothing I needed to do. However, even after resubmitting, the new build stayed in the same “Waiting for Review” status all the way until March 19 — with no signs of movement. At this point I started to think maybe the review team found some critical issues that would block the app from going live. I rechecked the entire app, didn’t find anything serious, but fixed a couple of small bugs and submitted another update. Unfortunately, this update is now also stuck in “Waiting for Review.” Additionally, I requested an expedited review on April 6, but haven’t received any response or changes in status. So at this point I’m not sure what else I can do. Has anyone experienced something similar? Is there anything that helped you unblock a submission stuck in this state? Any advice or shared experiences would be greatly appreciated.

Has anyone experienced something similar with App Review / App Store Connect? We ran into a very frustrating situation that is now seriously affecting our release and iteration plan. What happened: One of our subscription products was initially rejected on “value” grounds. Although we disagreed with that assessment, we removed that subscription from the latest build in order to move the review process forward. The problem is that the subscription product remained stuck in “In Review” status in App Store Connect. Because of that state, we were unable to edit, remove, or modify it from our side. App Review then rejected the app again under Guideline 2.1(b), saying the IAP attached to the submission could not be found in the binary. So the issue is basically: we already removed the product from the app as requested, but App Store Connect still keeps that product attached to review, and we have no way to remove it ourselves. Then the app gets rejected for exactly that mismatch. We explained this multiple times, attached recordings and backend screenshots, but the responses mostly repeated the same review language and pointed us to contact support. Questions: Has anyone had a subscription get stuck in “In Review” and become impossible to remove? How was it finally resolved? Did Apple manually remove it from the submission, reset the review state, or require you to withdraw and resubmit everything? This has already caused major delays to our release cycle, so any similar experience or practical advice would be greatly appreciated.

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!

Hello, My app has been approved on March 14, 2023 and has the status "Ready for sale" ever since. But the app is still not available on App Store, and whenever i use the link in App Connect to view on App Store it says "App Not available. This app is currently not available in your country or region". Initially I made the app only available in my country, after few days of getting that error, I made it available worldwide but still can't seem to find my app being available. I've sent a support ticket to apple a few days ago but got no reply. In the approval email it said it may take up to 24 hours for the app to be available on App Store, but few days have passed and still not available on app store. The app is free, and i checked all the countries and regions for availability. What can be the problem, how long does it take? Thank you

Hi everyone, I am currently working on automating the renewal process for our managed certificates using the App Store Connect API. However, I've encountered an issue where certificates of the "Apple Push Service" type cannot be retrieved or created. After reviewing the documentation on CertificateType, it seems there is no corresponding type for Push Service certificates. https://developer.apple.com/documentation/appstoreconnectapi/certificatetype Is there any other way or a workaround to obtain or manage these certificates programmatically? Any advice would be greatly appreciated.

Hi folks, I had a similar issue I was able to replicate without fail: Public beta submission fails with: "Beta app contract is missing" POST /iris/v1/betaAppReviewSubmissions returns 422 Error: TF_BETA_APP_REVIEW_RESPONSE Internal TestFlight installs fail with: "The requested app is not available or doesn't exist" Adding apps to beta review also fails I was unable to: Add builds to public testing groups Submit builds for TestFlight review Reliably update TestFlight metadata ("What to Test", etc.) The fix: filed via Feedback Assistant (not Developer Support email). Included a HAR capture of the failing request and response headers, also provided all affected App IDs (even though this was account-wide). Got traction within a couple days after filing, much faster than waiting on Developer Support. Note: In my case this affected every app on the account. From what I’ve seen, this may be triggered by changes to tester groups (adding/removing testers), but this is not confirmed. Seems to be a backend contract/entitlement desync Apple-side. Hope this helps someone.

Hello Apple App Review Team, and everyone, I am in a gap. I cant solve it. 2 days ago I received a copyright claim ref# APP264502-A As a 5 years experienced ASO professional, I choose and position keywords based on volume and relevancy. I didnt know that the keywords was copyrighted. After I received the App Store Notices email, I have took immediate action to prepare a new build to update the app title. I want to remove the copyrighted keyword. Now, because of this copyright claim, Apple put my account under "Pending Termination" status. Don't get me wrong, I can send the app to the review. But this status is blocking the app from going into App Review. Submission ID: 49f886fb-7d5e-4493-b7e8-5e5db2ab1e18 This is where I am stuck. The gap. the loop. I received copyright claim. Okay, of course I will remove your keyword. I need review to change app title. I cant get my app a review. I have created tickets, I replied all of the emails. I need help. This situation makes me stress a lot. I understand that companies or people can get copyrights. I respect that. And I move forward accordingly. I am willing to co-operate. Help needed. Thank you. Best regards,

Hi everyone, I am trying to submit the first version of my app with auto-renewable subscriptions, but I am stuck in a loop. Both of my subscriptions (Yearly and Monthly) are stuck with the status "Developer Action Needed". Because of this status, they do not appear in the list of available In-App Purchases when I try to attach them to my app binary on the App Store Connect submission page. Here is what I have already done/checked: All metadata is filled out (Display Name, Description, Pricing). Review Information is complete (Screenshot and Review Notes are provided). My "Paid Applications" agreement in the Agreements, Tax, and Banking section is Active. I contacted Apple Developer Support by phone, but they were unable to resolve the issue and suggested I post here for help. Has anyone experienced this "limbo" before? How can I trigger the status to change to "Ready to Submit" so I can finally attach them to my build and send the app for review? (I have attached screenshots of my App Store Connect dashboard showing the issue). Thanks in advance for any help!

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.

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')