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.

we met error when read data from https://api.appstoreconnect.apple.com/v1/salesReports then we found the file format changed before 7/29: api response byte data decompress gz get txt after 7/29: api response byte data decompress gz decompress gz get txt file need to decompress gz twice

Hello, All of my submissions across my account have been stuck in review for many weeks, which is well outside my normal turnaround. These are apps that have historically been approved within 24 hours or 2-3 days. Those updates are time critical. Singapore MRT just updated on 12 July. We are losing installs and impressions largely because of this, especially no reason is given. App: Singapore MRT Map Route Apple ID: 536957287 / Version: 3.0.1 App: Singapore MRT Map Route(Pro) Apple ID: 475976737 / Version: 3.0.0 App: Epic Cards Battle Apple ID: 1003611640/ Version: 2.6.3 On my side everything appears complete: metadata, build, review notes, demo account credentials, and all agreements in Agreements, Tax, and Banking are accepted. There are no messages in Resolution Center and App Store Connect shows no action required from me. I have contacted Developer Support but have not received a actual response. Could someone please confirm whether these submissions are correctly queued, or whether something is blocking them that requires action on my side? Thank you.

Last week I've submitted a new update for review doing the standard procedure for iOS, Mac and Vision. When submitting them both the Mac and Vision App switched to Waiting for Review state but the iOS one got stuck in Ready for Review state. I've tried a few times canceling the submission and submitting again and it always gets stuck in the "Ready for Review" state. Under the App Review section shows as Waiting for Review but on the general page shows Ready for Review. I've tried using the App Store Connect the API and the same thing happens. Any suggestions how to fix this?

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!

Hi, is anyone else having this issue? My new iOS builds finished processing successfully, but they only show “Expires in 90 days” and I can’t select them for internal or external testing. Export compliance is already completed, and I’ve also tried creating a new group, uploading another build, and refreshing App Store Connect, but nothing changed. Internal testing is still stuck on the previous build as well. Is this a current TestFlight/App Store Connect issue?

I am an account holder for my Team ID. I have paid Apple Developer Program too! Unfortunately, I see "Join the Apple Developer Program" and getting "Your Apple Account is already associated with the Account Holder of a membership." message. Also, I am getting "Unable to find a team with the given Team ID to which you belong. Please contact Apple Developer Program Support. https://developer.apple.com/support" error when I go to Certificates, IDs & Profiles. Help!!! Give me fix!!

I’m having an issue with the Apple Developer Program. I received a notification that the Apple Developer Program License Agreement has been updated and must be accepted in order to continue submitting and updating apps. The problem is that after signing in to my Apple Developer account, I don’t see any option to accept the new agreement. Instead, I’m shown a “Join the Apple Developer Program” screen, as if I’m not enrolled in the program, even though I have active apps on the App Store. In App Store Connect, I can see the agreement status as “Active (New Agreement Available)”, but there is no visible way to actually review or accept the updated version. Has anyone experienced a similar issue and knows how to fix it?

Hi everyone, I recently purchased an Apple Developer Membership using a newly created Apple Account. Currently, I am logged into this developer account only inside the Apple Developer app on my iPhone. Note that this same iPhone is primarily linked to my personal, separate iCloud account. When I try to log into the Apple Developer and App Store Connect portals on my MacBook via the web browser, I do not receive any 2FA verification codes on my phone. Here is what I have tried so far: Checked my SMS messages (no code received). Selected the phone call option for the 2FA code, but I did not receive any call. Verified that my mobile carrier is working normally. Since I cannot bypass the 2FA screen on the web, I am locked out of App Store Connect and cannot manage my membership. Has anyone encountered this issue with secondary accounts on the same device, and how can I resolve it? Thank you!

