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

I'm having issues with StoreKit 2 when trying to load my auto-renewable subscriptions on a physical device via TestFlight. It works perfectly in the simulator using a local .storekit configuration file, but when I install the app through TestFlight, StoreKit does not return any products at all. Instead, I get the error: "Storefront not available" What I've Tried: ✅ In-App Purchases are enabled on my device. ✅ Using a sandbox account (confirmed logged in under Settings &gt; Developer &gt; Sandbox Account). ✅ The app is signed correctly with automatic signing in Xcode. ✅ The product IDs are correct (they work in the simulator with the local StoreKit file). ✅ I enabled SK2DebugLogging, but I don't see detailed errors. ✅ Restarted the device and signed out/in of my sandbox account. ✅ Checked that the App Store region matches my sandbox account’s region. ✅ The app is not fetching products dynamically at all on a real device—just getting "storefront not available." Additional Notes The app is installed via TestFlight, not running in debug mode from Xcode. The app is signed in to the App Store with a real Apple ID (not the sandbox one). Apple confirmed that products don’t need to be "Ready for Sale" for sandbox testing. I checked the Console.app logs on my Mac, but nothing obvious showed up. What I Need Help With Why would StoreKit 2 fail to return products in TestFlight, but work fine in the simulator? What does "storefront not available" actually mean in this context? Any steps I might have missed to force StoreKit to fetch products properly? Any help would be greatly appreciated! 🚀

My main app contains a complete sub app, but when I put this app on TestFlight, the startup report says that The provisioning profile is invalid; The main app was launched separately and runs normally. Please help me deal with the issue of invalid preset description files. Thank you myapp.app --Contents --bin --subapp.app --Contents --MacOS --Frameworks --MacOS --Frameworks

Hello Developers, I submitted my app Score + for review on March 15, and it has been stuck in review for over 20 days with no progress. On March 22, I contacted Apple Developer Support, and they assured me that my app would receive an expedited review, but nothing has changed in the past two weeks. After waiting 20 days, I thought there might be a technical issue preventing my app from being reviewed, so I incremented the version number and resubmitted it. However, it is still not being reviewed. I am wondering if my app is: ❌ Stuck in the queue due to a system error ❌ Blacklisted for some unknown reason ❌ Delayed due to a backlog of reviews Has anyone else experienced such a long delay? What can I do to escalate this issue further? Any advice would be greatly appreciated! Thank you! Erdinç Ayvaz

I submitted my ID for review over a week ago, and it's still the same, I can't log in App Store Connect? How long have you been waiting? Have a nice day.

I am really struggling with registering my app in App Store Connect. I find the system to be complicated an unhelpful. I have two issues with my app. I can see the builds that I have uploaded from Xcode when I select "Add Build" from the "IOS App" page. But for some reason, I cannot select a build - as there is no error message or guide as to why I can't select the build, I am asking here. I have created a Subscription Group for my app in MONETIZATION -> Subscriptions. I have created the Reference Name and Product-Id. It has been saved. App Store Connect tells me there is Missing Metadata but once more gives me no clue as to what is missing and how to correct it. As far as I can see I have completed everything needed for the Subscription Group/Product. I would like to add a Trial Period to my subscription but I cannot see anywhere to do this. The UI for Apps Store Connect is terrible - I would expect errors to be flagged and some suggestions given as to why the error exists - nothing! Is there a helpful (and understandable) guide I could use for setting up the App and any suggestions from the forum as to what I need to do to get my app ready for review and testing in Test Flight. Thanks!

Hi all, I am dealing with a confusing issue relating to a beta build that I am trying to share over TestFlight. I have followed all steps and managed to upload a build to App Store Connect, but I mistakenly selected "Internal Only" when submitting from XCode. This build was accepted (See image), but then when I submitted a build that would be shareable externally, it was rejected under Guideline 4.3(a). I am unsure what had changed between the first and second build I submitted, and I have since updated the app page with more information and screenshots clearly explaining how this is different to other items available on the app store with no luck. Does anyone have any clue what I could do? Signed hopefully, Luke

I need to ship an urgent critical bug fix being experienced by paying users. AppName: Filters for Pictures: by LAVIE AppleID: 6743334853 My app has been in "In Review" status since a while -> I can see from our logs that the reviewer opened the app, went through first 4 onboarding screens and then quit the app without proceeding further. There has been no updates since then and app in just "In Review" state indefinitely. On App StoreConnect, I am also unable to "Remove From Review", I get Error with HTTP Status 409: STATE_ERROR.ENTITY_STATE_INVALID So, I cannot even remove the current build and push a new build for review. Our users are demanding a fix urgently so its critical to ship an update.

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

