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

I submitted my iOS app for review with the "On Hold" status, but I uploaded the build using an older SDK version. According to the guidelines, starting April 24th, apps need to be built with the updated SDK. If my app is approved and ready for release, will I be able to release it after April 24th, even though it uses the older SDK? Also, how long can the app remain in the "On Hold" status before I need to take further action?

Dear Apple Developer Community, I am facing an issue where my Flutter app build is not appearing in App Store Connect after a successful upload. Issue Details: I archived and uploaded my app using Xcode without any errors. The build appears under my app in App Store Connect. However, when I go inside the Build section to select it for submission, there is no build available. The message displayed: "If your app uses encryption, you're required to upload export compliance documentation..." I already completed the encryption compliance but the build still does not show up. I uploaded images/screenshots, yet the issue persists. I waited over 3 days, but the build has not appeared. Environment: Xcode Version: Latest macOS Version: Latest Flutter Version: Latest Has anyone else encountered this issue? Is there any workaround or additional step required? Any guidance would be greatly appreciated. Thank you in advance!

I've seen other similar posts with no clear answers and solutions. My Unity app has been rejected several times with this message: The UIRequiredDeviceCapabilities key in the Info.plist is still set up in such a way that the app will not install on the device used in review. Review device details: Device type: iPhone 13 mini OS version: iOS 18.4 Next Steps Please check the UIRequiredDeviceCapabilities key to verify that it contains only the attributes required for the app features or the attributes that must not be present on the device. Attributes specified by a dictionary should be set to true if they are required and false if they must not be present on the device. I have made sure the submitted app has only one value for UIRequiredDeviceCapabilities, arm64, which is required by Unity. Initially Metal was listed as well, but I've removed it in trying to fix this problem. Additionally, I've ran the app through TestFlight and it functions fine. I'm not sure what else to try to fix this issue, though I've seen from other posts that indicate this type of rejection could possibly be a bit of a red herring and the real issue could be something else. Any help would be appreciated

Lately TestFlight has been having unexpected delays for me. For context, I have an app that I am just testing internally right now, so whenever I have a new build the process I follow is: Upload build to App Store Connect Wait for build to finish processing (typically less than a minute) Add compliance info in App Store Connect Wait for build to be distributed via TestFlight For the last few months, after I entered the compliance info, my app would be available for TestFlight distribution almost immediately after I entered the compliance info. I would get the email notification and I could see my new build on TestFlight. I am getting the notifications from App Store Connect that my build has completed processing within a minute or two of uploading it. Then, I enter the compliance information in App Store Connect. Lately, it has been taking multiple hours in between when I provide the compliance info and when the new build is available on TestFlight though. So there is a seemingly random time period in between when I enter the compliance information and when the app is actually distributed to TestFlight. I am not sure why this process that used to be immediate now has multiple hours of lag. There also does not appear to be any way for me to manually check on the status or anything. After I enter the compliance info, it is an entirely hidden and automated process to then push that build out to TestFlight. Is there anything I can do to improve this, or are there any known causes for this issue? I have tried re-submitting another new build version to try and "flush the pipeline", and that worked once before, but it doesn't appear to be working anymore.

I'm having issues with StoreKit 2 when trying to load my auto-renewable subscriptions on a physical device via TestFlight. It works perfectly in the simulator using a local .storekit configuration file, but when I install the app through TestFlight, StoreKit does not return any products at all. Instead, I get the error: "Storefront not available" What I've Tried: ✅ In-App Purchases are enabled on my device. ✅ Using a sandbox account (confirmed logged in under Settings &gt; Developer &gt; Sandbox Account). ✅ The app is signed correctly with automatic signing in Xcode. ✅ The product IDs are correct (they work in the simulator with the local StoreKit file). ✅ I enabled SK2DebugLogging, but I don't see detailed errors. ✅ Restarted the device and signed out/in of my sandbox account. ✅ Checked that the App Store region matches my sandbox account’s region. ✅ The app is not fetching products dynamically at all on a real device—just getting "storefront not available." Additional Notes The app is installed via TestFlight, not running in debug mode from Xcode. The app is signed in to the App Store with a real Apple ID (not the sandbox one). Apple confirmed that products don’t need to be "Ready for Sale" for sandbox testing. I checked the Console.app logs on my Mac, but nothing obvious showed up. What I Need Help With Why would StoreKit 2 fail to return products in TestFlight, but work fine in the simulator? What does "storefront not available" actually mean in this context? Any steps I might have missed to force StoreKit to fetch products properly? Any help would be greatly appreciated! 🚀

