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

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

Hello, My app (Gezo Gündem, a Turkish news app) has been rejected twice under Guideline 4.2.2 (Minimum Functionality), both times with the same generic template: "the app only includes links, images, or content aggregated from the Internet with limited or no native functionality." For the second submission, I provided detailed App Review Notes listing 8 distinct native iOS features with step-by-step testing instructions for each: A native AI summary modal with native favoriting A native theming engine (5 modes) + dynamic "Club Mode" theming via native state management Native offline article storage using the device's file system (fully functional in airplane mode) A native Text-to-Speech engine reading article content aloud Native push notifications when followed authors publish new content A native source/favorites aggregation dashboard A native pinch-to-zoom newspaper cover gallery WebView is used only to render the body text of individual articles — nothing else in the app relies on it. Despite this, the second rejection used the exact same template language, with no reference to any of the listed features. I've since replied via Resolution Center asking the reviewer to re-test following the specific steps in the notes, but I'm unsure if this is the right channel to get a reviewer to actually engage with documented native functionality rather than reissue a template rejection. Has anyone successfully gotten a reviewer to revisit a 4.2.2 rejection by providing this level of detail? Is there a more effective way to ensure the review notes are actually read before a decision is made? Any guidance would be appreciated. Thanks.

Hi, Since today I'm unable to stay logged in to App Store Connect. Every time I click on an app, it immediately redirects me back to the login page. Things I've already tried: Cleared cookies and cache Multiple browsers (Edge, Safari, Chrome, incognito mode) Mobile app Different network (WiFi and mobile data) Checked appleid.apple.com — no suspicious devices or logins Apple System Status shows everything green. No account changes were made recently. Is anyone else experiencing this today? Could this be an account-level session issue? Thanks

Hello, I'm developing a Capacitor/Next.js iOS app with RevenueCat for auto-renewable subscriptions. On a real iPhone via TestFlight, StoreKit never returns my subscription products, so the Apple payment sheet never appears. App TestFlight builds tested: 110, 111, 112 (iOS 1.1.0) In-App Purchase capability enabled on App ID Paid Applications Agreement: active Banking/tax: active Subscription product IDs (auto-renewable, same subscription group) vytalai_premium_monthly vytalai_premium_yearly vytalai_premium_yearly_intro (exit offer) What happens Install app from TestFlight on physical iPhone Navigate to paywall App calls RevenueCat → Purchases.getProducts() with the 3 product IDs above StoreKit returns 0 products (or configure/getProducts times out) UI shows: "Apple Store: 0 subscriptions on this device — Sandbox popup cannot open" Tapping subscribe does not open the Apple payment sheet Fallback prices appear (3.49 / 29.99) instead of live App Store prices (3,49 € / 29,99 €), which suggests StoreKit is not returning products. What we already verified Correct bundle ID in build metadata NEXT_PUBLIC_REVENUECAT_API_KEY_IOS (appl_*) embedded in EAS production build Provisioning profile regenerated and active Subscription metadata corrected (was Rejected, now Waiting for Review) All 3 subscriptions attached to app version submission RevenueCat offering "default" with monthly, annual, and annual_intro packages App Store Server Notifications URL configured to RevenueCat Legal pages open in-app (no external cookie banner on native) Testing on TestFlight only (not Safari/web) App Review context We received Guideline 2.1(b) rejections because: Error on purchase page Exit offer (50% OFF / €1.91 per month equivalent) referenced product vytalai_premium_yearly_intro which was not submitted for review initially — now added and submitted with the app version. Question Even with subscriptions in "Waiting for Review" state and metadata completed, should StoreKit Sandbox/TestFlight return these products on device so we can test the payment sheet before approval? If not, what exact App Store Connect state is required for StoreKit to return products on TestFlight? Any guidance on why getProducts would return 0 for valid product IDs on a TestFlight build would be greatly appreciated. Thank you.

StoreKit getProducts returns 0 subscriptions on TestFlight for product IDs vytalai_premium_monthly, vytalai_premium_yearly, vytalai_premium_yearly_intro (bundle com.ciborgu.vytalai, build 112+). All metadata submitted, Paid Apps Agreement active. Please check why Sandbox catalog is empty for this app.

