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.

Looking for anyone at Apple who can nudge an escalated Developer Support case, or any developer who has seen this pattern. App: "Peptide GLP Supplement Synergy", Apple ID 6805712020, live since September 11. Distribution method Public, status Ready for Distribution, age rating 18+. Symptom: the app does not appear in App Store search on iPhone for any query — including its exact name and the developer name — on multiple devices and Apple Accounts with no content restrictions. The App Store Search API still returns it. Timeline: from September 11 to 15 the app was findable by its exact (old) name only. On September 15 version 1.0.2 released with the app renamed to the current name. Since that rename it is findable by nothing, including the new exact name. Nothing in App Store Connect has been changed since the case was opened. Developer Support case 102966931238 was opened September 17; the representative reproduced the failure on September 18 and escalated it to the technical team. Urgency notes were added September 19 and 21. No update since. Has anyone seen a listing fail to re-index after a rename, and is there a channel that moves a case like this? Thank you.

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.

Our Apple Developer Program membership for Avorp LLC was recently terminated under Section 3.2(f), citing “documented indications of fraudulent conduct associated with” my account. I am trying to understand the basis for this decision. Avorp LLC is a legitimate and independently operated U.S. software company. Its enrollment information was verified by Apple, and the account currently has no published apps on the App Store. I have not engaged in fraudulent reviews, payment fraud, account circumvention, or any other dishonest activity through this developer account. Like I said we don't even have a published application yet. I also work professionally as a freelance software developer and have previously worked on unrelated client projects involving Apple development resources. If an association with a former client account, project, device, or development environment contributed to this termination, I would like to clarify that such client work is entirely separate from Avorp LLC and does not imply ownership of or responsibility for the client's account or activities. The termination notice does not identify the specific activity, account, transaction, application, or association that Apple considers fraudulent. I have already submitted a reinstatement request. I am posting here to ask whether an Apple representative can clarify the appropriate escalation path for a manual review of the account associations involved in a Section 3.2(f) termination. I am fully prepared to provide company records, contracts, client-work documentation, or development records if needed to verify that Avorp LLC is independent and legitimate.

I got message in "AppStore connect" saying that there is a new version of the new version of the agrrement (Your Paid Applications agreement has a new version)When clicking on the "Agree" button for the renew for the Paid app agreement i get an error message saying there is a problem, but not what problem,. This is the error message. "We are currently unable to process your request. Please try again later."Ive gottten this message for several weeksl I have been trying different versions, with the same result. I even tried to send a support case to apple, but the request has been unanswered for 3.5 weeks now. I diont know what to do..

I reached out to Apple Developer Support and they directed me to the forums. This video "Explore Retention Messaging in App Store Connect" shows a "Retention Messaging" section at the 3:21 timestamp of the video, within "Subscriptions" below the "Billing Grace Period" section. For the apps in our account, there is no "Retention Messaging" section available within the Subscriptions area. I am not asking about the API. I do not believe the API is required in order to have the Retention Messaging section show up in App Store Connect. In the video, the speaker says “I'll share an overview of Retention Messaging, and how to set it up in App Store Connect” and she shows how to navigate there. While she explains that “Real-time Retention Messaging is powered by the Retention Messaging API” - she also says that you can “create the same views using real-time Retention Messaging as you can when using retention messages in App Store Connect.” Is there something that we need to do in order to get access to this area of App Store Connect so we can set up Retention Messaging? Thank you so much.

Hi all, Hoping someone has run into this or has advice. My App Store Connect account is registered as an Individual, with the legal entity/account holder under my name. I added a bank account, but the Account Holder Name on that bank account belongs to a different person than the name on my developer agreement. That other person and I are both Admins on the same App Store Connect team. It's now been well past the standard 24-hour processing window, and the bank account is still showing "Processing," with the usual banner: "Your banking updates are processing, and you should see the changes in 24 hours. You won't be able to make any additional updates until then." Separately, my Canadian GST/HST Form 506 also shows "Missing Tax Info," and my Paid Apps Agreement is "Pending User Info," so I suspect these two issues may be related/compounding. Questions: Has anyone successfully gotten Apple to approve a bank account where the Account Holder Name doesn't match the developer account's legal entity name, when both people are Admins on the same team? If not, has anyone been able to get Apple to cancel/reset a stuck bank account submission so they could resubmit under the correct account holder name? I can't edit it myself while it shows "Processing." Any luck getting a timely response from the Financial Information contact form specifically, versus general Developer Support (which just redirected me to documentation)? Appreciate any insight trying to avoid this dragging on for weeks like I've seen in a few other threads here. Thanks!

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.

HiI'm trying to send to review my app without success. when I try to upload my geojson file, which is formatted like this:http://pastebin.com/j0Mmedaythe iTunesConnect doesn't let me save the file and beside the upload field I'm seeing a red warning icon saying:"your routing app coverage file must be in the geojson format"This is very frustrating, it's since this morning that I'm trying to uploading my updateI've also tried with the standard example file provided by Apple, and it keeps saying the same error.Any help would be appreciated

We are writing about a sudden change in App Store Connect validation for our iOS app. A build with MinimumOSVersion 12.0 uploaded successfully on 8 September 2026. An otherwise equivalent build was rejected on 16 September 2026 with a 409 validation error. We have not found an official announcement that 12.0 is no longer acceptable, and we would like confirmation of the current rule and when it took effect.