Is App Store Connect down? The system status says it is up, but my team and I aren't able to access it from multiple locations. https://developer.apple.com/system-status/

All of a sudden today I started getting logged out of AppStoreConnect randomly. I would be able to get back in after logging in, but then moments later, logged out. I tried switching browsers and clearing cache etc.. but now when I login, I just get an endless spinner. If I try to refresh the page, I'm brought back to the login page. It appears this isn't the first time this sort of thing has happened as I saw a post in Nov 24 regarding a similar issue.

Refer to the attached screenshots I am trying to push an update for an existing iOS app that I developed a few years ago (App ID: 1465985188) but I am getting this error: A required agreement is missing or has expired. This request requires an in-effect agreement that has not been signed or has expired. (ID: O4YFH7VPB2LECAUAVXR6G4WRFQ) (403) I checked my agreements page and there is no clear indication of any missing agreements left to sign or what not. I have tried different builds of this project to no avail. I am stuck in a rut and I have been already waiting two weeks for customer support to acknowledge my issue and get back to me. My membership is due in a couple months, and honestly, if this is not resolved by end of this month I am not gonna renew. Attaching screenshots of all the agreements, and as you can see all the agreements are signed.

I've tried different browsers, clearing cache and history, restarting and using different networks, but I still have no access to the business page. I have the account holder and admin roles and I have F2A on my Apple ID. I need to access the business section to submit my new build because it has a subscription. Any help, recommendations or guidance would be greatly appreciated.

The app that I install from testFlight to my phone has icon, but in the app store connect , when i navigate to the App, that app doesn't have an icon. Please telll me me how to add. I've tried asking ai, it says there's a place to add app icon in the app store> app information, but I couldn't find it.

Hi everyone, I’m hoping to get advice or hear from anyone with similar experiences. Our app Pixllove was originally rejected under Guideline 4.3 (“Spam”). We were later invited to an App Review call with Erica, who reviewed everything and confirmed verbally and in writing (April 8, 2025) that the spam classification was removed. She acknowledged that our app uses a unique concept and only required us to implement a pre-chat consent popup. We implemented exactly that: • A popup appears before any chat starts, displaying the match’s name, age, and distance. • Users must actively accept before the chat begins. • We show this clearly in our new demo video. • Full reporting/blocking/moderation is in place. However, after submitting the updated build, we were again rejected under a different interpretation of 1.2, with the reasoning that our app “connects users randomly.” This appears to be a misunderstanding, since no match occurred during their test – and it takes at least 2 users online for a match to happen. We explained this and even submitted a screenshot of the consent popup, which had been explicitly requested by Erica. Sadly, the reviewer ignored our message and Erica’s previous confirmation and labeled us as spam again. We replied and asked them to please review Erica’s note from April 8, but we haven’t received a response yet. We’re lucky to have a second review meeting scheduled for Tuesday, but this experience has been extremely frustrating and honestly, quite unprofessional — especially after being told the issue had been resolved. Has anyone experienced something similar? What can be done to ensure prior Apple Review decisions are respected by future reviewers? Thanks so much in advance, Emilija Pixllove Team

Hi everyone, I’ve been facing an issue with TestFlight external builds that I haven't encountered before, and I’d appreciate any insights. Background: I have an iOS app that was recently approved and released to the App Store. Prior to this, I’ve regularly submitted TestFlight builds (with updated version and build numbers) to both internal and external tester groups. Internal builds would appear instantly, as expected. External builds were also available almost immediately after selecting “Ready to Submit.” This was consistent for many iterations. Current Issue: After pushing the latest version to the App Store (which went through the standard review process and was approved), I prepared a new version for TestFlight testing. Here’s what happened: Uploaded a new build with a new version number and build number. It appeared instantly for internal testing as usual. When I tried adding it to the external tester group, the build got stuck in the “Waiting for Review” state. I uploaded this on Saturday night, and as of Monday noon, the status has not changed. I also cancelled that build and uploaded a fresh one with an incremented build number — still stuck in the same status. Additional Notes: The app’s ITSAppUsesNonExemptEncryption key is set to false in Info.plist. There is no missing export compliance warning on App Store Connect. The changes in the new build are minor — a few small updates, nothing significant. I tried decreasing the build number temporarily (which caused an error), then increased it again. No changes were made to permissions, app capabilities, or metadata that would typically trigger a longer review. Questions: Is this expected after an App Store release? Has anyone else experienced delays like this recently for TestFlight external builds? Is there anything I can do to expedite the review? Thanks in advance for any help!