I noticed a very weird behavior for refunds. When a user refunds an up-front paid app, they still have access to the app. How can I detect such a case and block access to the app? In general, I think it should be handled by Apple, but for some reason, they don't do it.

I just spent way too many hours trying to figure out why my in-app subscription was stuck in “Missing Metadata” in App Store Connect, even though I had filled out everything. If you're here because you're in the same boat, this is the solution Apple doesn't make obvious. The Problem I created an auto-renewable subscription (Kanabloom Premium) and filled in all required fields. The subscription was still marked "Missing Metadata", preventing me from submitting it. The “In-App Purchases” section wasn’t showing up in my App Store version submission, which meant I couldn't even attach the subscription to my app version. I triple-checked the metadata, pricing, tax settings, review screenshot, and even resaved everything, but nothing worked. What I Tried (Before Finding the Fix) Checked that pricing was set up correctly for all countries. Uploaded the required review screenshot for the subscription. Made sure the subscription group existed and was linked properly. Refreshed, logged out/in, and tried different browsers. Read every Stack Overflow, Reddit, and Apple Developer Forum post I could find. Even tried creating a dummy subscription to see if that would reset the system. The Solution: Localizing the Subscription Group Here’s the stupidly hidden requirement that finally fixed it: ✅ Your subscription group itself (not just the subscription) needs a localized display name. App Store Connect requires each subscription group to have at least one localized display name for it to be valid. If this is missing, all subscriptions inside that group will stay stuck in “Missing Metadata” no matter how complete they are. How to Fix It: Go to App Store Connect > Subscriptions > Subscription Group Click on your subscription group (not the individual subscription). Check if there's a localization added under "Group Reference Name." If missing, add a localization (e.g., English) and save. Refresh the page and boom – the subscription will finally be "Ready to Submit." Conclusion Apple really needs to make this requirement clearer. Now that I’ve finally figured it out, hopefully, this post helps someone else avoid losing hours of their life to the same issue. If you're still stuck, double-check that: You’ve set pricing and enabled "Cleared for Sale." You’ve uploaded a review screenshot for the subscription. You’ve signed all App Store agreements and banking/tax documents. Your app's In-App Purchase capability is enabled in Xcode. Let me know if this helped you! I wish I had found a post like this sooner. 😂 This should make for a useful and searchable post in case other devs run into the same headache. Let me know if you want any tweaks before posting! 🚀

I just started with App Clips so quite new to it. One of our dependencies is very big in size (85+ MB) which is making the app size almost 87MB's uncompressed and 40MB's compressed with just this dependency and no other app clip related code in it. I created a App Thinning size report for the app clip and even with bigger app clip size, I decided to upload the beta build to App Store Connect for testing purposes. On App Store Connect, app clip size is 70+ MB and to my surprise it passed the App Store Connect review and I was able to install this app clip on my device from Test Flight. If I add functionality to the app clip with this bigger dependency SDK, then the app clip size is going to increase further and am worried that it could get rejected when I push it to app store. Minimum iOS version of the app is 16.4, so my understanding is that the maximum app clip size allowed is 15MB. Am trying to figure out, how the app clip build was approved on app store connect and if dependency sizes in app clips are ignored? Attaching screenshot of App Thinning report and screenshot of App Store Connect build with this App Clip.

