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

Hello everyone, I’m currently stuck in App Review and would appreciate input from anyone who has dealt with a similar situation. App setup iOS app, SwiftUI, StoreKit 2 No user accounts (no login, no username/password, no backend) No subscriptions Monetization model: App was paid before version 1.0.5 Since 1.0.5 the app is free Unlocking full functionality is done via a non-consumable, one-time IAP (“Pro Unlock”) Existing users who bought the app when it was paid are automatically granted Pro access New users get a 24-hour local trial, then must purchase the non-consumable IAP All state is local / device-based, no server There is no concept of an account, subscription renewal, or expired subscription in the app. Rejection from App Review Apple rejected the app with the following message: Guideline 2.1 – Information Needed We are not able to continue our review because we need access to a demo account with an expired subscription to review the entire purchase flow. Please provide a user name and password for a demo account with expired subscriptions in the App Review Information section of App Store Connect. This is where I’m confused. Why this doesn’t seem applicable The app does not use subscriptions The app does not have user accounts The IAP is non-consumable, one-time purchase Trials are not subscription-based and expire automatically on-device There is no “expired subscription account” that could exist technically StoreKit testing is done via sandbox Apple IDs, but those are: not app-level accounts not usernames/passwords inside the app only used in the Apple purchase sheet Additional complication Because old paid users are automatically recognized as “Pro” via AppTransaction.originalAppVersion, the Unlock Pro button is hidden once Pro is active. This means that on some devices (including mine), the purchase sheet never appears anymore because the app already considers the user entitled. This might be confusing App Review and causing them to assume the app uses subscriptions and gated accounts. Questions Has anyone seen App Review request a demo account with expired subscription for an app that uses only non-consumable IAPs? Is there a correct way to respond other than explicitly explaining that: there are no accounts there are no subscriptions StoreKit sandbox Apple IDs are sufficient? Would providing a sandbox Apple ID (clearly labeled as such) help, or is that inappropriate since Apple reviewers already have sandbox accounts? Is this likely just a misclassification by App Review, or is there something in Apple’s guidelines that I’m missing? What I’ve already tried Explained the purchase flow step-by-step in App Review notes Clarified that the Paid Apps Agreement is already accepted Clarified that Pro access is automatically granted to previous paid users Verified that the IAP is correctly configured and available in App Store Connect At this point I’m unsure whether I should: escalate / push back on the incorrect assumption, or modify the UI to make the purchase path permanently visible even for entitled users Any insight from people who have gone through similar review issues would be greatly appreciated. Thanks in advance.

Hello everyone, I'm currently waiting for my Apple Developer Program enrollment to be approved and wondering if my timeline is normal. My situation: Payment of $99 USD: ✅ Completed (have invoice and order number) Government-issued photo ID: ✅ Submitted Confirmation email received: ✅ Yes - "Thank you for providing the documents we requested. We will review them and follow up with you within two business days" Days since confirmation email: 3+ business days The email stated they would follow up within two business days, but it's now been more than three business days with no update. My questions: Is it normal for the review to take longer than the stated "two business days"? For those who were approved, did you receive multiple emails throughout the process, or just a final approval email? Has anyone experienced similar delays? What was the outcome? Just want to make sure nothing is stuck or requires additional action from my side. Thanks for any insights!

I am getting this issue, whenever I am trying to reconnect XcodeCloud in App Store as the XcodeCloud builds are blocked. Steps we followed Go to App Store Connect -> select app -> select Xcode Cloud -> select build 2 we are able to see error message with connect button Xcode Cloud is unable to connect to the repository “**********”. Reconnect the repository to resume builds. 3. Tapping on connect -> shows a popup with option to authorize in bitbucket -> taping on it, takes us to another window which redirects continuously and nothing happens Can anyone help me with this

Hi everyone, Just wanted to ask if anyone else has noticed longer-than-normal review times recently. Our latest app has been sitting in “In Review” for more than a week now. Normally our apps get reviewed much faster, so we’re unsure if this is just a backlog or something else. Currently: No communication from Apple No visible issues in metadata Review status hasn’t changed Curious to know: • Are others seeing similar delays? • Does this usually mean a deeper/manual review? • When should we reach out to Apple? • How do you usually contact App Review for status checks? Would love to hear your experiences. Thanks!

Hello everyone, I wanted to check if anyone else has experienced longer App Review delays recently. Our recent app submission has been in the “In Review” status for more than 7 days (since Jan 15, 10:44 PM). In our previous submissions, reviews usually started or completed within a few days, so this delay feels unusual. Current situation: No messages or rejection notes from Apple No metadata or compliance issues flagged Status remains “In Review” without updates I’d appreciate guidance from the community: • Is this type of delay normal these days? • Could this indicate a manual or extended review? • At what point should we contact App Review directly? • What is the best way to contact App Store / App Review support regarding a stuck review? If anyone has faced a similar delay and can share their experience or advice, it would be very helpful. Thank you in advance for your help.

I am using Product Page Optimization for the first time and after updating a new app version the test stopped automatically. The status shows developer has stopped with no option to restart the test even though I did not stop it.