Hi everyone, I'm hoping someone from Apple or a senior community member can help escalate my situation. About four weeks ago, I received a termination warning on my developer account related to an app called Checklist Buddy (originally named Cessna Checklist Buddy). I renamed it after realizing I didn't have formal written permission from Textron Aviation, even though I had verbal approval. I believe that name change — or possibly code similarity between apps — may have triggered a flag. I have three apps on the store: WIB 26, Checklist Buddy, and Pure International 2026. WIB 26 is live and functioning fine. Pure International 2026 is the critical one — it's an event app for a pageant happening next week and delegates are counting on it. I have submitted multiple appeals and tickets over the past four weeks with zero acknowledgment from Apple. Last week I called Apple Support and spoke with a representative. He pulled up my account and confirmed there were notes showing an appeal on file, but no reason whatsoever was documented for the termination warning — even he couldn't see why. He escalated my case to a senior advisor and told me I would hear back within 3 business days. It has now been 7 days with no contact. I understand Apple has a high volume of cases, but this is affecting my livelihood. I have a real event with real attendees next week who need this app, and I cannot distribute it or push updates because my account is in a restricted state pending this appeal. If any Apple staff reads this — my case has been escalated to the senior advisor team and is sitting in an email queue. I just need a resolution or at minimum a reason for the original warning so I can address it properly. Any advice or help from the community is also appreciated. Thank you.

I submitted an update for my app 7 days ago and it's still sitting in "Waiting for review". This isn't a new app submission—it's an update containing important bug fixes that users are waiting for. I've already contacted Apple Review to ask about the situation and request assistance, but so far I haven't received any update/reply. What makes this even more frustrating is that I've submitted other apps after this one, and those apps were reviewed and approved first. I genuinely don't understand how the review queue works if later submissions can move ahead while an older submission remains untouched. The delay is causing real damage: Users are leaving negative reviews for bugs that have already been fixed in the pending update. Some subscribers have canceled because they assume the issues aren't being addressed. The app's rating and reputation are taking a hit while the fix is effectively locked behind the review process. I'm attaching the email I sent to Apple Review. Has anyone else experienced unusually long review times recently? Have you found any effective way to get visibility into what's causing the delay? I'd be interested to hear whether this is an isolated case or if other developers are seeing the same thing.

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.

Hi everyone, I recently launched my app, when searching for the app on Google, the official App Store link that appears in the search results is from the Chinese App Store. My app's primary language is correctly configured in App Store Connect, and I would naturally expect the search result to display in that primary language, or at least default to English. Has anyone else experienced this issue where Google indexes the wrong regional App Store page (e.g., pulling a Chinese localization instead of the global or primary one)? Is there a specific setting or metadata in App Store Connect I need to double-check to force the correct locale, or is this purely a Google crawling anomaly that usually resolves itself over time? Thanks in advance for any insights!

Our app submission has been in "Waiting for Review" status for 8 days after another 8 days before that with no review. Typical review time is 24–48 hours, so this appears to be stuck. We have not received any communication from App Review during this period and there are no outstanding items in App Store Connect. Could a member of the App Review team please check the status of this submission? App Name: Blingz App ID: 6759068218 Bundle ID: com.apperfun.hub Version: 1.39.1 Submission ID: 381c3dce-68f5-426b-b6de-807f513d370f Submission Date: Jun 13, 2026 Support Case ID: 102915835489 Thank you.

A couple months ago, I got an error when attempting to deploy our app to App Store Connect (see error further below). I used the CLI command xcrun altool --upload-app, and I was trying to upload a new version 1.0.26 build 0, when the previous uploaded version was 1.0.25 build 2 (so the new version is definitely a higher number). I later tried to upload a version 1.0.27 build 1, and that still failed. Note that I have an identical staging app, and I was able to go from 1.0.25 build 2 to 1.0.26 build 0 just fine there. And I have never had issues with version incrementation in the past for either our production or staging app. What could be going wrong here? Here are the error logs: 2026-04-30 23:18:19.430 ERROR: [ContentDelivery.Uploader.6000012404C0] The provided entity includes an attribute with a value that has already been used (-19232) The bundle version must be higher than the previously uploaded version: ‘0’. (ID: 71a9077b-807a-476c-b8a2-04cb8357bc32) NSUnderlyingError : The provided entity includes an attribute with a value that has already been used (-19241) The bundle version must be higher than the previously uploaded version. status : 409 detail : The bundle version must be higher than the previously uploaded version. Failed to upload archive at '[MyApp].ipa'. source : pointer : /data/attributes/cfBundleVersion id : 71a9077b-807a-476c-b8a2-04cb8357bc32 code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE title : The provided entity includes an attribute with a value that has already been used meta : previousBundleVersion : 0 previousBundleVersion : 0 iris-code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE 2026-04-30 23:18:19.431 ERROR: [altool.6000012404C0] Failed to upload package. 2026-04-30 23:18:19.431 ERROR: [altool.6000012404C0] The provided entity includes an attribute with a value that has already been used (-19232) The bundle version must be higher than the previously uploaded version: ‘0’. (ID: 71a9077b-807a-476c-b8a2-04cb8357bc32) NSUnderlyingError : The provided entity includes an attribute with a value that has already been used (-19241) The bundle version must be higher than the previously uploaded version. status : 409 detail : The bundle version must be higher than the previously uploaded version. source : pointer : /data/attributes/cfBundleVersion id : 71a9077b-807a-476c-b8a2-04cb8357bc32 code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE title : The provided entity includes an attribute with a value that has already been used meta : previousBundleVersion : 0 previousBundleVersion : 0 iris-code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE

