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

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

Hello App Review team, Our live app crashes within 15–20 seconds of launch for all users and has been unusable since October 29. The update containing the crash fix has been in "Waiting for Review" since October 31, despite multiple accepted expedited review requests and follow-up escalations through Contact Us. Apple ID: 1450809061 Version: 9.1 (iOS) Submission ID: 097aad7f-e972-4bcc-9521-5d6539727d3f Case ID: 103013406646 Context: The update was previously rejected twice for metadata guidelines only, and both issues were addressed the same day. Each time, Apple confirmed the expedited review, but the resubmission has not yet entered review. Could you please look into this submission and let us know if anything is blocking it, or if any action is needed from our side? Our entire live user base is affected. Thank you for your help.

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 Review Team, I hope this post finds you well. My app CapDex: Language Learning (App ID: 6805323578) was rejected on October 30, 2026. I have since addressed the issues and resubmitted version 1.0.1, which has been in “Waiting for Review” for over 7 days. Could you please help me with the following: Provide more detailed feedback on the specific reasons for the previous rejection (if possible). Advise if there is anything else I should check or improve before the next review. If appropriate, kindly consider prioritizing the current submission so we can move forward. I am fully committed to complying with the App Store Review Guidelines and will make any necessary changes immediately based on your guidance.Thank you very much for your time and support. Submission ID: f9633cec-c596-4e78-90b8-aec89b0e2691 Best regards, Hiến Hồ

Hello App Review team, Our first app, FormaCoach AI (Apple ID 6826677522), was rejected on Oct 30 under Guideline 2.1(a) (date of birth could not be entered). We fixed the cause (a time-zone issue in date parsing) and resubmitted build 23 on Oct 31. An expedited review was granted the same day, but the submission has stayed in "Waiting for Review" since then. Submission ID: 16c87033-937e-4bcb-8ab3-95c25dca87be Could you please confirm the expedite is attached to this submission and let us know if anything is needed from our side? Thank you.

Our app vCard — Digital Business Card (Apple ID 6820835727, version 1.0) was first submitted on October 11, 2026. We removed it and resubmitted it on October 23, and it has remained in Waiting for Review since then, with no messages in App Store Connect. Its in-app purchase and subscription are also waiting for review. Our agreements, tax and banking information are all active, and other apps on the same account have been reviewed and released normally. Support case 103010061741 was opened on October 27 and followed up on October 29, and we have not received a resolution. We also submitted an expedited review request on November 6. Could you please check whether something is blocking this submission, and tell us if any action is needed from our side?

Hi everyone, I'm a Spanish citizen living in Georgia, where I'm registered as an Individual Entrepreneur. In App Store Connect, the W-8BEN tax form shows Line 2 "Country of citizenship" fixed as Georgia, and the field can't be edited. My citizenship is Spain, so I can't submit the form without giving false information. Because of this, my Paid Apps Agreement has been stuck in "pending user information" since October 20, and I can't offer in-app subscriptions. What I've tried: Resetting the tax questionnaire: the field stays locked. Contacting Apple Media Services Finance Support (cases 23005981 and 23107848). I've followed up four times since October 20 and haven't received a resolution. I haven't changed my account country, to avoid triggering another verification. I've seen other developers in the forums with the same issue (citizenship locked to the account country), so it looks like a known problem: https://developer.apple.com/forums/thread/839914 https://developer.apple.com/forums/thread/850501 https://developer.apple.com/forums/thread/852867 Could someone from Apple look into these cases or escalate them to the team that can unlock the field? Has anyone found a way to get this fixed? Thanks a lot.

I own a U.S. single-member LLC that's a disregarded entity. In App Store Connect, Line 1 of the W-9 is locked to the LLC name, but the IRS instructions say the owner's name goes on Line 1 and the LLC on Line 2. This is blocking my Paid Apps Agreement. I contacted Finance Support around 9-23-26 with a screenshot and video of the issue, but haven't heard back. I followed up a week ago. Still no response. Has anyone with a single-member LLC gotten this fixed recently? Apple developer support says their financial team is the only team that can handle this issue. Nearly one month to fix some basic text is ridiculous. I could have handles this myself if the Line 1 box wasn't greyed out.

