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, Our first submission was previously reviewed and we received feedback under Guideline 2.1 because the reviewer was unable to access the app due to a forced update issue. We fixed the issue completely, uploaded a new build, and resubmitted on Friday. The submission has now been in Waiting for Review for approximately 4–5 days with no further messages or requests. Could someone please confirm that the submission is correctly queued and that nothing else is required from our side? App: KIBAKI: Persian Community Submission ID: d1f921a3-9001-4ef2-a392-657860c437cd Current status: Waiting for Review Thank you.

Hello, I’m looking for clarification and guidance regarding a recent App Store Connect upload validation change that is preventing us from delivering an important bug-fix update to existing users on legacy iOS versions. Our production iOS app has historically supported iOS 11 and later. On August 28, 2026, we successfully uploaded a build with: MinimumOSVersion = 11.0 The upload completed successfully, with warnings only. One of the warnings stated: “MinimumOSVersion too low. This app has a MinimumOSVersion of 11.0. Starting later this year, all iOS apps must have a MinimumOSVersion of 13.0 or later in order to be uploaded to App Store Connect or submitted for distribution.” No specific enforcement date was provided. The same upload also displayed another warning stating: “Starting in Spring 2027, all iOS apps must have a MinimumOSVersion of 15.0 or later…” We subsequently uploaded another build targeting iOS 11 around September 8, and that version was successfully released on the App Store on September 10, 2026. I no longer have a screenshot of the warning from that particular upload, but the build itself was accepted and the corresponding version was released successfully. However, on September 17, 2026, when attempting to upload our next bug-fix build with the same MinimumOSVersion of 11.0, Apple’s server-side validation rejected the build with: Error 90068 “This bundle is invalid. The value provided for the key MinimumOSVersion '11.0' is not acceptable.” This means that the server-side enforcement appears to have changed sometime after our successful upload around September 8 and before September 17. What is especially confusing is that: the previous warning only said that iOS 13 would become mandatory “later this year”, without providing a specific enforcement date; iOS 11 builds were still being accepted in early September, including the build that was released on September 10; the same validation dialog stated that iOS 15 would become mandatory only in Spring 2027; the upload now fails completely before the build reaches App Store Connect or TestFlight. Because validation fails during upload, we cannot submit this build to App Review or request an expedited review. We have already completed a final bug-fix release for our existing legacy iOS users. Our intention is not to continue supporting iOS 11 indefinitely. We plan to increase the minimum supported iOS version after this release. We are only trying to deliver one final bug-fix update to users who already have the application installed on legacy iOS versions. The fix is ready, but affected production users currently have no way to receive it. I opened Apple Developer Support Case ID 102966589079 on September 17, 2026 and sent a follow-up on September 21. So far I have only received automated acknowledgements. The Developer Support case history also shows: “Email with Apple Developer Support — September 19, 2026” but I did not receive any email from Apple on that date. I checked Inbox, Spam/Junk, and Trash. Phone support for this case currently shows: “Phone support is currently unavailable due to high call volumes.” I have attached screenshots showing: the successful August 28 upload with the iOS 13 / iOS 15 warnings; the current Error 90068 rejection; the support case history. Could Apple please clarify: On what exact date did the MinimumOSVersion 13 requirement begin being enforced? Was this enforcement date announced anywhere before it became a hard upload requirement? Is there any supported way to upload one final bug-fix build for existing legacy iOS users? Could Case ID 102966589079 please be routed to the appropriate App Store Connect / Distribution team? Thank you.

Hi, I'm a new Apple Developer program member and over about a 10-day period, I have been blocked from beta testing my app. I have been getting repeated 422's about a TestFlight Beta contract not attached to app 6812131455 . I submitted a Feedback Assistant ticket, FB24795679, where an engineer replied and said things were unblocked. I believe that I was able to get one more build uploaded after that but then the problem recurred and completely blocked me from sharing the TestFlight External beta link with new testers. I am uploading using the Transporter App and then trying to attach in Appstore Connect. I emailed Apple Developer support and they sent me only basic information about what 4xx HTTP status codes were, so I followed up via phone to Developer Support under ticket 102964195981. I've been calling over the past 3 days and a Senior Advisor has not picked up the ticket yet. Diagnostic information is below, including a sanitized HAR file. The error is reproducible, even with new builds, even with going through and confirming all requested data input fields are filled out and agreements are signed (to the best of my knowledge). I am developing an ad-free, free app with a focus on accessibility for the visually impaired. Can someone help me find a durable solution here? Much appreciated--I see others have had this issue. Happy to capture further debug logs to assist in a fix. captured_at_utc source build_number method url http_status error_code error_id x-apple-jingle-correlation-key x-apple-request-uuid x-responding-instance 2026-09-24T15:07:48.547415+00:00 live 116 POST /iris/v1/betaAppReviewSubmissions 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING 7ef85ee6-412e-4535-b8f7-16cb8da406c8 5QSUAQZ4MOELPIGMJXUJD4UBP4 ec254043-3c63-88b7-a0cc-4de891f2817f ac-gateway-api:ac-gateway-api-main-5d674cb558-bp79n:ac-gateway-api-main-5d674cb558-bp79n:-1::::prod failures-422.md failures.jsonl failures.md session.sanitized.har