CONTEXT: iOS: 18.2.1 || macOS: 15.4 || Xcode: 16.2 || App status: Not yet released || In-app purchase type: Subscription || App version: 1.0, Build 3 ISSUE:
 App Store Connect has rejected our latest app submission with the instructions “…submit your in-app purchases and upload a new binary in App Store Connect…”. Unfortunately, the required "In-App Purchases and Subscriptions" section is missing from the ‘version page’ of our submission. This is further complicated by the fact that we had already tested the subscription in App Store Connect’s sandbox, where it successfully returned the non-domestic storefront pricing for Hungary (HUF1,490.00/year). After reviewing nearly four dozen Apple pages of documentation and a dozen Apple forum posts, we found only one relevant link: https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-for-review Unfortunately, the instructions under the disclosure triangle: "Submit an in-app purchase for the first time" confirm that the "In-App Purchases and Subscriptions" section is missing from our version page. Additionally, review of the blue warning box on the Subscription page includes the following instructions: "…Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page…" Unfortunately, this section does not exist on our version page, confirming that there is no specific section labeled "In-App Purchases and Subscriptions" available. Similar issues have been reported by other developers. See this Stack Overflow thread for additional context: https://stackoverflow.com/questions/73098652/app-store-connect-in-app-purchase-and-subscriptions-section-missing HISTORY: Successfully created and sandbox tested the subscription in App Store Connect. Reviewed over five dozen pages of Apple documentation and forum posts as well as Stack Overflow. Have repeatedly loaded and checked the 'version page' for the "In-App Purchases and Subscriptions" section, which is unfortunately missing from our submission. QUESTIONS: Where is the "In-App Purchases and Subscriptions" section located, if not on the 'version page' of our submission? Is there an alternative method to submit in-app purchases and upload a new binary in App Store Connect? Do we need to remove any part of the submission to access the "In-App Purchases and Subscriptions" section? What is the risk of losing our app name 'Concensus' in the Apple App Store if we delete any portion of the submission? We would appreciate guidance on how to proceed with submitting our in-app purchase subscription along with our new app version. Grateful Indeed.

Is anyone else having an issue where you’ve deployed your build, and its has been approved (marked to available for testing) but when you share the public link, add a new tester, or even just add an internal tester it doesn’t let you?

Dear Apple Developer Community, I have been facing repeated 4.3 Spam rejections for my game on the App Store, and I am struggling to understand the reason behind it. My game is a multiplayer racing and drifting game, fully designed and developed from scratch. Every aspect—including UI, 3D assets, game mechanics, and netcode—has been built independently. While I have used some paid assets, they are strictly for visuals only (such as models and textures), not game templates or code templates. Additionally, these assets have been significantly modified to fit my game’s unique style. To address the rejection, I have made numerous changes—some major and some minor—including: Modifying gameplay elements Adjusting UI and mechanics Updating the App Store listing (title, screenshots, description, and category) Despite these efforts, I continue to receive the same 4.3 Spam rejection. I have also tried to appeal multiple times but have not received any response. My game is categorized under Racing and Simulation (with Racing as the main category), but I even tried submitting it under just Games without subcategories—yet the rejection persists. I’m truly frustrated and unsure what else I can do to resolve this issue. If anyone has faced a similar situation or has any advice on how to proceed, I would greatly appreciate your insights. Thank you in advance!

I archived and distributed a new version of my app (with new build number) and it shows up in the Appstore connect (no issues here). But the new version doesn't show up in the Testflight app, nor did the internal testers receive any email regarding the new update. I have waited for 3 hours now, and still no progress on this. This issue is happening out of the blue. The whole process was working fine yesterday. I did a couple of things to debug this issue, along with: Changed build version couple of times Reset provisioning profile Created new testing group, added users, added build manually No matter what I do, I'm unable to get the new version of the app to show in the Testflight app for my internal testers. I have also contacted apple support via email, waiting for their response. Any help appreciated! Thanks

I have a new, unreleased app in App Store Connect. The Mac app icon is a rounded rect with transparent border. For some reason, the "Included Assets App Icon" has a black background in App Store Connect. The black background also appears in the TestFlight app. The issue doesn't appear to be specific to the new app's icon, because I tried uploading a build with another icon, from an already released Mac app, and App Store Connect also gave that a black background. The app icon displays correct at runtime on macOS. The black background is a phenomenon only of App Store Connect and TestFlight. My theory is that App Store Connect is confused and still treating the app icon as if it were iOS rather than Mac. During development, the app has gone through a transition: first it was iOS on Mac, then it was Catalyst, and now finally it's AppKit. If the App Store Connect record for the app has some kind of iOS or Catalyst flag, I have no idea how to reset the flag. Has anyone else experienced this issue?

