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 have received an invitation to a development team in the Apple Developer Program. Having filled the form out and completing the image challenge successfully, tapping on continue simply results in the button graying itself out. The JavaScript console shows the following error when this happens: { code: -4 data: "Destination unavailable. 500" message: "Application error." } I have tried this process in Safari, Chromium, as well as on mobile data on my iPhone, and the result is the same each time. Other messages in the console: [Warning] 30 console messages are not shown. [Log] pm-rpc response recieved at – "" (widget-a72347aab29cc0b7fb82.js, line 2) [Log] success - rpc: 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] will send 'receivePingRequest' for rpc: 'formRendered', number of retries left: 1 (widget-a72347aab29cc0b7fb82.js, line 2) [Log] - will send rpc message for 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] pm-rpc response recieved at – "" (widget-a72347aab29cc0b7fb82.js, line 2) [Log] success - rpc: 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Error] Blocked a frame with origin "https://appleid.apple.com" from accessing a frame with origin "https://appstoreconnect.apple.com". Protocols, domains, and ports must match. [Log] will send 'receivePingRequest' for rpc: 'formRendered', number of retries left: 0 (widget-a72347aab29cc0b7fb82.js, line 2) [Log] - will send rpc message for 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] pm-rpc response recieved at – "" (widget-a72347aab29cc0b7fb82.js, line 2) [Log] success - rpc: 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] - will send rpc message for 'formRendered' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] failure - rpc: 'formRendered', reason: reached maximum retries. (widget-a72347aab29cc0b7fb82.js, line 2)

I just successfully enrolled in the Apple Developer Program today. After receiving the enrollment confirmation email and completing the payment, I tried to access App Store Connect. However, I am stuck on the Apple Developer Agreement page: https://appstoreconnect.apple.com/review_agree When I click the “Agree” button, nothing happens and I cannot proceed into App Store Connect. The page does not advance, even after multiple attempts. Using browser DevTools, I found that clicking Agree triggers the following request: POST https://appstoreconnect.apple.com/olympus/v1/termsSignatures // Request payload { "data": { "type": "termsSignatures", "attributes": { "termsType": "RAD", "acceptMarketingCommunications": false } } } // Response { "errors" : [ { "id" : "bf5f232a-97ea-4239-a8ba-13b3ce2cf91f", "status" : "409", "code" : "ENTITY_ERROR.ATTRIBUTE.REQUIRED", "title" : "The provided entity is missing a required attribute", "detail" : "You must provide a value for the attribute 'version' with this request", "source" : { "pointer" : "/data/attributes/version" } } ] } Because of this, I am completely blocked from accessing App Store Connect, even though my Developer Program enrollment is confirmed and active. Question Has anyone encountered this issue before? Is there a workaround to accept the agreement manually? Any insight or confirmation would be greatly appreciated. Thanks in advance.

One of our apps has 85% stuck in Billing Retry -- We are so confused. All the users are from the US, and have a one-week free trial. We had 1,000 subscriptions expire from this issue. So any help would be so appreciated.

Hi all, We can’t install our app from TestFlight. The app is visible in TestFlight for invited internal testers, but tapping Install fails immediately with: “The requested app is not available or doesn’t exist.” --Setup-- Distribution: TestFlight – Internal Testing Internal group created and testers added (invite accepted) Build processing status in App Store Connect: Complete TestFlight build status shows: Ready to Submit / Prepare for Submission Minimum iOS deployment target: iOS 15.0 Version/Build: 1.0.0 (1) What we tried Confirmed tester is signed into TestFlight with the same Apple ID email that was invited Removed/added testers to the internal group and resent invites Reinstalled TestFlight, signed out/in Verified build is assigned to the internal group Set and saved Monetization → Pricing and Availability → App Availability (All Countries/Regions) Question Has anyone resolved this issue? Is there a known TestFlight/App Store Connect stuck state that causes this error even for internal testing? Any recommended steps (new build number, group reset, availability/pricing settings, etc.)? Screenshots available (TestFlight error + App Store Connect build/group view). Thanks.

I have two apps stuck in "Waiting for Review" status: App 1: Submitted Dec 20, 2024 (still waiting) App 2: Submitted Jan 12, 2025 (still waiting) I've requested expedited reviews but haven't heard back. I know the holidays can cause delays, but it's been over 3 weeks for the first app. Has anyone else experienced similar delays? If anyone from Apple's review team sees this, could you check on these submissions? Happy to provide more details if needed. Thanks guys