I'm submitting a new version of my app, and after click "submit for Review", it show that: A few more items are needed in order to submit for review The items listed below are required for submission:There are still screenshot uploads in progress. I didn't met this problem before. Is that mean I haven't upload all the screenshot required or it's still uploading the screenshots to App Store Connect's server? Cause before there is a "save" button after you drag images to the screenshots area, now you don't. And I think I have uploaded all the screenshots needed and I waited a day to try submit again, still the same. What should I do?

Hi Apple Developer Community, I'm hoping someone from the App Review community or Apple can help me understand what may be happening with our app. Our educational app has now been rejected multiple times under Guideline 5.6 — Developer Code of Conduct. The problem is that we have not received a specific explanation identifying which feature, behavior, or part of the app is considered a violation. We have carefully reviewed the rejection and made sure that there are no features intentionally hidden from App Review. The functionality available to the reviewer is available to normal users as well. We have already: Replied to the App Review rejection asking for the specific reason. Submitted an appeal explaining the situation. Asked Apple to identify the specific feature or behavior that triggered Guideline 5.6. However, we have not received a response to either the appeal or our message in the App Review/Resolution Center yet. About the app: This is an educational application used by students for exam preparation. The upcoming examination period is approaching, and students are currently waiting for access to the application and its preparation materials. This makes the situation particularly time-sensitive for us. We are willing to make any changes required by Apple, but without knowing what behavior triggered 5.6, we don't want to keep making random changes and repeatedly resubmitting the same app. My questions are: What kinds of situations typically result in a 5.6 rejection when Apple does not specify a particular feature? Is there anything specific we should check in our app or review configuration? Is there a way to obtain clarification on the exact 5.6 concern while the appeal is pending? Should we wait for the appeal response before submitting another build? We would really appreciate any guidance. We are not trying to bypass App Review — we simply want to understand the specific issue so we can fix it correctly and provide students access before their exams. Thank you.

I have been trying for 24 hours to upload app, and first time this has happened in 8 years and 100+ uploads. Please help. Validate App and Upload both hang indefinitely at "Preparing" in Xcode Organizer. No error is ever returned — the progress bar freezes and the operation never completes or times out. Transporter 1.4.5 fails identically. Key detail: archive 2.4.3 (build 123), which Apple accepted and processed on Sept 10, 2026, now hangs the same way when validated. Same machine, same Xcode, same Apple ID. This rules out the archive, its signature, and its provisioning profile. Already ruled out: two independent networks (home Wi-Fi and iPhone cellular hotspot); the archive itself (known-good build 123 fails identically); Xcode install (27.0 / 27A266a, xcode-select verified correct); Apple ID session (signed out and back in three times); full reboot. macOS 27.0 (26A428) on MacBookPro18,4. Last successful upload Sept 10, 2026. 100+ prior archives uploaded without incident over several years. macOS has updated twice since Sept 10. Separately: Transporter 1.4.5 crashes on macOS 27.0 with an unhandled exception in TransporterKit while drawing its activity queue (EXC_BREAKPOINT via +[NSApplication _crashOnException:]).

My app was rejected during App Review because the reviewer reported that the app could not be installed on their iPad Air 11-inch (M3) running iPadOS 26.6.2. The rejection references UIRequiredDeviceCapabilities. My development platform, Base44, tested the app on the same device type and confirmed that the app installs and launches successfully. They also confirmed that UIRequiredDeviceCapabilities is set to arm64. Because the issue cannot be reproduced outside of Apple’s App Review environment, Base44 recommended contacting Apple Developer Technical Support to obtain the exact installation error and device/install logs. However, the DTS submission form requires a focused Xcode sample project demonstrating the issue. I don’t have a separate Xcode sample project because the app is built through Base44. App: On Mangeoù Version: 1.0 Build: 10 Review device: iPad Air 11-inch (M3) OS: iPadOS 26.6.2 Is there a way for Apple to provide the exact installation error or relevant diagnostic information from the App Review device so the issue can be identified? Thank you.