Hi everyone, I’m looking for advice on the best escalation path for an App Store Connect tax issue that is blocking our Paid Apps / In-App Purchase setup for a live app. Timeline: Jun 18, 2026: Opened a Finance Support case for tax information submissions. Since then: No update from Apple Finance. Current impact: Paid Apps / IAP cannot be completed, and users are already trying to purchase the Pro upgrade. I have also submitted a new Finance contact request under Tax information submissions. Has anyone dealt with a similar App Store Connect tax issue where Finance Support went quiet? Is there any escalation path beyond the Finance contact form and replying to the original iTSPayments email? Any guidance from Apple staff or developers who have been through this would be appreciated.

When submiting my W-8BEN (US Tax Forms) my citizenship is automatically set to Australia. This is incorrect as my citizenship is in Germany, but the issue is that I can not change the citizenship section because it greyed out and I can not select it. Can someone please provide me with advice as to how I can change my citizenship.Thank you

My app has been waiting for review since June 13 and has been under review since June 19. I would like to know if this is considered normal. I have already sent emails to Apple requesting a faster review and asking for an explanation regarding the delay, but I have not received a helpful response. The app is called "Piscineiros." Could any fellow developers please check if this review timeline is normal or share if you've experienced something similar? Any advice would be greatly appreciated.

Hello, My app MGY Fit (Apple ID: 6793196121, iOS, version 1.0.0, build 11) was submitted for review on July 23, 2026 and has remained in "Waiting for Review" ever since. It has never moved to "In Review". There are no messages in the Resolution Center and I have not received any request for additional information. Export compliance, content rights, and advertising identifier questions were all answered at submission, and the Review Notes include demo account credentials and steps to reach the main flows. This is the first submission for this app and for my developer account, so I understand a longer wait is expected. I wanted to check whether the submission may have been routed in a way that needs attention, or whether this is simply current queue volume. Any guidance would be appreciated. Thank you.

