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, I’m looking for assistance with an App Store submission that appears to have stalled after a Guideline 2.1 – Information Needed request. App: Costante: Trading Discipline Version: 1.0.0 Build: 6 Timeline: September 25: App Review requested additional information under Guideline 2.1. September 25: I replied the same day with all requested information, including a physical-device screen recording and detailed answers regarding the app’s purpose, services, availability, and functionality. September 28: I followed up through the App Review message thread in App Store Connect. September 30: I contacted Apple Developer Support regarding the delay and received confirmation that a support case was opened. October 1: There has still been no further response or progress on the submission. Could someone from the App Review team please check whether this submission is still actively being processed, and whether any further action is required from my side? I can provide the Submission ID and Developer Support Case ID privately through the appropriate Apple support channel if required. Thank you.

I hope this message finds you well. I’m reaching out to ask whether specific App Store Connect metrics available in the App Analytics dashboard can also be accessed via the App Store Connect REST API. I have reviewed the official API documentation, but I couldn’t find confirmation regarding the metrics listed below. Could you kindly clarify if the following metrics are available through the REST API? And if so, could you point me to the relevant endpoints or documentation? From the "Usage" group: Installations (Opt-in only) Active Devices Deletions (Uninstalls) From the "App Store" group: Impressions (Unique Devices) Product Page Views (Unique Devices) If these metrics are not available via the REST API, is there an alternative method to programmatically access or export them? Thank you very much in advance for your help and guidance.

Hello, Our app RANKnis (Apple ID 6813090542) has been in "Waiting for Review" since September 24, 2026. We have received no further communication since then. Timeline: Sep 24: submitted version 1.0 (Submission ID bdac0025-0af1-4ca7-a65d-43c9b182cd72) and received a Guideline 2.1 "Information Needed" request about limited App Review history. Sep 24: replied in App Store Connect with a screen recording and the requested details, and attached build 1.0 (15). Sep 29: opened an App Review Status request through Contact Us (case ID 102980088536). No response yet. We have not cancelled or resubmitted, so that we don't lose our place in the queue. Could someone on the App Review team confirm whether the submission is in the queue, or tell us if anything else is needed from our side? Thank you, Lucas Cordeiro, KAYA Tecnologia Ltda

Hello, I am an individual developer from Kazakhstan and I cannot complete the Digital Services Act trader form in App Store Connect. My app submission is blocked because of this. The problem Email verification in the DSA form worked fine. Phone verification does not: my Kazakhstan mobile number (+7) never receives the code. I tried "Resend text" and "Call me" several times since September 22. No SMS and no call ever arrived. The number is entered correctly — the form displays it in the right format. Manual verification App Store Connect Help says that if a phone number can't receive two-factor authentication codes, manual verification can be requested. However, this option does not appear anywhere in the form — the dialog only offers "Resend text" and "Call me". I am ready to provide any document proving the number belongs to me. Support replies are not delivered I opened two cases: • 102971839367 (September 22) • 102978683054 (September 28) Both cases show "Email with Apple Developer Support" in the case history (September 24 and September 30), but none of these emails reached my account email address. I checked all folders including spam. The case page does not let me open the replies, and phone support shows as unavailable. I have no way to read Apple's responses. Request Could someone from Apple please: 1. Look into these two cases and let me know what the replies said, and 2. Enable manual verification for my phone number, or tell me how to request it? If possible, please reply here in the thread, since email from Developer Support is not reaching me. Thank you.

Hello, I’m looking for assistance with an App Store submission that appears to have stalled after a Guideline 2.1 – Information Needed request. App: Costante: Trading Discipline Version: 1.0.0 Build: 6 Timeline: September 25: App Review requested additional information under Guideline 2.1. September 25: I replied the same day with all requested information, including a physical-device screen recording and detailed answers regarding the app’s purpose, services, availability, and functionality. September 28: I followed up through the App Review message thread in App Store Connect. September 30: I contacted Apple Developer Support regarding the delay and received confirmation that a support case was opened. October 1: There has still been no further response or progress on the submission. Could someone from the App Review team please check whether this submission is still actively being processed, and whether any further action is required from my side? I can provide the Submission ID and Developer Support Case ID privately through the appropriate Apple support channel if required. Thank you.

