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.

My macOS app update has been sitting in "In Review" since Aug 31 at 12:50 PM PT — 13 days — with no messages, questions, or status changes in App Store Connect. ▎ App: NFS Files – NAS Drive Client ▎ App ID: 6789844265 ▎ Platform: macOS, version 2.0 (build 9) ▎ Submission ID: ac1eccf9-a982-492c-a6c4-c402c5f91d29 ▎ The identical iOS 2.0 submission, with the same review notes, was reviewed and approved on Sep 6. The earlier 4.3(a) concern on both platforms was addressed by removing the other network-file apps from my account and by the NFS-specific functionality described in the review notes. ▎ I've also submitted a request through the Contact Us form. Is the review still active, or is anything needed from me?

Hello, My app IMMONAI (App ID: XXXXXXXXX) has been stuck in "Waiting for Review" since September 4, 2026 — iOS version 1.4.3, build 32. During this time, I have: Contacted App Review support (no response) Submitted two expedited review requests (Case Number: XXXXXXXXX), with no acknowledgment There are no messages in the Resolution Center and no rejection or feedback of any kind. My previous submissions were typically reviewed within 24-48 hours. Could you please check whether my submission is blocked in the queue for some reason? Any guidance would be greatly appreciated. Thank you.

Hi, I'm completely blocked from TestFlight. Every attempt returns: "status": "422", "code": "BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app." This is an older account that has used TestFlight fine before. Nothing changed on my end, no account changes, no agreement updates. What I've already checked: Business > Agreements: Paid Apps and Free Apps both Active Tax forms and bank account Active No pending banners anywhere in App Store Connect or developer.apple.com Test Information complete Export compliance answered Build processes to VALID with no warnings Same error on a brand new app with a fresh build, so it looks like the beta contract is detached on the backend rather than an app-level problem. I've filed a support request and haven't heard back. This is time sensitive, I have a client pilot waiting on an external TestFlight link. Is there any way to get this re-provisioned? Apple Support case ID: 20000118605424 Thanks.

The Screenshot specifications page lists iPhone Duo as an iPhone screenshot size: Outer display: 1398 × 2034 and 2034 × 1398 Inner display: 2007 × 2853 and 2853 × 2007 https://developer.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications I cannot find a way to upload them. In App Store Connect, the App Previews and Screenshots device selector on my app's version page does not list iPhone Duo. The only iPhone options are the existing display sizes. In the App Store Connect API, ScreenshotDisplayType has no Duo case. The largest iPhone case is still APP_IPHONE_67. I checked the current reference: https://developer.apple.com/documentation/appstoreconnectapi/screenshotdisplaytype My questions: Where in App Store Connect do I upload iPhone Duo screenshots? If the option is not open yet, is there a ScreenshotDisplayType case for Duo that I should use through the API instead? Thanks.

Hi, our new app Amisoria (App ID 6805385809, Submission ID 95e40745-299b-4467-b9f6-8dd5ca907b02) was submitted Aug 29. On Aug 30 we received a Guideline 2.1 "Information Needed" message; we replied Aug 31 with all eight requested items including a screen recording, and followed up on Sep 3. We also opened Developer Support case 102955409950 on Sep 7. There has been no response of any kind since Aug 30. Could someone from App Review please take a look? The app is a client for a self-hosted AI gateway; a built-in demo mode lets reviewers test it without any server. Thank you.