Hello Apple Developer Forum, We have implemented the Declared Age Range API exactly as described in Apple's documentation. Our implementation checks isEligibleForAgeFeatures before calling requestAgeRange, as recommended. We have been testing with different users located in Texas (US) and Brazil. However, for all users, isEligibleForAgeFeatures consistently returns false, so the Declared Age Range prompt is never displayed. We would appreciate some clarification on the following: Under what conditions does isEligibleForAgeFeatures return true? When is the Declared Age Range prompt expected to be shown? Besides the user's region, are there any additional eligibility requirements, such as whether the Apple ID has a verified payment method (credit/debit card), verified identity or address, account age or a phased rollout? Since all of our test users are in supported regions (Texas and Brazil), we expected at least some users to be eligible. However, all four test accounts consistently return false. Could you please clarify how Apple determines eligibility for the Declared Age Range feature and when developers should expect the prompt to appear? Thank you for your guidance.

Hi everyone, I'm trying to publish my first iOS app (a game built with the Godot engine), but every upload to App Store Connect fails with this error: "Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path "sevenatseven.app/sevenatseven" is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate." Setup: Xcode 27.1 (27A9275), macOS 27.0.1 The Xcode project is exported from Godot 4.7.2 (stable) Automatic signing with my paid team; no signing errors shown in Xcode Release configuration, Code Sign Identity: Apple Development (Xcode re-signs for distribution on upload) My account has a valid Distribution Managed certificate What I tried: Archive with "Any iOS Device (arm64)", then Distribute App > App Store Connect > Upload Clean Build Folder, fresh project export, new archive The archive always succeeds and the app runs fine on a real iPhone, but the upload is rejected every time with the same error on the main executable. What can cause this error on the main executable when the archive and signing look correct in Xcode? Is there a way to see which code requirement is failing, or a codesign command I should run on the archive to check it? Thanks!

Hello, My app has been stuck in the "Waiting for Review" status for seven days since submission. During my previous submission, it took a total of 37 days to receive a review result—even though the issues raised back then were quick to fix. I have already requested an "Expedited Review" and reached out to the review team via App Store Connect, but I have yet to receive any response or updates. As a solo developer, the ongoing costs I incur while unable to launch my app make this delay a significant burden. Is anyone else experiencing similar review delays recently? If an Apple representative happens to see this post, could you please check the status of my app’s review? I can provide the App ID or further details regarding the submission if needed. Thank you.

I submitted a corrected Form W-9 through Apple's provided secure submission link after App Store Connect reversed my information, listing my single-member LLC on Line 1 and my personal legal name on Line 2. This appears to be a known issue that Apple Finance has reportedly acknowledged. Apple confirmed receipt on September 3, 2026, and said its Tax team would review it. As of October 21, 48 days and multiple follow-ups later, I still haven't received confirmation of whether the correction was accepted or further action is required. Today, I called Apple Developer Support. The representative consulted a Senior Advisor, their Support Advisor, and Business Support. According to the representative, the people contacted had "no clue" how to reach Apple Finance or escalate the case. I received a new case ID, but the issue remains unresolved. My app is approved and ready for release, but I've chosen to wait until Apple confirms my tax information is correct. Apple specifically stated that the corrected information would not be reflected in App Store Connect, so I have no way to verify the update myself. All I'm asking for is confirmation that my corrected Form W-9 was accepted or whether anything else is needed from me. I'm sharing this to document my experience because there's still no clear way to obtain an update or escalate my Apple Finance case, and the delay is holding me back from launching my app and growing my business.

Hi everyone, I submitted an update to my app on November 5th, 2026, and its status is still “Waiting for Review.” Has anyone else seen similar wait times recently? I’d be interested to hear how long it took for your submission to move to “In Review.” Thanks for sharing your experience.