Hello! I have a new organization-level Apple Developer account and I'm stuck on the Tax Forms step in App Store Connect (https://appstoreconnect.apple.com/business). The system is showing me U.S. Form W-9 as the only option, but in my case filling out a W-9 would be incorrect — and I'd appreciate guidance from anyone who has resolved this. My setup: I am a non-US individual (not a US citizen, not a US resident, never lived in the US). I am the sole owner of a single-member LLC registered in the US (set up via Firstbase specifically to distribute a mobile app). For US federal tax purposes, this LLC is a disregarded entity — it's not treated as a separate taxpayer from its owner. Why W-9 is not the correct form in my case: The IRS instructions for Form W-9 explicitly state: "If the owner of the disregarded entity is a foreign person, the owner must complete an appropriate Form W-8 instead of a Form W-9. This is the case even if the foreign person has a U.S. TIN." Form W-9 also requires me to certify, under penalty of perjury, that I am a US person — which I am not. The LLC itself doesn't certify anything on a W-9 because it's disregarded; the IRS looks through to the beneficial owner, who in my case is a foreign individual. The correct form for me should be W-8BEN (Certificate of Foreign Status of Beneficial Owner — Individuals). What I've already tried: I opened two support cases 4 days ago and have not received a substantive response yet: Apple Developer Support — Case ID: 20000112974233 Ack Tax / Tax category settings — Team ID: 7YYWN3MYCY, Case ID: 19944616 My questions: Has anyone in the same situation (non-US individual, sole owner of a US single-member LLC) successfully switched the tax form from W-9 to W-8BEN inside App Store Connect? If so, how? Is there a specific path in the Business / Tax Forms section to declare the beneficial owner as a foreign individual that I might be missing? Is there an escalation channel beyond the standard support cases for tax-form issues that are blocking onboarding? Thanks in advance for any pointers.

Feedback: FB25016556 (includes sysdiagnose and device log archives) Since our Apple Developer Program membership lapsed on Sep 26, 2026 (renewed Sep 27), Product.products(for:) returns an empty array for every In-App Purchase of our app, in both production and sandbox. No error is thrown. Customers can't subscribe. App: bundle ID com.thefuntasty.gastromapa, live version 2.2.1 (worked fine until Sep 26, no code changes since). Products (both Approved, available in all countries, priced, localized): com.thefuntasty.gastromapa.subscription.premium (auto-renewable) com.thefuntasty.gastromapa.donation (non-consumable) Verified against TN3186 / TN3188: Membership active, latest Program License Agreement accepted (Account Holder checked) Paid Apps Agreement Active (effective Sep 29, 2026), nothing left to sign Bank account and tax forms Active Product IDs and bundle ID match the app record, In-App Purchase capability enabled on the explicit App ID Sandbox test build signed with a freshly regenerated development profile Apple Developer Support (phone) confirmed account, agreements and products look correct and referred us here storekitd log, identical in production and sandbox: Requesting Media API product batch ["com.thefuntasty.gastromapa.subscription.premium"] ... response_status=200 Media request MediaAPIProductRequest correlation key: KKP646ABIQJTWR5GGC3UBLBJDU Ignoring empty product response Correlation keys: Oct 1, 2026, 14:15 CEST, production, iOS 27.0.1 (24A446): KKP646ABIQJTWR5GGC3UBLBJDU Sep 30, 2026, 15:30 CEST, production, iOS 27.0: 3VRU2QHLFRRMP2UBTYG4ZSIBPQ Sep 30, 2026, 15:45 and 15:51 CEST, sandbox: VF6Y3XNFTZXPBRKX6VCKSJNB3U, V7Q3K5JTJ46PB6D2HGKCY5RINU This looks similar to https://developer.apple.com/forums/thread/845526. Could someone from Apple check whether our In-App Purchases were deactivated in the store catalogue when the agreement expired, and reactivate them? It's blocking all revenue for the app.

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 everyone / Apple Support Team, Our app update has been stuck in "In Review" for over 60 hours following an expedited review approval, and we would appreciate any advice or guidance from the community or Apple Staff. Here are the details for our submission: App Name: Luklok Casino: Slots & Games App ID (Apple ID): 6776359755 Version: 0154 Platform: iOS Support Case ID: 102981501483 Submission Timeline: Sep 24, 2026, 8:15 AM: Submitted & entered Waiting for Review Sep 28, 2026, 9:24 AM: Expedited review granted & status changed to In Review Current Status: Still In Review (No Resolution Center messages or extra info requested) As this is a routine update containing bug fixes and performance improvements, our server and backend test environments are all fully operational and monitored. Has anyone recently experienced similar extended review times for standard app updates? If any Apple Staff member sees this, could you please help check if the case is proceeding normally or if additional information is required? Thank you very much for your time and help!