Hello, We would appreciate some guidance regarding an unexpected StoreKit currency result in a TestFlight build. Our iPhone language and region are both set to France. The Sandbox tester is also configured for France, and our subscription products have French availability and pricing configured in App Store Connect. In the TestFlight build we diagnosed, StoreKit reports the current storefront as France with EUR: storefront=FRA/143442/EUR However, all 10 subscription products are returned with USD product metadata: products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE Example: formatCurrency=USD locale=fr_US_currency_USD localeCurrency=USD display=1,99 $US price=1.99 We first observed this through Flutter's in_app_purchase integration. To determine whether the Flutter plugin was involved, we added a native StoreKit 2 diagnostic to the same TestFlight build. The native result was identical: receipt=sandboxReceipt storefront before=FRA/143442/EUR storefront after=FRA/143442/EUR products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE The issue appears specific to the TestFlight distribution. When the application is installed directly from the development computer, prices are returned in euros on the same device. We also tested with the regular Media & Purchases account signed out and a French Sandbox tester connected. Once the products loaded successfully, StoreKit still returned USD metadata. In another configuration, the application displayed the USD price while Apple's purchase sheet displayed the price in euros. We are using the price and formatting information returned directly by StoreKit. We do not want to infer the currency from the device region or perform a client-side currency conversion, because StoreKit should remain the authoritative source. Could you please help us understand: Is it expected for Storefront.current to report FRA/EUR while Product.priceFormatStyle.currencyCode, its locale currency, and Product.displayPrice use USD? Could a TestFlight or App Store Connect configuration cause product metadata to use a different currency from the current storefront? Is there another account, availability, pricing or distribution setting that we should verify? Is there a recommended way to refresh or invalidate the product metadata used by a TestFlight installation? We have already filed Feedback Assistant report FB24723329, which is currently under investigation. Thank you very much for any clarification or additional diagnostic steps you can suggest.

Dear Apple Developer Support Team, I am writing to urgently escalate my Apple Developer Program enrollment issue regarding Case Number 20000132030420. I have been trying to enroll in the Apple Developer Program for almost two months, but my enrollment is still pending. I have contacted Apple Support multiple times and followed the instructions provided, but unfortunately, I have not received any meaningful update or resolution. More than a month ago, I was asked to submit my government-issued ID for verification, which I submitted as requested. Since then, I have received no update regarding the status of my enrollment. I have also attempted to contact support regarding this case, but my messages have not received a response. This prolonged delay is extremely frustrating and is preventing me from moving forward with my development work and publishing plans. I have been patient and have followed every step requested by Apple, but after nearly two months without a resolution, I am requesting that this case be urgently escalated to the appropriate team and that my enrollment status be reviewed. Please provide me with: An update on the current status of my enrollment. Confirmation that my submitted government ID has been received and reviewed. The reason for the continued delay, if applicable. A clear timeline for when my Apple Developer Program enrollment will be completed. I sincerely hope @Apple @Support can look into this matter and resolve it as soon as possible. This is now my last option to reach out again for support, as I have already spent considerable time trying to resolve this through the existing support channels. I would greatly appreciate a prompt response and resolution to Case #20000132030420. Kind regards,

Hi everyone, I'm an iOS developer based in Türkiye. Over the years, some of my Apple Developer accounts have been blocked/terminated, and I was never able to regain access or find out the reason — even the termination emails didn't give me a clear explanation. Right now I'm a member of three teams: my personal (individual) account and two organization accounts belonging to companies I work for. I regularly update and release apps on all of them, so losing access again would put me and my employers in a very difficult position. Support hasn't been able to tell me why the previous accounts were closed, and I feel quite alone in this. Has anyone been through something similar? What steps do you recommend to: Avoid account termination in the first place, and Get a proper response from Apple Developer Support if it happens again? Any advice would be appreciated. Thank you!

Its my First App. It has been ready for Distribution since August 18, in the Business tap,everything is "Active" but my status in Compliance -Digital Services Act is stack "in review"!! No email replies, no nothing. Can anyone help me please?

Our app Finbo (Apple ID 6761951739, iOS version 1.0.32, build 28) has been in "Waiting for Review" since August 20, 2026: 22 days with no reviewer assigned and no messages in Resolution Center. We sent two expedited review requests last week and never received a reply, not even the acknowledgement email. Today we opened support case 102959970140 (App Review Status). Has anyone seen a submission sit unassigned for this long? Is there any other channel to get it picked up? We are not going to cancel and resubmit because that sends it to the back of the queue.