Once, the App Store empowered indie creators - small teams could launch great apps and find users easily. But in 2025, that era feels long gone, with algorithms, big players, and pay-to-win discoverability reshaping everything. Is there still a real chance for indie iOS developers today, or has Apple’s evolving ecosystem made independent success nearly impossible?

I’ve observed several areas in iOS where user experience could be enhanced, such as keyboard flexibility, animation speed, biometric options, cache management, background uploads, navigation reliability, and automation features. Addressing these aspects would not only improve usability but also align iOS more closely with diverse user needs across regions and use cases. What enhancements would you consider most valuable?

I want a programmatic way to monitor my app search ranking on the Apple App Store. Is there any API or external website available besides checking directly in the App Store app on iPhone?

Hello, I’m posting here in hopes of getting some help or advice regarding our app submission, which has now been stuck in “Waiting for Review” status for 45 days. We submitted our iOS app on Dec 12, 2025, and since then there has been no movement in the review process. This app is important for our business. The delay is now starting to affect our plans significantly. We called Developer Support, hoping to get some clarity or assistance. Unfortunately, the responses we received were generic and didn’t provide any concrete solutions or timelines. We understand the review process can take time, but 45 days with no progress or transparency feels excessive—especially considering the app was submitted under a developer account that has had previous successful submissions without issue. Here’s a quick summary: • Initial submission: Dec 12, 2025 • Current status: “Waiting for Review” If anyone from the App Review team happens to see this, or if any fellow developers have deal with a similar issue recently and have advice, we would greatly appreciate your insights. This delay is putting real pressure on our timeline, and we’re doing everything we can to resolve it. Thank you for your time and support.

When creating a new App Store version to update ASO keywords and metadata, I notice that elements like the app icon and other details are missing and I am looking for a way to copy the existing metadata from the previous version. Also, is it possible to submit a new App Store version solely for ASO improvements without uploading a new build and still have the changes applied successfully.

I’ve been building iOS apps since 2011 and have worked on hundreds along the way. Recently, I started a series on App Store Optimization (ASO) to share tips, strategies, and lessons learned. In this first post, I dive into how responding to customer reviews can directly influence ASO performance and App Store ranking - covering timing, response style, and best practices to turn negative reviews into positive ones.

Even the best apps struggle to get noticed—over 5 million apps compete in stores, and most never hit 1,000 downloads. Visibility, not quality, is the real challenge. App Store Optimization (ASO) is the key to breaking through. Optimizing your app’s title, keywords, visuals, and description, combined with ongoing testing and competitor analysis, can drastically improve discoverability and downloads in 2025.

I updated the price of subscriptions within an app in App Store Connect, however the new price does not show within the test app. I would just like to make sure that if the app is released that the subscription price is set to the most recent price. Is there any way to confirm that and is there a way to see the new price in the test app?

I want to know if App Store Connect provides daily breakdowns of new 1–5 star ratings rather than just cumulative totals. This would help me track the impact of remotely enabling a feature, but I haven’t found such an option.

Our VPN app on the Apple App Store has seen a slowdown in installs lately. I’d appreciate any suggestions on effective strategies or new tactics to drive growth

Hey All, Last week, I submitted a build of my app with the ability for users to subscribe & receive some extra content in exchange. I wasn't super sold on that being the right path for my app, and when I rightfully received a rejection for missing in app EULA, I decided that I'd postpone monetizing the app and I'd give away that content instead. So, I went ahead and disabled any paths of entry to the subscribe modal & marked the subscriptions as "Remove from Sale" in AppStoreConnect. Additionally, I updated the subscription review notes to be "This is not accessible in app at this time" Sadly, I still got rejected due to missing EULA and the tester being unable to find where IAP's are offered. I'd like to avoid cutting a new build, and instead just remove the subscriptions from being associated with this submission. But, I cannot for the life of me figure out how to remove them! Please help! TLDR: How do you disassociate an IAP or Subscription from an app submission?

Dear Apple, The Apple Developer website and App Store Connect currently remain locked in light mode, which can cause significant eye strain during extended development sessions. It would be greatly appreciated if dark mode — or an automatic system-based appearance option — could be added to make these platforms more eye-friendly for developers. Thank you for considering this improvement.

Hi, Anyone else hitting this App Store Connect issue? I have now submitted two app versions. Both get accepted and I can release them, but the subscriptions are never included. What is happening: App versions get approved normally No “In-App Purchases” section appears on the app version review page Subscriptions page shows subscriptions stuck on “In Review” for 10 days Subscription localization is “Rejected” and completely locked I cannot edit, recreate, or resubmit anything related to subscriptions.. Tried submitting a new app version again, same result. App approved, subscriptions still stuck. So I keep releasing without subscriptions every time 🤦‍♂️ Anyone experienced this or found a way to unblock subscriptions when localization is rejected and locked? Thanks!

Hello everyone, I achieved my MacOs app and distributed for "App Store Connect" and I already have setup the Product In App Purchase in the App Store connect, and I even tested the purchase flow using the local .storekit file using the "Edit Schema". And now, when I remove the edit scema's storekit file and archieved the app and used the Internal testing and installed the app using Testflight, I see that the product is not showing, an empty product array is being returned and there is no option to purchase. I don't want to sumit the full app until I test the StoreKit integration in real test