Every App Store Connect upload I sign with my Cloud Managed Apple Distribution certificate is rejected with ITMS-90035 ("Code failed to satisfy specified code requirement(s)") for the app binary and its widget extension. It happens from Xcode Cloud and from a manual Organizer upload alike. I think I have found the cause, and it looks like a Unicode normalization bug in cloud-managed signing. The certificate holder's name contains an umlaut: "Apple Distribution: Jonathan Thorsten Müller (…)". In the certificate the "ü" is precomposed (NFC, UTF-8 c3 bc). In the designated requirement that the export writes into the signature it is decomposed (NFD, "u" + U+0308, UTF-8 75 cc 88): certificate subject CN ... 4d c3 bc 6c 6c 65 72 ... ("Müller", NFC) designated requirement leaf CN ... 4d 75 cc 88 6c 6c 65 72 ... ("Müller", NFD) The bytes differ, so the signature can never satisfy its own designated requirement. It reproduces with Xcode 27.0's App template, unmodified, and without uploading anything: Archive for a generic iOS device. With no distribution identity in the local keychain, export for App Store Connect to a folder (export options: method app-store-connect, destination export, signingStyle automatic). DistributionSummary.plist shows "Cloud Managed Apple Distribution". xcodebuild -exportArchive -archivePath MyApp.xcarchive -exportPath out -exportOptionsPlist ExportOptions.plist -allowProvisioningUpdates Verify the exported app: codesign --verify --strict -vv Payload/MyApp.app Result: "valid on disk", then "does not satisfy its designated Requirement". Compare the requirement with the certificate's subject: codesign -d -r- Payload/MyApp.app codesign -d --extract-certificates Payload/MyApp.app openssl x509 -inform DER -in codesign0 -noout -subject -nameopt RFC2253,-esc_msb | xxd The same archive exported with a regular Apple Distribution certificate (same name, private key in my keychain) writes the NFC form, verifies, and App Store Connect accepts that upload. That works for manual uploads only. Xcode Cloud always signs with the cloud-managed certificate, so I cannot distribute from Xcode Cloud at all. Setup: Xcode 27.0 (27A266a) locally and in Xcode Cloud, automatic signing, one team, no custom code-signing flags. Product name, bundle IDs and file names are plain ASCII. Questions: Is this a known issue with cloud-managed signing and non-ASCII certificate names? Is there a supported way to have Xcode Cloud sign without hitting it in the meantime? If you see ITMS-90035 on Xcode Cloud and your name (or your team's) has an accent or umlaut in it, you may be hitting the same thing: run step 3 on an exported IPA and check.