Hello everyone, I successfully submitted my iOS app build to App Store Connect via EAS(expo.dev). The submission logs confirm successful upload, but the build is not visible in App store connect TestFlight → Builds after several hours. Submission was successful according to logs: "Successfully uploaded package to App Store Connect" and "The app has been submitted successfully." Has anyone experienced a problem with this? Can I get some information? Thank you.

I have uploaded my build 10 days ago, still it is in processing. FYKI: The app size is 533 MB. Now two more builds were added and that is also in processing. Please help us.

I successfully archive my app but when I try and distribute it via XCode I get this error: But I do have that permission. I tried signout and sign in on XCode but still same error. Help!

I'm stuck in an impossible situation with DeviceActivityReportExtension on iOS 18. THE ISSUE: Configuration that works on device (iOS 18.2): Info.plist has only NSExtensionPointIdentifier Swift code uses u/main attribute App installs and runs perfectly Extension works correctly App Store validation FAILS: "Missing NSExtensionPrincipalClass" Adding NSExtensionPrincipalClass (as validation requests): Device installation FAILS with Error 3002 Error says: "NSExtensionPrincipalClass key is not allowed for this extension point" Cannot test on device Validation would likely pass ENVIRONMENT: Xcode 16.2 iOS 18.2 Extension point: com.apple.deviceactivityui.report-extension EVIDENCE IT'S WIDESPREAD: Apple Forums (3 days ago): https://developer.apple.com/forums/thread/812380 Stack Overflow (1+ year): https://stackoverflow.com/questions/77866230/ ROOT CAUSE: iOS 18 changed this extension to use u/main pattern (no NSExtensionPrincipalClass needed). App Store validation hasn't been updated and still expects iOS 17 configuration. WHAT I'VE TRIED: ✅ All deployment targets set to iOS 18.3 ✅ Code follows Apple's WWDC 2022 guidance ✅ All entitlements correct ✅ Info.plist validated ✅ Clean builds ✅ Works perfectly on device No configuration satisfies both device runtime AND App Store validation. Has anyone successfully uploaded an app with DeviceActivityReportExtension to TestFlight on iOS 18? Any workarounds? This is blocking TestFlight deployment completely.