I'm genuinely at a loss with Apple's App Review process. Our backend records show that across BOTH reviews, Apple's reviewers did not complete a SINGLE use of our app's core functionality. Not once. ZERO completed generations. For the latest review, our logs confirm Apple successfully logged in, but recorded ZERO generation requests and ZERO credits consumed. This isn't some minor feature. It's the entire foundation of our app. Our app fundamentally changes and becomes personalised as it's used. Without completing that process, you're essentially judging an incomplete product. Submission ID: 6a126514-9bb6-4d91-923c-bf29aacb1b68 Here's why this is so frustrating. We spent months deliberately building an app that offers functionality and a user experience fundamentally different from existing competitors. This wasn't another copycat app - avoiding that was central to its design from day one. We explained these differences extensively in our App Review notes. Yet Apple has rejected us TWICE under Guideline 4.3(b) — Design Spam. We even provided a narrated walkthrough demonstrating exactly what makes our app unique. Our video analytics show ZERO views. So we're being rejected for supposedly lacking originality, despite neither review producing a completed use of our main feature and no recorded views of our demonstration. After both rejections, we've received nothing but generic responses telling us to improve the app, without identifying a single specific problem. How are independent developers supposed to fix something when Apple won't explain what's wrong? We've now filed a formal appeal, which could take a month, with no visible queue position, progress updates or estimated timeframe. Meanwhile, we've already missed multiple planned marketing opportunities, and waiting could mean missing even more. We're not asking for guaranteed approval. We're asking for a fair review of what we've actually built. Has anyone else experienced this? What would you do? Wait for the appeal, hoping the App Review Board properly evaluates the app, even if it takes another month and we miss more deadlines? Withdraw the appeal and resubmit, hoping for a different reviewer, but risking another rejection without proper testing and further warnings against our developer account? I'd genuinely appreciate advice from anyone who's experienced something similar, especially those who've successfully appealed a 4.3(b) rejection. At this point, I genuinely don't know whether this is a reviewer misunderstanding, an automated rejection process, or something else entirely. But how can Apple determine that an app lacks originality when its defining functionality hasn't even been tested?

Hello Apple Developer Community and App Store Commerce team, I am looking for guidance on the review workflow for the first In-App Purchases of my app, Capture Link: UVC Monitor (Apple App ID: 6818688239). The first IAPs were submitted on October 5, 2026: Monthly auto-renewable subscription (Apple IAP ID: 6818721468) Non-consumable lifetime unlock (Apple IAP ID: 6818721648) Subscription group (ID: 22435932) Our macOS app (1.0, Build 16) is approved and Ready for Distribution. The current iPadOS app (1.0, Build 17) and both IAPs still show Waiting for Review on November 6. We verified in App Store Connect that the iPadOS review submission submitted November 3 contains the app version, monthly subscription, lifetime unlock, and subscription group. The current statuses show no rejection or developer action required for these items. The Paid Apps Agreement is active, banking is available, tax documents are in use, and IAP metadata and review screenshots have been supplied. We received confirmation of an expedited app review request on November 2. A production user has reported that purchase options cannot be loaded. I understand from an App Store Commerce Engineer reply that unapproved IAPs are not returned to production StoreKit. My questions: Given that the four items are included in the iPadOS review submission, is there any other first-IAP submission requirement we may have missed? Is this combination of states expected while iPadOS Build 17 is still Waiting for Review, or could it indicate a review workflow issue? What diagnostics or details would help Developer Support distinguish a normal queue delay from a stuck first-IAP workflow without withdrawing the existing submission? I have opened formal support inquiries and am seeking technical guidance here rather than requesting a separate expedited review. Thank you for any insight.

Hi all, I'm trying to stay patient, but I've run out of options and would really appreciate any help, from Apple or from anyone who has been through this. My app's first version with auto-renewable subscriptions has been in review since September. Timeline: Rejected on 4 October (Guideline 3.1.1). Fair enough, fixed and resubmitted on 15 October. Waited 13 days. Rejected on 28 October under Guideline 2.3.2, because my monthly and yearly subscriptions have identical promotional images. App Review asked me to make them unique or delete them. I replied on the submission within 20 minutes. No response, and none to the two follow-up messages I've left there since. The problem is that I can't do what App Review asked. In App Store Connect the image on both subscriptions is locked: no remove (—) option on hover, and the + / upload control doesn't open, in Chrome and Safari, with drag-and-drop too. Apple's docs say removed items can't be added back to the same submission, so I haven't removed the subscriptions. I've deactivated the only offer code, there are no win-back offers, and App Store Promotion was never enabled. New, distinct images are ready to upload. On the support side, I opened case 103005026336 on 28 October. I spoke to someone who was genuinely lovely and said they'd follow up, but that was a week ago and I haven't heard anything since. I've also requested an expedited review and booked an App Review appointment, the earliest available on 10 November. I resubmitted on 30 October with an explanation in the review notes, and it has been "Waiting for Review" ever since. My real question: should I cancel and start a completely fresh submission with new subscription products, and go to the back of the queue again? Or keep waiting? Weeks are turning into months, and the Android version has been approved and waiting the whole time. If anyone from Apple sees this, case 103005026336 is still unresolved, and all I need is the image field unlocked or someone to tell me how to proceed. Thank you.