Hey, we're stuck in a loop and need help from App Review. App: Latent: Focus Camera (Apple ID 6788947658) Submission: 302fb800-e336-4f51-afef-6bdffdc59320, version 1.0.1 (30) Latent is free. Build 30 has no in-app purchases, no paywall, and no purchase code. We keep getting rejected under 2.1(b) because the reviewer can't find "Latent Pro Yearly" (6813310670) and "Latent Pro Monthly" (6813311816) in the binary. That's correct, they aren't in it. They're leftovers from before we went free. The rejection says to remove them from App Store Connect. We can't: They were never approved. Both show Developer Rejected, with 0 territories, and they aren't part of the submission. There's no Delete button in App Store Connect. DELETE /v1/subscriptions/{id} returns 409 SUBSCRIPTION_DELETE_NOT_ALLOWED. The subscription group can't be deleted while those two are in it. We replied in Resolution Center on Sept 29 and resubmitted. Can someone remove these two subscriptions on your side, or let the reviewer know they aren't part of this version? Thanks, Malcolm

Hi App Review team, • App: Offing — Offline Chat • Apple ID: id6793304688 • Version: 1.1.0 (build 14) • Submission ID: 443edd98-a4e6-4e0e-98ca-794bfb8583c2 On Sept 2 the app received a Guideline 2.1(b) Information Needed request about paid content. I replied that the app is completely free, with no In-App Purchases, subscriptions, accounts, or backend, since it works offline over Bluetooth. I resubmitted the same day. It waited until Sept 19 and has been In Review since then, 11 days as of today. I have a newer build ready but don't want to withdraw this one and restart the queue. Could someone check whether anything else is needed from me? Thank you!

I am having an issue with both In-App Purchases and auto-renewable subscriptions using the current App Store Connect submission workflow. My app was previously submitted for review along with its IAPs and first auto-renewable subscriptions. The app itself was approved, but the IAPs and subscriptions were not approved with it. Afterward, the IAPs/subscriptions showed “Developer Rejected.” I did not intentionally reject these products individually. Because App Store Connect states that the first auto-renewable subscription must be submitted with a new app version, I created a new version (1.1.8), uploaded a new binary, and added version 1.1.8 for review. I now have the following situation: • My In-App Purchases show “Ready for Review.” • My subscription group shows “Ready for Review.” • Both auto-renewable subscriptions show “Ready for Review.” • The Add for Review controls for these products are disabled, so I cannot add them to another submission. • App Store Connect shows only one Draft Submission. • When I open that Draft Submission, the only item listed is iOS App 1.1.8. • None of the IAPs, the subscription group, or the individual subscriptions appear in the Draft Submission. Therefore, App Store Connect appears to consider the IAPs and subscriptions Ready for Review, but they are not actually visible in any Draft Submission and I have no way to add them to the 1.1.8 submission. I have tried removing iOS App 1.1.8 from the Draft Submission and adding it again. This does not change the status of the IAPs or subscriptions and does not make them available to add to the submission. I have contacted Apple Developer Support twice, but so far they have not been able to provide a solution. Has anyone encountered this with the new App Store Connect IAP/subscription submission workflow? Is there a way to reset the review/submission state of IAPs and subscriptions that show “Ready for Review” but are not actually present in any Draft Submission? I would strongly prefer to keep the existing product identifiers rather than recreate all of the IAPs and subscriptions.

Hi everyone, I’m stuck with some auto-renewable subscriptions in App Store Connect. I can’t submit them for review, remove them from the submission, or get them out of the “Ready for Review” state. I’m hoping someone has experienced this before. Here’s what happened: I submitted a new app with 4 auto-renewable subscriptions. The app was rejected because 2 of the subscriptions were not being used in the app. I removed those 2 subscriptions from the submission and submitted the app again. The app was eventually approved by Apple. However, I now have the following problem: The 2 subscriptions that were submitted and approved are showing an “Accepted” status instead of “Approved”, so they are not available in my app. The other 2 subscriptions that I removed from the submission are now stuck in “Ready for Review”. I cannot submit those subscriptions for review. I also tried creating new subscriptions, but I ran into the same issue. When I try to add them to the submission, App Store Connect shows this error: "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." After that, the new subscriptions also become stuck in :Ready for Review", and the "Add for Review" button is disabled. At this point, I have no way to submit the subscriptions for review, which means I cannot get In-App Purchases working in my app. It seems like something may be wrong on the App Store Connect side. Has anyone experienced this issue before? If so, is there a workaround or anything I can do to resolve it? And if there is an Apple engineer or App Store Connect specialist here, I would really appreciate any help. Thanks!