This error appeared yesterday out of the blue. I'd been on appstoreconnect.apple.com working on an app update and later in the day when I tried to log in again I immediately get the error, "Failed to verify your identity. Try Again". No verification code is sent and it's not a password issue, as that's a different error. I'm able to log in to iOS devices and Apple's apps, like the App Store Connect App. I was even able to log in to the Apple Support App and change my password, but I still couldn't access any Apple websites. If I try to log in to icloud.com, searchads, appstoreconnect.apple.com, developer.apple.com, or appleid.apple.com I immediately get the same error and no 2FA code is sent. I've seen online that others have had this issue and some resolved it by appending a verification code to the end of their password, but that hasn't worked for me. (Even though Apple's sites fail to send the 2FA I was able to get a code by going into iOS Settings->iCloud->Passwords & Security->Send Code). Has anyone had this issue and been able to resolve it? I've seen online that people have periodically experienced this issue for years, but I've seen no solution other than the code-appending trick. Apple Developer Support and regular Apple Support haven't been able to help so far (they also told me to try appending a 2FA code to my password). I had to create another Apple ID just to be able to get back into this forum and also the Contact Support page. But now that I have a support case the only way I can communicate with the rep is by logging in with the ID that actually has the login issue. The issue may be rare, but it's been around for several years and Apple has set up its support systems in a way that makes it extremely difficult to get support in these circumstances. In fact, regular Apple Support has no ability to even transfer a call to Developer support. If anyone can help me with this I'll buy you a beer--heck, several beers. Thanks

I have developed several apps out of interest, and if everyone likes my app, I plan to truly become an independent developer. I used a name and icon similar to the existing app in the hope of gaining more app exposure. The App Store reviewer found an issue and gave me a 'Pending Termination Notice'. My account will be deleted within 30 days. I finally realized that this was an extremely foolish practice that undermined my integrity. After receiving the notification, I immediately responded through the appeal channel and admitted my mistake. I have already removed my app from App Store Connect, even though it hasn't been officially launched yet. I am determined not to make similar mistakes again and to become an excellent independent developer. There is another question that I am quite puzzled about. My application is considered to be: “Evidence of Dishonest or Fraudulent Activity App submissions from your account have engaged in concept or feature switch schemes to evade the review process, such as dynamically populating different app content after review, submitting apps with hidden features, repeatedly submitting misleading apps, and/or submitting apps with concrete references to content that you are not authorized to provide or is otherwise not appropriate for the App Store. “ I am a browser application that uses SwiftUI to write programs without using any third-party SDKs. I also did not attempt to evade the review. If the APP reviewer needs it, I can provide my source code. As a browser application, how can I avoid similar misunderstandings in the future? What I hope to get help with now: Will my appeal really be seen by the review committee? When can I expect to see a reply? I refresh my emails more than ten times a day to see if there are any new messages. Can my account still be restored? Otherwise, my developer dream would suffer a major setback. This audit has made me fully aware. The App Store is a high-quality platform, a rigorous platform, and any attempt to take shortcuts is not allowed. If my account can really be restored, I will be so happy that I can fly up. However, how should I resubmit my browser application and provide sufficient explanation to avoid being misunderstood and evading censorship? Thank you all for watching.

Hello All, I am hoping someone has a solution we are encountering. We recently upgraded to XCode 16.3 this week, and were putting together the next test build to push to TestFlight. However, the AppStore is rejecting the app with the following message. ITMS-90048: This bundle is invalid - Your archive contains paths that are not allowed: [._Symbols] We have never had this before and the problem is, there is no path named "_Symbols" in our IPA. Doing some searching online I have seen people report the same problem when build using Flutter or React, but we are using plain vanilla Swift and Native iOS. We also have not added anything significantly new to our project since our last release a couple weeks ago. Any suggestion on how to fix this would be greatly apprecaited. Sincerely, Stan R. - CaringBridge

Hi, My app currently offers a non-consumable in-app purchase to unlock all its features, and I would like to provide this full access for free to an organization with a few thousand Macs. Since Apple limits non-consumable in-app purchase promo codes to 1000 per app, this isn't sufficient for the organization's size. So I'm considering an alternative approach using an auto-renewable annual subscription with offer codes: Create a few thousand offer codes for an annual subscription. Users within the organization would redeem these codes. Instruct users to immediately unsubscribe after redeeming the code. The app would then check the in-app purchase receipt. If the receipt contains a transaction redeemed with an offer code, the app would treat this as a permanent unlock of all features. My concern is that repurposing an auto-renewable subscription in this manner—effectively turning it into a lifetime unlock triggered by redeeming an offer code and immediately cancelling—might violate App Store guidelines. Is using an annual subscription and offer codes this way likely to be compliant with App Store guidelines? Thank you for your guidance!

I received the following message in my email: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit. But I don't know how to find the problem. How should I find and solve the problem？