Radio Dad (App ID 6798412909, version 1.0) is an internet radio player: it reads the radio-browser.info directory and plays each station from the broadcaster's own public stream URL, on the listener's device, with nothing hosted or re-streamed by us. It also plays podcasts from their public RSS feeds via Podcast Index. It was rejected under 5.2.3 (Legal: Intellectual Property, Audio/Video Downloading) on 26 August and again on 21 September, each time with the request to "attach documentary evidence evidencing that you have all necessary rights or permissions to the third-party audio or video streaming, catalogs, and discovery services." We have attached, in the App Review Information section, a signed statement with exhibits: the directory's public-domain dedication and API terms permitting commercial use; Podcast Index's published terms; a survey of 2,000 stream addresses showing the broadcasters' own servers serve the streams unauthenticated (97.4%) and identify themselves in the transmission (84% name the station, 60% their own website, 44% set icy-pub: 1); the directory's owner mechanism, under which only the stream owner can change or delete a listing; and our own takedown path, actioned typically within 48 hours. The app cannot save, convert or download a radio stream, and accesses none of the services the guideline names. The reply to the second submission was "The issues we previously identified still need your attention", without saying what form of evidence would resolve them. For publicly broadcast streams there is no rights holder to obtain a licence from beyond the broadcaster, who publishes the stream for public reception. Submission ID 448bc0d6-d797-444b-934f-9f0d7c1a5a28. We have asked for an App Review Appointment in the Resolution Center. If App Review can say what document would satisfy 5.2.3 for this kind of app, we will provide it.

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,

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.

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)

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.

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 the developer of FOS Social (Apple ID: 6755471015), a creator-membership marketplace currently in TestFlight. I've submitted the Advanced Commerce API access request form twice and have not received any response, confirmation, or status update. My most recent submission has Request ID: UVQ7FUZVV3. Our use case: FOS Social is a social platform where viewers subscribe to individual content creators through independent auto-renewable monthly subscriptions across three tiers ($10 / $17 / $29). A single viewer must be able to hold concurrent active subscriptions to multiple creators at the same tier — for example, subscribed to Creator A at Gold and Creator B at Gold simultaneously. This matches Apple's stated eligibility model for the Advanced Commerce API: "exceptionally large catalogs of subscription content — apps that include frequently added content from multiple creators, where each creator's offering is merchandised as a single auto-renewable subscription." Why standard StoreKit doesn't work for us: We currently reuse one product ID per tier across all creators (e.g. com.fosssocial.creator.gold.monthly). When a viewer already subscribed to one creator at Gold tries to subscribe to a second creator at Gold, StoreKit returns "already subscribed" and treats it as a renewal rather than a new independent subscription. Pre-creating a separate subscription group per creator in App Store Connect is not feasible since our creator base is dynamic and growing. My questions: Is there any way to check the status of an Advanced Commerce API access request, or a typical response timeframe we should expect? Is there anything that commonly causes these requests to go unanswered (e.g. submission not made by the Account Holder, app still in TestFlight, missing information)? Is there a recommended escalation path when the request form has been submitted multiple times with no reply? I've also opened a support case (Case ID: 102934491974) but wanted to ask here as well in case anyone from the community or Apple has guidance. Thank you!

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.

Hello Apple Developer Team, I've followed the AppStoreConnect API documentation and created the following: I've created a API Key in App store > Integrations > Teams key, gave the role as admin. Created a valid JWT token When fetching the GET v1/apps, I can see the list of apps. Also I was able to make GET v1/users as well successfully. I've the valid bundle Id and capabilities enabled in the developer portal. Facing an issue while creating an app in App Store using AppStoreConnect API using POST call: This is my ruby script: response = api_request( method: :post, path: "/v1/apps", token: token, body: { data: { type: 'apps', attributes: { name: APP_NAME, primaryLocale: LOCALE, sku: "SKU#{Time.now.to_i}", bundleId: BUNDLE_ID, platform: 'IOS' } } } ) It gives me below error: { "errors": [ { "id": "09b465fc-316f-47b4-9bc3-9c340cb966aa", "status": "403", "code": "FORBIDDEN_ERROR", "title": "The given operation is not allowed", "detail": "The resource 'apps' does not allow 'CREATE'. Allowed operations are: GET_COLLECTION, GET_INSTANCE, UPDATE" } ] } Did anyone was able to successfully create the app in App Store via AppStoreConnect API? Could you please help me identify the root cause for the above issue and provide some inputs so that I could work on resolving them and move forward in the deployment process. Appreciate your help in reviewing this. Thank you, Santosh

My app is rejected and I have fixed the issues and resubmitted the app last week. But after 3 days, app status has not changed yet . It should change because I have asked for expedited request and it is accepted. So, what should I do next. Submission ID 61ec5cdd-fe09-4023-8e46-b85988084ef7 App Name- Prime Ferry

I have a very embarrassing problem. that I can't transfer my macOS app to another account. and above is wrong picture. I already tried to delete the apps group. but it doesn't work. this transfer is very important for our team. if anyone can tell me how to do, I will be very grateful.