I've developed a Multiplatform app under Xcode 26 (currently using 26.2 17C52). The current destinations of the single target are Mac, iPad and Mac(designed for iPad). The minimum deployments are MacOS 15.6 and iOS 18.6. All destinations build and perform correctly on physical devices (running OS 26 versions). The MacOS version has been submitted successfully to the AppStore for TestFlight usage. However, the iPad version shows a submission validation failure: Missing Info.plist value. A value for the key “WKApplication”, or “WKWatchKitApp” if your project has a WatchKit App Extension target, is required in “xxxxx.app/xxxxx.app” bundle. For details, see: https://developer.apple.com/documentation/watchkit/creating_independent_watchos_apps/setting_up_a_watchos_project (ID: 4911506c-39c3-4b69-a8bb-5e5dcd3dc2fb) The app has no WatchKit version (although one's planned for a future release). The Target's Build Settings include a "watchOS Deployment Target" and Info.plist values related to WatchKit. The Build Settings also include similar settings for TVOS and VisionOS. I'm unable to delete the aforementioned Build Settings (Can't select & use the delete key). The link in the message provides no help. Is this a bug in Xcode, or am I missing something? Regards, Michaela

Mobile app marketing feels even more challenging in 2026, with once-reliable tactics like paid installs, influencer promotions, and push notifications losing impact while organic growth and user retention continue to slow. I am curious what is truly working for developers in 2026, whether stronger ASO, community-led engagement, web-to-app funnels, or long-term retention strategies are outperforming traditional paid acquisition.

I’m working on an iOS app and need help with ASO to find the best keywords for title, subtitle, description, and keyword field. Can anyone suggest free tools that show keyword volume, difficulty, and competitor keywords?

A 1.69% App Store conversion rate could be due to factors like unclear value proposition, unoptimized screenshots, or lack of strong reviews. Improving visuals, refining your app description, and gathering positive ratings can help boost installs.

User spending on mobile apps keeps rising, but competition is growing faster, making App Store Optimization a critical pillar of mobile growth by improving visibility, reducing cost per install, and driving stronger organic performance. This post highlights the most important ASO trends for 2026, including AI driven optimization, user intent focus, localization, creative testing, analytics, and privacy first strategies to help apps grow consistently on the App Store.

I am in the middle of trying to get an app approved for beta release and the back and forth with the App Store reviewers has been incredibly frustrating and concerning. On Tuesday, I created an app record for my app but quickly realized I made it under the wrong account- I'm working for a company that has a few brands under it's umbrella, and I was under the wrong account when I created the app record. Rather than wait several days to get Apple's approval to transfer app ownership, I decided to delete that app record and create a new one under the proper account. Worst mistake of my life. Now, Apple is insisting that the new app record is spam despite my clarification that I own the other app record and that it was deleted before the new one was created. I have no choice but to believe that somebody else is using our branding and asset somewhere in the App Store that I can't see. Does anybody know how I can resolve this? It should have never taken me the whole week to make an app available on test flight and my stakeholders are not pleased, and I have no clear path towards resolution that will allow me to use the proper branding with the proper company account. App review refuse to offer any solutions, I am stuck with a brand name that I can't use because it's associated with an app I already deleted.

Hello, I have a question regarding the lifecycle of user consent and tokens in "Sign in with Apple." Specifically, I would like to understand the behavior of the auth/revoke API in relation to App Store Connect status changes. Impact of App Status Changes If an app is "Removed from Sale" or "Deleted" from App Store Connect, does Apple automatically revoke all associated user tokens and consent? Or is it still the developer's responsibility to programmatically revoke each user's token via the REST API to ensure the app is removed from the user’s "Apps Using Apple ID" list? API Availability after Removal Once an app is no longer available on the App Store (or its record is deleted in App Store Connect), is the auth/revoke REST API still accessible? I want to ensure that a developer can still perform necessary privacy clean-up tasks (revoking consent) even if the app is not currently distributed. Specific User Impacts of Non-Revocation If we do not call the revocation API, besides the app remaining in the "Sign in with Apple" list, what are the specific consequences for the user? Thank you for your guidance.

I'm experiencing a contradictory validation issue with DeviceActivityReportExtension that creates an impossible situation: The Problem: Without NSExtensionPrincipalClass in Info.plist → App Store Connect rejects upload with: "Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found" With NSExtensionPrincipalClass → Local install fails with: "defines either an NSExtensionMainStoryboard or NSExtensionPrincipalClass key, which is not allowed for the extension point com.apple.deviceactivityui.report-extension" Setup: Extension point: com.apple.deviceactivityui.report-extension Using SwiftUI with @main attribute and DeviceActivityReportExtension protocol Xcode 16.2, iOS 17.6 deployment target Code structure: @main struct SpoolReport: DeviceActivityReportExtension { var body: some DeviceActivityReportScene { // Report scenes here } } The extension builds and runs perfectly without NSExtensionPrincipalClass, but cannot be uploaded to App Store Connect. Adding the key allows upload but breaks local installation. Is this a known issue? Is there a workaround or correct Info.plist configuration for DeviceActivityReportExtension? Thank you!

Hello, We are facing an App Store Connect issue that is blocking our release and cannot be resolved from the developer side. Here is the exact situation: iOS app version 1.0 was initially approved together with its associated in-app purchases (auto-renewable subscriptions). We decided not to release that version and manually set version 1.0 to “Developer Rejected”. After that, we made minor optimization fixes and uploaded a new build to App Store Connect. When attempting to submit this new build, the In-App Purchases section no longer appears in the App Store version UI, so we are unable to associate the already approved IAPs with the submission. Additionally, the “New Version” option is not available, so we cannot create a new app version either. As a result, any submission is rejected with the same message stating that the app references in-app purchases that were not submitted for review, even though the IAPs themselves are already approved. We have contacted App Store Connect Support and explained the situation in App Review notes, but we continue to receive the same rejection without any way to resolve the issue through App Store Connect. This appears to be an App Store Connect tooling or version state issue related to a Developer Rejected app version, rather than an in-app purchase configuration problem. Could an Apple staff member please assist by forwarding this to App Store Connect Support or engineering so the affected app version state can be reset or removed, allowing us to associate the approved IAPs and proceed with submission? Thank you for your help.

I am using XCode (Version 26.0.1 (17A400)) -> Archive -> Distribute App (or Validate App) to upload my iOS app into App Store Connect. However I am always getting this error: Uploading SPI errors: Validation failed (409) The app contains one or more corrupted binaries. Rebuild the app and resubmit. NSUnderlyingError : Validation failed (-19241) The app contains one or more corrupted binaries. Rebuild the app and resubmit. code : STATE_ERROR.VALIDATION_ERROR I tried exporting the app as an IPA and uploading with Transporter, but I see the same error. I couldn't find any other useful logs or error messages. More info: I have created the app in App Store Connect and this is my first time uploading. The app can build and run on my physical phone and emulator without any problem. Would be great to get some help! Thanks!

Hell Apple Developer Community, I need help with the Upload of my Project to AppStore Connect. I’ve got an Error Message, that tells me something is missing in the Info.plist file. Can somebody help me?