Hello Developers! I am trying to run a test In-App Purchase (IAP) for a renewable subscription product in the sandbox environment. I have set up everything required for sandbox testing, but it’s unclear whether the subscription product needs to be pre-approved by Apple for testing. If approval is required, I have already added the necessary metadata, but the status still shows "Ready for Submit." Additionally, when I save the page, a "Submit for Review" button briefly appears for a fraction of a second on the subscription page before disappearing. Is this button missing, or is there a known issue with this process? This is my first time running this test, and I would appreciate any pointers or suggestions. Thanks!

Hi everyone, I am working on a Unity iOS app. I am adding in-app purchasing in my app. I have added Unity IAP to the Unity project, as well as the code for initialising and purchasing a subscription with the product ID. I have also added my certificates and provisioning profile in Xcode with in-app purchasing capabilities. Also, I have set up an App Store Connect page with a non-renewing subscription with a unique product ID and all required information. The subscription status is ready to submit. I have added a sandbox tester account in it. In unity editor, it is working fine with fake purchase receipt. While testing in an iOS device, apple ID is logged out. But there is an error occurs everytime : IAP not initialized. Also I have uploaded a newer version of app on app store connect, it is in waiting for review status. Is there any step or something I am missing that it is not working in iOS device? Please help

We set up monthly subscription with a 1-month free trial. We tested it with Sandbox and TestFlight, and the subscription worked as expected. The app is now available on Apple Store, but the monthly subscription is changed to One-Time Charge on Apple Store. When we try to download our app, it asks One-Time Charge with the cost of the subscription fee before downloading the app. However, in our testing, the app was able to be installed without this One-Time Charge, and both free trial and subscription worked well. Does anyone have had the similar issue before? How would you suggest the fixing? Thanks in advance!

I've been trying to upload my app to the App Store with Xcode 16.3 RC but I keep getting these error messages. When will Apple start allowing Xcode 16.3 submissions?

Context: Back on March 4th, we scheduled a price increase for April 16th on one of our monthly subscription plans with several hundred active subscribers, to change the price from $18.99/mo to $19.99/mo and it has sat unedited in App Store Connect since. Expected: Based on this documentation (Increase the price of an auto-renewable subscription), I would expect that 27 days prior to the price increase (which would be 4 days ago, on March 20th), that users would start receiving notifications about the price increase in the form of emails to their Apple IDs and push notifications when they open up the app. We also have App Store Server Notifications V2 set up. Therefore, I expected to start receiving PRICE_INCREASE notifications as users either got emails and/or push notifications. Actual: We have yet to see any PRICE_INCREASE events come through. Additionally, we have one employee subscribed to this plan on production with a subscription that would renew on April 17th, which would mean that the 21st (3 days ago) was 27 days prior to his subscription renewing. He has checked his email and the app and has still not been notified in any way about the price increase and his subscription manager shows he will renew April 17th at the same price. Questions: Is there some other step that needs to happen for the price increase to take place? Are my expectations wrong about what we should see by this point, or else why might we not have had any indication of customer notifications of the price increase occuring yet?

Hi! My app has a free feature and another feature require in-app-purchase to unlock. I am not listing the app in EU region due to digital service act. It is not a good idea to publish all my personal information on appstore. I just wonder if it is possible to still list my app on EU appstore but not the in-app-purchase. It will be great if the free feature still available to EU users. There will be a purchase button created using SwiftUI product view. In this case, users in EU will be very confused because the in-app-purchase will not be located. Not really sure if apple will allow my app to be listed and the in-app-purchase product view would be causing confusion to user. If anyone got any suggestion, please let me know!

I assume this is just some temporary error that will resolve itself but in App Store Connect > Trends > Subscriptions > Summary my number of Active Paid Subscriptions just tanked, so March 19th # is 74% less than March 18th # of subscribers. More than half of my subscribers are on an annual basis not renewing for a long time so no way it could drop like that. The breakdown on subscription type (1m, 3m, 6m and 1y) also shows a massive drop in subscriber numbers across all time lengths. All other numbers look normal, i.e. I should have added subscribers on the 19th, not lost them, based on the events tab. Just posting to make sure this gets noticed and resolved quickly. About to go through due diligence with a venture capital company so don't want due diligence process to have a negative result since the numbers suddenly don't add up!!! Thanks!