Our app Powerful Progress: Goal Coach (Apple ID 6809707414) was resubmitted on October 31, 2026 after fixing the issues from the previous review (Guidelines 2.1(b), 3.1.1 and 4). It has been "In Review" since then with no messages from App Review. The submission includes version 1.0 (26), a first subscription group with two auto-renewable subscriptions, and a Lifetime In-App Purchase. We also sent an expedite request on November 4. Is there anything we can do or provide to help complete the review? Submission ID: a1b9ab04-923f-45ac-ba61-76dae5046341

Our app Ring-Ring® (Apple ID 6799744191), version 1.0 (build 1968), with its first in-app subscriptions, has been Waiting for Review since 31 October 2026. An expedited review was granted on 3 November, and we contacted App Review (case 30000003800448). The status has not changed since. The app is live on Google Play with paying members. Could someone from App Review take a look? Thank you.

I'm trying to enroll in the Apple development program as an Individual. After I accept Agreement it shows error: Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. I have checked my profile/account and all data are correct. First Name and Last name Age(older than 18 Payment card ( I already purchased apps/items in Appstore). I have tried master card, visa Address When I submit form to enroll development program I have checked HTTP request as well HTTP Request POST (406)  https://developer.apple.com/servicesenrollment/submitIndividualEnrollment Response creationTimestamp: "2020-07-03T14:15:39Z" httpCode: 406 requestUrl: "https:/developer.apple.com/services-enrollment/submitIndividualEnrollmen" responseId: "8575721d-e88c-44c1-984f-cae3cc8fc5f2" resultCode: 202000 resultString: "Your request could not be processed" userLocale: "en_US" userString: "Your request could not be processed" As you can see I got some unknown error: Your request could not be processed Without any details about reason.

Hello — posting here on the advice that community managers can flag submissions that appear stuck in the system. My app (Drip Rides) was submitted for review on October 30, 2026. An expedited review was requested and approved on November 1. Since then the submission has not moved at all: the status has read "Waiting for Review" continuously for over 136 hours (day 6), and the build has never entered review. I also never received any email confirmation of the expedite approval. I have an open support inquiry (30000003909762) and an earlier case (103017689548), and I have been filing regular follow-ups through the Developer Contact page, but every response so far has been an automated acknowledgment. Can someone check whether this submission is stuck in a processing state rather than simply waiting in the queue? If it is a "ghost build" situation, I would be grateful if it could be flagged for an engineer to push it into review. Thank you, Eric Evans, Developer — Drip Rides

Hello, I submitted my DSA trader information on October 26, 2026. I received the confirmation email "We received your trader contact information" the same day, but the status under Business > Compliance > Digital Services Act is still "In Review" after 10 days. My app MineFisk (Apple ID 6827249361) has been approved, and version 1.1 is "Ready for Distribution". But under Pricing and Availability, Denmark, Germany and Sweden show "Cannot Sell – Trader Status Not Provided". It is only available in Norway. Denmark is my main market, so the app is not available to my users. What I have tried: Support request by email on November 3, 2026 (case 30000003827017). Only the automatic reply so far. Phone support, but it shows "Phone support is temporarily unavailable due to high call volumes". I am an individual developer with a registered Danish business (sole proprietorship). I have not been asked for any documents. Could someone from Apple please look at this or escalate it? Is there anything else I can do on my side? Thank you.