I have a question about Product page headers. I can see some apps like TikTok and Snapchat are using this feature. Is it only available for some accounts? If it is not currently available for all developers, when should we expect to gain access to it?

Hello, My app 岩片 (YanPian, Apple ID 6800534375, bundle ID com.ajin.heartrate) was rejected on September 19, 2026 under Guideline 4.3(a) - Design - Spam. Submission ID: 69a97b70-0219-42fe-861f-ce737bc19b38, version 1.0 (202609061946). The app is original. I wrote it myself, it is the only app on my account, I have not submitted similar apps on any other account, and I have never used or bought an app template. It is a tool for lead climbers who film their climbs from a tripod far below the wall: Heart-rate overlay: pick a climbing video from Photos. Heart-rate samples recorded by Apple Watch are read from HealthKit (read-only), matched to the video by capture time, and drawn on the video with a heart-rate graph. Zoom and follow: the climber is tiny in a wide shot, so the app crops in and follows them with editable keyframes (on-device person detection). Live capture, with an optional Zhiyun CQ5 gimbal that moves only when the climber is about to leave the frame, and an optional Apple Watch companion. Everything runs on device. No account, no backend. What I have done so far: September 20: replied in App Store Connect with the explanation above. No response yet. September 29: submitted an appeal to the App Review Board. An earlier appeal got no confirmation, and I cannot find any record of it. The review was done on an iPad Air. The app is iPhone-only. Without a climbing video in Photos, the home screen only shows "New project" and "Live capture", so I understand it may look like a generic camera app. A screen recording of the full flow is attached to the submission in App Store Connect. If a specific app looks similar, I would be glad to know which part so I can change it. Could someone from App Review take a look? Thank you.

For an In-App Purchase made by a customer whose App Store account is in the Saudi Arabia storefront, where Apple acts as commissionaire and remits VAT, does Apple issue the customer any tax document (a VAT invoice or a tax receipt), or is the customer's purchase history the only record available? Apple's support article 'View your purchase history for the App Store and other Apple media services' (support.apple.com/en-us/118212) documents viewing purchase history only — the words 'receipt', 'invoice' and 'tax' do not appear on that page.

Does changing the price of an already-approved In-App Purchase trigger a new App Review, or does the new price take effect without review? App Store Connect Help states that changes to localized information require review and that 'New pricing will go into effect immediately', but never says explicitly whether a price change alone is exempt from review. We need this for a non-renewing subscription sold in the Saudi Arabia storefront.

Can an In-App Purchase that has reached the 'Approved' state ever be deleted from App Store Connect, either in the UI or through the App Store Connect API? App Store Connect Help documents no deletion procedure and no 'deleted' status. If deletion is possible, is it blocked while the product has existing purchases, or while it is still available for sale?

Hello, I recently received a Pending Termination Notice for my Apple Developer Program membership. The notice states that my account was identified as having provided false or fraudulent account information, documentation, or representations. I respectfully disagree with this finding. All information and documents I provided to Apple during enrollment and throughout my Developer Program membership are genuine and accurate. I have not intentionally provided false information, fraudulent documentation, or misrepresented my identity. I have complete original supporting documentation available and am fully willing to provide it again to Apple for verification, including identity and other relevant account verification documents. I have already been advised to submit an appeal to the App Review Board within the stated 30-day period, which I intend to do. I would appreciate guidance from anyone who has experienced a similar situation: Is there any additional verification process I should request as part of the appeal? Is there a recommended way to provide supporting identity documents for manual verification? Should I also contact Apple Developer Support in addition to submitting the App Review Board appeal? Is there anything specific that should be included when requesting reconsideration of a Developer Program termination related to Developer Identity? I am fully prepared to cooperate with Apple and provide any documentation necessary to verify the authenticity of my account information. My intention is simply to resolve any misunderstanding or discrepancy and have my Apple Developer Program membership reconsidered after verification. Thank you for any guidance.