Hello, I am the developer of Kodogram, an educational programming platform that allows users to learn, inspect, edit, and execute code. My app was rejected twice under Guideline 2.5.2 despite the fact that all executable source code is fully visible and editable by users before execution. According to Guideline 2.5.2, educational apps may download code provided that: The code is used solely for educational purposes. The source code is completely viewable by the user. The source code is editable by the user. Kodogram is designed specifically for programming education. Users can learn, inspect, edit, share, fork, and test source code written in multiple programming languages, including HTML, CSS, JavaScript, Python, C, C++, C#, Java, PHP, and others. In the application: Users can view the complete source code before execution. Users can edit the source code before execution. Users can create forks of shared projects and modify them. Users can test and learn code written in multiple programming languages. Code execution occurs only after the user has reviewed and optionally modified the source code. During the review process, Apple attached a screenshot showing only the final "Run Output" screen. In response, I provided additional screenshots demonstrating: Complete source code visibility before execution. Separate source code views for HTML, CSS, and JavaScript examples. The code preview/editor screen where users can review and modify code. The final output screen shown only after the code has been reviewed and executed. The attached screenshots use HTML, CSS, and JavaScript as examples, but the same workflow applies to all supported programming languages within the platform. My question is: Has anyone experienced a similar Guideline 2.5.2 rejection for an educational coding application where the source code was already fully visible and editable before execution? Is there any additional requirement, documentation, or implementation detail that App Review may expect beyond demonstrating that source code is completely viewable and editable by the user prior to execution? Any guidance or shared experiences would be greatly appreciated. Thank you.

大家好， 想请教一下是否有开发者遇到过类似情况，并愿意分享处理经验。 假设某 App 收到第三方发起的知识产权投诉（例如图片、字体、素材等相关内容）。 开发者收到投诉后已经： 完成内部核查； 删除或替换了被投诉内容； 发布整改版本； 当前 App 及相关线上服务中已无法访问被投诉内容。 但投诉方认为双方争议并未解决，并持续基于历史使用行为提出异议或再次发起投诉。 想了解大家是否遇到过类似情况： 开发者完成整改后，Apple 是否曾针对同一事项再次联系过你们？ Apple 是否要求过额外材料，例如整改说明、授权证明或其他补充文件？ 如果当前版本和线上服务已经无法访问被投诉内容，Apple 在后续处理中通常更关注哪些方面？ 有没有开发者遇到过已经完成整改，但仍然因为同一事项被进一步处理甚至下架的情况？ 对于这类已经完成整改、但双方仍存在历史争议的问题，Apple 后续通常是如何处理的？ 我理解每个案件情况不同，也理解 Apple 会根据个案进行评估。 这里只是希望了解其他开发者的实际处理经验，以便更好地理解 App Store 在知识产权投诉方面的一般处理方式。 感谢大家分享经验。

Hi all, We can’t install our app from TestFlight. The app is visible in TestFlight for invited internal testers, but tapping Install fails immediately with: “The requested app is not available or doesn’t exist.” --Setup-- Distribution: TestFlight – Internal Testing Internal group created and testers added (invite accepted) Build processing status in App Store Connect: Complete TestFlight build status shows: Ready to Submit / Prepare for Submission Minimum iOS deployment target: iOS 15.0 Version/Build: 1.0.0 (1) What we tried Confirmed tester is signed into TestFlight with the same Apple ID email that was invited Removed/added testers to the internal group and resent invites Reinstalled TestFlight, signed out/in Verified build is assigned to the internal group Set and saved Monetization → Pricing and Availability → App Availability (All Countries/Regions) Question Has anyone resolved this issue? Is there a known TestFlight/App Store Connect stuck state that causes this error even for internal testing? Any recommended steps (new build number, group reset, availability/pricing settings, etc.)? Screenshots available (TestFlight error + App Store Connect build/group view). Thanks.