Good day, I'm trying to resolve the EU "Digital Services Act" compliance for my employer's Apple Developer account, but I'm stuck on verifying the phone number. The email verification code came through without any issue. We are located in South Africa, with a "+27" area code and the number I need to use here is a landline that comes through to the receptionist at our head office. This number does not have the ability to receive text messages, so I selected the "Didn't get a verification code?" link and chose the receive a phone call instead, however the call never comes through. Calling the number from my cellphone goes straight through to the receptionist, there are no digital switchboard prompts for the caller to select from. I tried this numerous times this Friday just past, and again twice now today, still no luck. I've requested an official document from my manager to see if I can go that route to verify the details, but so far nobody seems to be able to find an appropriate document for me to use... :( Is there anything else that I can do here?

My app has one App Store Connect listing with released iOS, tvOS, and native visionOS versions. I have temporarily discontinued native visionOS development due to very limited adoption and no access to a physical Vision Pro for ongoing testing. I would like Vision Pro users to receive my iPad app through “Designed for iPad” compatibility instead. Xcode is configured with “Apple Vision (Designed for iPad)” and correctly produces an iOS build. I am not trying to generate another native visionOS build. The obstacle is the existing published visionOS version. Apple’s documentation says that iPad compatibility is unavailable when the app already supports native visionOS, and that a platform cannot be deleted once a build has been uploaded. Has anyone successfully made this transition while keeping the same App Store Connect record? Specifically: Is there a supported way to retire the native visionOS version and offer the compatible iPad app? Can Apple Developer Support enable this if App Store Connect cannot? What happens to existing native visionOS installations? I would appreciate any firsthand experience or clarification from Apple on whether this transition is supported.

Initially, I had some issues enrolling in the individual Apple developer program. Then, I contacted support via email, and they finally requested that I verify my identity. I submitted my national ID for verification and then received an email stating that my identity was verified. After that, I tried to enroll in the Apple developer program, but the issue persisted even after they instructed me to proceed. Subsequently, I received an email stating that my identity was not verified. Here is the exact wording from the email: "We can’t verify your identity with the Apple Developer app or provide further assistance with the Apple Account for Apple developer programs." After that, I tried to reach support several times, but there has been no response from them.

I am having an error when trying to Add for Review? Unable to Add for Review The items below are required to start the review process: An unexpected error was encountered when submitting for review. If the issue persists please contact us. Does anyone else have this issue or know perhaps a workaround.

Hi everyone, I set up an auto-renewable subscription introductory offer in App Store Connect with a scheduled start date of September 7 for the Philippines storefront. According to the documentation App Store pricing and availability start times by country or region, scheduled pricing and offer updates are expected to go live based on local regional times. However, the offer did not show up in the Current Introductory Offers in app store connect portal at the documented start time (14:00 Sep 6th UTC). Instead, it stayed in the Upcoming Offers until 7:00 Sep 7th UTC which is 17 hours after the time in the doc. We met a similar situation a few days later when we launch another introductory offer in Thailand. I would appreciate clarification on the following points: What is the underlying reason for the discrepancy between the documented start time behavior and the actual start time observed in production? Can Apple update the App Store pricing and availability start times by country or region reference documentation so that it accurately reflects the practical start time and propagation window for each region? Any insights or shared experiences with offer scheduling in the APAC region would be greatly appreciated.