I'm stuck on what should be a routine resubmission and can't find documented steps that match what I'm actually seeing in App Store Connect. Situation: My app's only existing submission (from an earlier rejected review round) is now in "Unresolved Issues" status. Per Apple's own docs, items can't be added to a submission in this state. I have a new build ready and uploaded (via eas submit / App Store Connect API), showing "Ready for Review" on the version page. I also have two subscriptions in the same subscription group, both fully configured and showing "Ready for Review" status. The subscriptions' own "Add for Review" button creates a separate Draft Submission, but that draft has no way to attach an app version to it. It just shows "To submit your items for review, add an app version for the selected platform," with no visible control to do so from that panel. The app version page itself has no "+" button next to Build and no "In-App Purchases and Subscriptions" section (some help docs describe this section; it doesn't appear on my version page at all). What I'm trying to do: submit the new build together with both subscriptions as one review submission, since it's a first-time auto-renewable subscription and Apple requires it be submitted alongside an app version. Has anyone run into this specific dead end: an app version with nowhere to attach IAPs, and a subscription draft with nowhere to attach a build? What's the actual current path to combine them? Screenshots of the exact UI I'm seeing available on request.

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 , In the app store are my old image that you can see, and not the new ones ? How can i fix that ? This is from the connect If you see online its ok Appstore This is what i get in the app store (old)

I have a problem to solve. Wondering if anyone can help me? My app (auto-mobile Apple ID: 6802762195) uses a standard encryption algorithm, instead of using or accessing the encryption within Apple's operating system. So Apple requires you to fill out and submit App Encryption Documentation on appstoreconnect. Well I did that on Sept 5th 2026 and it is now Sept 21 2026 and Apple says “still in review.” So I contacted Apple Support on Sept 12. Asked why "still in review" on Sept 12. Their first reply is on Sept 15: “Your inquiry will be forwarded to Apple’s Export Compliance Department team for review and response.” A week passes and I hear nothing. So I email support again (Sept 18) and their second reply (Sept 21) is: “We currently do not have the right tools to share you the exact information you are looking for. if the status shows "In-review" for you that means "Your binary is currently being reviewed by Apple. If you want to remove your binary from the App Review queue, click Reject Binary". But if I remove the submitted App Encryption Documentation (“binary”) the app will be rejected. So I am kinda confused by Apple’s answers and advice so far. Anyone else have this issue? How did you resolve it? Why is Apple telling me "they don't have the right tools" to investigate the App Encryption Documentation on their own AppStoreConnect? Any input would be amazing... Because I've tried Apple and get no answer... or an answer that would make my app ineligible. Thanks in advance community!

Hello, I'm hoping someone from the App Review team can take a look at our submission. App name: Happyy UAE Latest submission date: 10 September 2026 Current status: Waiting for Review We have been trying to publish this app for more than two months. We addressed the feedback from previous reviews before resubmitting, but the latest submission has now been waiting for 11 days with no feedback, questions, or status change. This delay is holding up our launch. Could someone please check whether the submission is stuck, or let us know if anything else is needed from our side? Thank you for your help.

Hi everyone, I'm hoping App Review can take a look at our case, or help us get a call. Our app FlightCue: Flight Tracker (App ID 6790973619, version 1.0) was rejected under Guideline 4.3(a) – Design – Spam on September 9 and, after a resubmission with new features, again on September 19, 2026. Timeline: September 1: submitted for review. September 9: first 4.3(a) rejection. September 9: we replied in App Store Connect, asked which of binary / metadata / concept applied, and requested a call (with our phone number, hours and language). We did not receive a call. September 17: App Review replied to our message that the app "still provides the same feature set as other apps submitted to the App Store for review." September 18: we resubmitted with the two feature areas we had been building: (1) a Turbulence tab on every flight screen – a segment-by-segment turbulence forecast along the actual route, headwind/tailwind and its effect on arrival time, thunderstorm areas the route crosses, nearby pilot reports (PIREPs), and takeoff/landing conditions at both airports; (2) a Price Tracker tab – fare-drop alerts for a route or a specific itinerary, re-checked daily by our backend, with price history. September 19: rejected again under 4.3(a), this time with the Extended Review note. FlightCue is a single app from a single developer account, developed in-house. Our next build (not yet submitted) also adds a flight by scanning the boarding pass. We are not resubmitting until we hear back. We have filed an appeal with the App Review Board, and we would be very grateful for a call so we can understand which part of the app or the listing is considered similar and change the right thing. Submission ID: 16908a41-1139-4832-bee7-87bce3bc6acd Thank you for your time Ercan Garip

Hi Apple Developer Community, Our app has been going through App Review since September 13. We have addressed every issue raised by App Review. Importantly, the most recent review issues were primarily metadata-related. The latest screenshot issue was specifically stated by App Review as eligible to be resolved in our next update, but we nevertheless fixed it immediately and submitted on September 18. Our expedited review request was also accepted and confirmed by a Senior Advisor from Apple Developer Support. The app and all associated subscriptions are now back at “Waiting for Review.” Submission ID: 6b3c0adc-e145-4329-91cf-811c92e25a7b Given that the recent issues were metadata-related and have all been addressed, is there anything else preventing the expedited review from proceeding? If an Apple staff member could check or internally escalate the existing review, we would greatly appreciate it. Our team is standing by and can respond immediately to any additional requirements. Thank you.

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.