Hello Apple Developer Community and App Review Team, I received a Pending Termination Notice regarding Section 4.3 (Spam) for my games (Scream Bird and Hopscotch). I submitted a formal appeal 7 days ago detailing the technical context, but I have not yet received an automated confirmation email or a case tracking number. Full Context of My Situation: I had previously published a game called "Scream Bird" on this account, and that was the first time I received a 4.3 Spam error. It was the first time I'd encountered this error, as all my games and applications are designed by me, from the buttons to the characters and gameplay. When I received that error, I tried to understand and modify my game a bit, thinking it might have overlapped with an existing game. But that build continued to receive the 4.3 Spam error. This time, I really didn't know what to do. I intended to keep the gameplay but redesign everything. Strangely, while I was trying to redesign and change my game, I received an email saying that Apple was reviewing my app (the one that had just been rejected), and just minutes later, my game was approved and ready for distribution. This was the first time I'd encountered something like this. I thought the review team had re-evaluated my game and changed their minds. And since the game was approved, I didn't know what else to do and just continued working on other projects. Shortly after, Google AdMob approved it (because the game was already live on the store), so ads started appearing on the game (I think this was the issue, causing the system to automatically think my game had been flagged for content changes, but the content was already there; it was just that I had set a production ID for the ads at the time, so they weren't showing – that was partly my fault). But the problems didn't end there. Recently, I published a new game called "Hopscotch" and encountered the 4.3 Spam issue again. It was then that I really looked back at the binary files I built for my games and was shocked to realize that this might be the reason the automated system incorrectly flagged my games as spam. Technical Explanation (Godot Framework & Shared Native Libraries): I build all my games myself using Godot (3.x and 4.x). Regardless of the version, I write supporting libraries (mainly to call simple native features). Therefore, all my games will have files like: notch.a, share.a, haptics.a, local-notification.a, inappstore.a... You can check it out on my GitHub page; most of it is public. https://github.com/kyoz/godot-notch https://github.com/kyoz/godot-share https://github.com/kyoz/godot-local-notification https://github.com/kyoz/godot-haptics https://github.com/kyoz/godot-leaderboard https://github.com/kyoz/godot-native-rating https://github.com/kyoz/godot-flashlight etc... However, the entire game, from images, models, scenes... almost everything I designed myself, was packed into a single [game].pck file by Godot. This makes my Godot-built games look very similar in terms of binary, but in terms of content and gameplay, they are completely unrelated. My Commitment: I've been on my Apple journey for over five years now, and I've published 20 apps/games. The journey so far hasn't been easy. But I promise I've always complied with Apple's policies. I have never engaged in subscription scams, fake reviews, bait-and-switch tactics, or any of the fraudulent conduct described in the termination notice. I am respectfully requesting: Confirmation if my appeal submitted 7 days ago is actively under review by the App Review Board. A status update or Case Reference Number for tracking. I am fully cooperative and ready to provide full source code, Godot project files, or any documentation needed. Thank you so much for your time and assistance! Best regards, Phan Minh Cuong

I paid the $99 annual Apple Developer Program fee and submitted my first iOS app with the understanding that App Review would normally take approximately one or two days. It has now been six days, and the submission is still sitting in “Waiting for Review.” There has been no review, no request for additional information, no explanation, and no indication that anyone has looked at it. I understand that review times can vary, especially for a first submission, but six days without even entering review seems excessive. Developers are required to pay Apple before they can distribute an app, yet there appears to be no meaningful service-time commitment or communication when a submission remains untouched. Is this currently normal for first-time app submissions? At what point is a developer supposed to conclude that the submission is stuck rather than merely delayed? At this point, I am also wondering whether I should request a refund of the $99 membership fee, since the primary service I paid to access has not been provided within anything resembling the expected timeframe.

Hello everyone, I’m looking for advice from developers who may have faced a similar situation, as we appear to be stuck in a long-running loop of Guideline 4.3(a) rejections on iOS with no actionable feedback from App Review. Over an extended period, our iOS app has been repeatedly rejected under Guideline 4.3(a) (“similar or repackaged”), regardless of the changes we make. The responses from App Review consistently use the same high-level language and do not indicate what specifically is considered problematic. Some relevant context: The app is built with Flutter using a single shared codebase. The macOS version, built from the same codebase with the same overall structure and UI, has been approved without issues. The iOS version, using that same implementation, continues to receive 4.3(a) rejections. We do not use purchased templates and do not operate multiple developer accounts. Like most apps, we use some third-party and open-source components where technically appropriate. Across multiple submissions, we have tried to address the feedback as best we can by making changes to UI/UX, assets, metadata, internal structure, and overall product quality. However, App Review has not provided clarification even at a high level (for example, whether the concern is primarily related to UI/UX, code structure, metadata, user flows, or overall product framing). Requests for any directional guidance have resulted in the same generic responses, both in review replies and via support. This leaves us making blind changes without a feedback loop. As a result, it’s difficult to understand whether the issue is realistically correctable, or whether the app is effectively blocked due to similarity clustering or other non-obvious review heuristics. Any firsthand experiences, practical steps, or lessons learned would be extremely helpful.

Hi, I have a submission (App Store Connect ID: 6754396289) that has been stuck in "InReview" status for almost 3 months now. I tried with support multiple time but always received a generic reply. I am experiencing ususually long delay and would Appreciate any guidance from Apple Review or other developers. Can the Apple Review team check why submission iD:6754396289 is Stuck in "InReview" status and what information is needed to move it forward?

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

Hello, Our app, Platform Kiralama Rehberi, has been repeatedly rejected under Guideline 4.2 – Minimum Functionality, even though we have made substantial improvements after every review. We fully respect the App Review process. However, we strongly believe that the current version of our app provides sufficient functionality and meaningful value for its intended audience. Despite adding new features, expanding the content, and redesigning the user experience, we continue to receive almost the same general response without a specific explanation of what is still considered insufficient. The app is specifically developed for professionals and users in the manlift industry in Türkiye. It currently includes: A location-based interactive map showing nearby companies Distance calculations based on the user’s location Rental, manufacturer, distributor, spare parts, and technical service categories City and category-based filtering Detailed company pages with contact, address, and location information A searchable database of approximately 350–400 machine fault codes Favorites for companies, fault codes, and technical documents A technical and safety document library Native navigation between map pins, company cards, and detail pages After each rejection, we carefully reviewed the feedback and continued improving the app. We believe the app is no longer a simple catalogue or content viewer. It offers several interactive, practical, and location-based features designed for a specific professional sector. Our main concern is that the app may not have been fully explored during review, as the responses we receive remain almost identical despite the significant changes between submissions. We respectfully request that the app be reviewed again in detail, preferably by a different reviewer or App Review team member, so that all of its current features can be tested fairly and completely. We are confident in the usefulness and functionality of the app. We are not trying to avoid further development, but without specific feedback, it is becoming difficult to understand what additional functionality is genuinely expected. Could someone please advise us on the most appropriate next step, or help ensure that the app receives a fresh and detailed review? NOTE: For nearly two months, we have made extensive improvements to the app in an effort to move past this stage. During this process, we have tried to contact Apple Developer Support and have also communicated directly with the reviewer. However, the reviewer continues to send nearly the same response regarding Guideline 4.2, while we have received no response from the Support team for approximately 10 days. For this reason, we genuinely need the app to be reviewed in detail by a different reviewer and to receive clear, specific guidance on what is still considered insufficient. Thank you.

Hi, I created a Sandbox Apple Account in App Store Connect for testing StoreKit / Age Assurance sandbox scenarios. When I try to sign in on an iPhone through: Settings -> Developer -> Sandbox Apple Account I can enter the sandbox account email/password and I successfully receive the email verification code. After entering the email verification code, iOS asks me to add/verify a phone number. When I enter the phone number, I get this error: “Could not connect to iCloud. Verification codes cannot be sent to this phone number at this time. Please try again later.” I did not set any phone number when creating the sandbox tester in App Store Connect. The sandbox tester was created with only name, email, password, and country/region. Context: iPhone has Developer Mode enabled I am signing in via Settings -> Developer -> Sandbox Apple Account I am not trying to sign in through normal iCloud / Apple Account settings The sandbox account email is not used as a normal Apple Account Email verification works Phone verification has failed for more than a day Questions: Is phone verification expected when signing in with a Sandbox Apple Account? Is there a way to use Sandbox Apple Accounts / Age Assurance sandbox scenarios without adding a trusted phone number? Does this error usually mean the phone number is rate-limited/blocked, or that the sandbox account is stuck? Should this be handled by Apple Developer Program Support instead? Thanks!

Hello Applet, I’m experiencing an issue with StoreKit on a TestFlight build. My app uses auto-renewable subscriptions through StoreKit and RevenueCat. Configuration already verified: App installed through TestFlight (not debug). Bundle Identifier: com.ciborgu.vytalai Paid Applications agreement is active. In-App Purchase capability is enabled. Three auto-renewable subscriptions exist in App Store Connect. Product IDs match exactly between App Store Connect, RevenueCat and the application. RevenueCat initializes successfully. A Sandbox test account has been created. Tested on a physical iPhone. Device restarted and app reinstalled from TestFlight. VPN and iCloud Private Relay disabled. When attempting to purchase a subscription, the Apple payment sheet never appears. Our diagnostics indicate that StoreKit does not return any available products for the configured Product IDs, preventing the purchase sheet from opening. Expected Product IDs: vytalai_premium_monthly vytalai_premium_yearly vytalai_premium_yearly_intro Could you please verify if there is any issue with the App Store Connect configuration, StoreKit availability, or the processing state of these subscriptions on Apple’s side? If additional logs or diagnostics are required, I can provide them. Thank you. I have already contacted Apple Developer Support regarding this same issue. Previously, I was advised to schedule a technical support meeting. However, when I requested the meeting, my request was declined because of the subject of my issue, so I was unable to speak with an Apple engineer. Since I have now completed all the recommended troubleshooting and the issue still persists, I would greatly appreciate it if this case could be reviewed by the appropriate technical team or a StoreKit engineer. Thank you for your assistance.