I need to delete permanently an app bundle, or at least remove the apps from it, to be able to delete those apps. How to do it?

So I know apple store connect are strict in term of your app screenshots, you cannot insert some promotional video and you cannot insert any screenshot that does not come from an iphone or official simulator. But I saw earleir someone's app with a screenshot that was like "MOCK" type, it has some 2 sentence description on top and below them the actual screenshot (on a phone simulation mockup lets say). This got me thinking that apple store connect actually tolerate images that are not PURE screenshots? You can actually take screenshots insert them to mockup and then insert that image in app store connect? How to do that and more importantly what to do to make sure it is done in a way apple store connect accepts it? What others things can be done, or best practices?

Hi everyone, I am currently completely blocked from submitting my new app for TestFlight Beta Review (External Testing). The App Store Connect web interface fails to submit, and when I try to bypass the UI using the App Store Connect REST API to create a betaAppReviewSubmissions request, Apple's servers return the following 422 error: { "errors" : [ { "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Here is what I have already checked and verified on my end: Agreements, Tax, and Banking: My "Paid Apps Agreement", "Free Apps Agreement", "U.S. Tax Forms", and "Bank Accounts" all clearly show as "Active" status. There are absolutely no pending banners or unaccepted agreements on developer.apple.com or appstoreconnect.apple.com. Apple Developer App: I logged into the official iOS Apple Developer app with the Account Holder ID, and there are no hidden agreements to accept there either. App Privacy: All data collection questions are answered, and the App Privacy section is fully Published. Test Information: All required Beta App Review details (Name, Email, Phone) are correctly filled. Export Compliance: My Info.plist includes <key>ITSAppUsesNonExemptEncryption</key><false/>, and the build attributes confirm it. It appears that my TestFlight beta contract has somehow become detached, bugged, or failed to provision on Apple's backend. Has anyone experienced this specific API error recently? Is there a way to force the system to re-provision the contract, or does this strictly require manual intervention from an Apple Engineer? Any guidance would be highly appreciated. Thanks!

Hello App Review Team, My team's first app submission has been in "Waiting for Review" status for 17 days with no movement, and I would appreciate any visibility you can provide on its current state. Submission details: App name: Motor İzleme Submission ID: fb2151a2-969e-458b-b57b-9fc7a982e168 Submitted: May 20, 2026 at 10:24 PM Version: 1.0 (build 2) Current status: Waiting for Review (17 days) Account type: Organization (first submission under this account) About the app: Motor İzleme is a hardware companion app that communicates with our physical device over Bluetooth Low Energy. Because reviewers cannot physically test the device without the hardware, we have provided the following materials with the submission to support the review: A demonstration video showing the full app-to-hardware interaction (linked in App Review Notes) Detailed App Review Notes explaining the BLE communication flow App screenshots covering all primary screens Clear handling of the no-device state (the app does not crash or hang — it shows appropriate prompts when Bluetooth is off or no device is found) I want to be transparent: I am not requesting expedited review and I understand the team is operating under heavy submission volume in 2026. I am simply asking whether this submission may have been overlooked, or whether there is anything additional I can provide to help the review proceed. This launch is tied to a commitment with our business partner, and the extended delay is beginning to impact business obligations on our end. Any update would be greatly appreciated. Thank you for your time. Best regards, Saadettin Yıldırım

I am using CI/CD method to build my apps, i dont have xcode simulator, so I cannot produce 13'' screenshots And I have an ipad that is NOT 13'' what can I do? I am locked out from releasing on ipads?

Hi everyone, I’m facing a frustrating loop trying to access App Store Connect and wanted to see if anyone else has encountered this or found a backend fix. The Problem: On Web (Chrome & Safari): When navigating to App Store Connect (specifically the Apps console or Users and Access), the page loads completely blank/white. On iOS App: Attempting to log into the official App Store Connect app using the exact same Apple ID results in a "Developer Account Required (Error 2002)" message. What I've already tried: Clearing browser cache, cookies, and using full Incognito/Private mode. Disabling all ad-blockers and extensions. Trying completely different devices (Mac and iPhone). Since it happens across all devices and browsers for the exact same account, it looks like a provisioning or synchronization bug on Apple's backend. Has anyone managed to resolve this without waiting weeks for senior engineering support? Any advice would be highly appreciated.

I need to check for which countries the app is available. The "pricing and availability" option is missing. Th "add a new version" + sign is missing as well. What should I do?