Hello, I am looking for guidance on a submission that has been in review for an unusually long time, and to ask whether other developers are seeing the same thing. App: Kids Coloring & Learning Games Apple ID: 6754971485 Platform: iOS Support case: 20000144299546 Timeline: 14 Aug 2026 — submitted, entered Waiting for Review 14–24 Aug — no movement (10 days), never entered In Review 25 Aug — cancelled and resubmitted the identical build ~3 Sept — entered In Review Today — still In Review That is 35 days since first submission and about 17 days in In Review. I have contacted Developer Support and my expedited review request was accepted and confirmed. Despite that, there has been no further movement and no communication. There are no messages in Resolution Center and the review team has not asked me for anything. This is an update to an app already live on the App Store, in the Kids Category with in-app subscriptions. The build itself is unchanged from a version that was previously approved. My questions: Is there a way to find out whether something specific is blocking this review, as opposed to it simply being queued? Are other developers currently seeing extended In Review times, particularly for Kids Category apps with subscriptions? Is there anything further I should do, or is waiting the only option at this point? I would rather fix a problem on my side than keep waiting if something is actually wrong. Any guidance would be appreciated. Thank you.

Our app, Roll (Apple ID: 6797953438), has received two Guideline 4.3(a) spam rejections. Our responses have gone unanswered for almost 3 weeks, and then we got an account warning. August 27: First rejection. We replied requesting clarification, explaining the app’s functionality, and supplied a walkthrough video. September 14: After almost three weeks without clarification, we submitted a substantially revised build with new functionality. We included an explanation directly in the App Review notes. September 15: The exact same rejection, still without identifying the issue or addressing our notes to them. This time, it included a warning about account removal for repeated noncompliance. It seems Apple is refusing to read our replies. Instead, they got back to us with the same rejection and a warning. For what? Doing as we were told and writing a reply? Note that thus far, NONE of our replies have even been acknowledged. Has anyone resolved a similar 4.3(a) rejection? What helped you get specific clarification or a call with App Review?

I'm encountering a validation failure when uploading my app to App Store Connect. The upload itself completes successfully, but Apple's server-side validation fails with the following error: "The app contains one or more corrupted binaries. Rebuild the app and resubmit. (ID: 087e356b-4dc3-4e52-8d61-ddee9e3c74e7)" App Information App Name: 万华电商 Bundle ID: com.imhehe.wanhuads Version: 1.0.25 (Build 2) Distribution: iOS App Store Environment Xcode: 26.3 macOS: Sequoia 15.8 Team: Wanhua Petrochemical Co.,Ltd Steps Already Taken I have tried the following troubleshooting steps, but the issue persists: Cleaned Derived Data and removed old Archives Executed Product > Clean Build Folder Re-archived the app with a fresh build Re-uploaded via Xcode Organizer The upload appears to succeed (ContentDelivery returns 201 Created), but the binary fails during Apple's server-side validation with the corrupted binaries error. What I'm Looking For Could someone help clarify what might cause this server-side validation failure, and what additional steps I should take to resolve it? I'm particularly interested in: Whether there are known issues with Xcode 26.3 and App Store validation Any specific binary integrity checks that might be failing on Apple's side Whether there are additional diagnostic steps I can take to identify which binary is flagged as corrupted Attachments I have attached the full upload log for reference. Please let me know if any additional information would be helpful. Thank you in advance for any guidance. ContentDelivery.log DVTITunesSoftwareService.log [ContentDelivery.log] IDEDistributionPipeline.log ( IDEDistribution.standard.log h IDEDistribution.verbose.log ttps://developer.apple.com/forums/content/attachment/8d344932-bbfe-41cc-81dc-3d93e94cda2b)

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, Our app has been in "Waiting for Review" since September 8 with no status change. It has never moved to "In Review." Steps already taken: Expedited Review Request, approved on September 11, but status did not change Contacted App Review Support for a status update, no response Requested a call, no call has taken place We have received no rejection, no request for additional information, and no messages in Resolution Center. This is time-sensitive: we have a real-world community event on September 19 in Düsseldorf, Germany, tied to this launch. App: KIBAKI: Persian Community Apple ID: 6797615150 Version: 1.0.36 (35) Submission ID: d1f921a3-9001-4ef2-a392-657860c437cd Submitted: September 8, 2026 Could the App Review team please check whether this submission is stuck in the queue? Thank you.