An update to our 10-year-old passport photo app for macOS was rejected under “Guideline 1.1.6 - Safety - Objectionable Content.” We have neither changed any of the app's existing features nor added new ones. This update only included minor changes to the user interface and an update to the age rating questionnaire in App Store Connect. This is the reason for rejection provided to us by the reviewer: Guideline 1.1.6 - Safety - Objectionable Content Issue Description The app contains content or features that are misleading, intended to deceive users, or are otherwise fraudulent. Specifically, the app provides services for editing photos for government documents. Note that adding a disclaimer to the app description is not sufficient if the rest of the metadata and the app are misleading. Next Steps It would be appropriate to remove any content or features from the app that could be misleading or enable fraudulent activity before resubmitting for review. We are having difficulty understanding how Guideline 1.1.6 applies to our app. The app is simply a tool for creating passport photos. Users select their own portrait photo and manually position and crop it to the required photo dimensions. The app does not manipulate the content of the photo, change facial features, or alter a person's appearance. The app has been available for approximately 10 years and is also used as a professional tool by photographers around the world to prepare and print passport and ID photos for their customers. It does not edit passports, ID cards, visas, or any other government documents. The output is simply a portrait photo in the selected dimensions that can be saved or printed. The country-specific presets provide the required photo dimensions as well as a visual mask for head size and positioning, based on publicly available specifications published by the relevant authorities in each country. These presets are used only to help the user manually align and crop the portrait photo according to those published requirements. They are not templates for government documents. We have submitted an appeal, as we believe there may be a misunderstanding about what the app actually does. Has anyone else encountered a rejection under Guideline 1.1.6 for a passport photo or similar photo-formatting app? We would particularly appreciate any insight into the statement that providing services for “editing photos for government documents” falls under Guideline 1.1.6. Is there a specific App Review policy regarding passport photo apps that we may have overlooked? For additional context, this particular app does not include background replacement or automatic cropping. However, even if an app did offer such features, passport-style photos are not used exclusively for passports or government-issued identity documents. They can also be used for driver's licenses, student IDs, fishing licenses, membership cards, employee IDs, and many other purposes. For some of these use cases, background replacement may be perfectly acceptable. Requirements also vary depending on the country, authority, and intended use of the photo. It would therefore seem reasonable for users to decide how to prepare their photos based on the requirements applicable to their particular use case. We would be very interested to hear how other developers interpret this guideline and whether anyone has encountered a similar situation. Any experiences or advice would be greatly appreciated.

Hi everyone, I’m looking for guidance regarding an unusually long App Review delay. My first iOS app, EmpowerFI, has been in “Waiting for Review” for almost 30 days. In two days, it will reach a full month without moving to “In Review.” During this period, I have contacted Apple Developer Support several times. After my initial contact, Apple submitted an expedited review request as a one-time exception for my app. However, the status did not change. I contacted support again and received the following response: “We have confirmed that your app review is proceeding normally, and there is no further action you need to take.” I have followed up multiple times since then, explaining that I am not asking Apple to guarantee a review or approval date. I am simply trying to understand why this particular submission has remained in “Waiting for Review” for almost a month. Unfortunately, I continue to receive essentially the same standard response. There are no pending actions visible in App Store Connect, and Apple Support has explicitly confirmed that there is nothing further required from me. I fully understand that review times vary and that some apps may require additional scrutiny. However, almost 30 days without even moving from “Waiting for Review” to “In Review” seems exceptionally long, particularly after an expedited review request was submitted. I also know developers who submitted apps during this period and received a review response within approximately two days, so I am trying to understand whether there could be something specific affecting my submission. Has anyone recently experienced a similar delay with a first app submission? More importantly, is there any other appropriate escalation path when Developer Support confirms that everything is normal but the app remains in “Waiting for Review” for almost a month? I am not looking to bypass App Review or request guaranteed approval. I would simply like someone to investigate whether there is an issue affecting this submission or explain why it has remained in the queue for such an exceptional amount of time. Any guidance from Apple staff or developers who have experienced this recently would be greatly appreciated. Thank you,

Hello, I am trying to enroll in the Apple Developer Program, but I cannot complete the payment. During the purchase process, I receive the following error: We are unable to complete your order. There was an issue when we processed your order. An invalid value '1549' was provided for State, Province, or Region. My details: Country: Kosovo State/Province/Region: Kosovo Region (selected from the available option) I have verified my information multiple times, but the error appears every time. I have contacted Apple Developer Support multiple times over the past month.I have not received any response (positive or negative). I need to complete enrollment to publish my apps, and this delay is blocking my work.