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

Hello, I have an app with a few essential asset packs currently totaling to ~8GB. I've noticed that when trying to install the app fresh from TestFlight, there is a significant delay between tapping install and the app appearing on the device in the loading state. The delay is long enough where it's hard to tell what's happening, or if the installation has failed. This also appears to be an issue in App Review, as I've had my app rejected twice due to the app not loading on the reviewers device. The reason they gave is UIRequiredDeviceCapabilities is blocking the installation, but UIRequiredDeviceCapabilities is empty. Note: I'm not looking for App Store review help, simply sharing the extent of the issue. Thank you

Hello, My app “DeepTone” has been fully approved and is marked as Ready for Distribution in App Store Connect. However, the app is not available in EU countries due to Digital Services Act (DSA) compliance still showing “In Review”. details: DSA verification was submitted and confirmed as completed by Apple Developer Support (case ID available). App Review has already approved the app. The app is currently live in non-EU regions but blocked in the EU. App Store Connect still shows: Digital Services Act (DSA) compliance – In Review Encryption Self-Declaration (France) – In Review This appears to be a backend compliance status issue rather than an app review issue. Has anyone experienced a similar situation where DSA compliance remained “In Review” after approval? Is there a known escalation path or expected resolution timeframe for this? Thank you for any guidance.

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.

ASO is by far one of the most frustrating parts of being an indie iOS dev. Despite trying keywords, descriptions, screenshots, and icons, results are unpredictable and competing with big-budget apps feels impossible. Has anyone found a way to make it work?

I'm looking to learn from others in the community. Please share any effective tips, hacks, or approaches you've used to boost app visibility and downloads through App Store SEO. Insights on keywords, descriptions, or metadata optimization are especially welcome.

Brand new to app development and marketing and preparing to launch my app on both the App Store and Google Play Store soon I understand ASO is a strong approach for organic growth and would appreciate any tools services or practical advice on how to do ASO efficiently and effectively

Hey everyone, I’ve been building iOS apps since 2011, released several, took a four-year break, and recently launched two new apps, but the ecosystem feels very different now. Earlier, new apps saw strong first-day downloads and fast Google indexing, while today my App Store pages took weeks to appear and show almost no organic traction without promotion, so I’m curious if others notice this and how developers now gain discovery.

Current issue (happening now) I get blocked immediately after entering my identity details and address. Apple Developer app (iPhone) I start the enrollment flow. After identity verification, I enter my address (Street Address, City/Town, State/Province, Postal/Zip, Phone). As soon as I tap Continue, I get: Contact Us to Continue There may be an issue with your account that needs to be resolved before you can continue. Please contact support. I cannot proceed past this point. Web enrollment (developer.apple.com) When I try on the web, I get: Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. This happens right after providing identity + address (before I can proceed further). Previous timeline (related background) ~3 months ago I incorporated my company in Türkiye (Ltd. Şti.) and tried to enroll as an organization. What happened First attempt on the web: enrollment was approved, but I couldn’t complete payment. Support told me to reset and try via the Developer app. Developer app enrollment then requested identity + “association with the enrolling entity” and company documents: Government-issued photo ID Employment/association verification Commercial registry extract (signed/stamped) Articles of association Tax office + tax number document Signatory circular I uploaded the requested documents. Apple replied that Turkish documents were unsupported and asked for “solicitor-certified English translations.” I uploaded English translations that were sworn-translator stamped. Why the translations were not notarized In Türkiye, due to the current economic situation, notarizing multiple translated corporate documents can cost hundreds of USD. Because of that, I initially provided sworn-translator certified (stamped) English translations rather than notarized translations. The translation office I worked with told me they regularly prepare company document translations for Apple Developer Program enrollments and that translator-certified translations are usually sufficient. My plan was to get everything notarized immediately if Apple explicitly requested notarization again or clarified that notarization was mandatory. About a week later, I received: Your enrollment request for your company has been declined. I followed up multiple times asking what exact requirement was not met (translation certification type, identity/association verification, etc.). Phone support said the decision was final and they could not disclose the reason. Additional detail discovered after the decline (document error fixed) After the decline, I reviewed all documents line-by-line and found a serious issue in my signatory circular: My company was incorporated on 27.08.2025. The signatory circular incorrectly stated that my authority started on 27.08.2023 (two years earlier). This was a notary/document preparation error. I immediately returned to the notary and had it corrected. They acknowledged the mistake, and I can obtain an official written statement confirming the correction if needed. However, Apple has not provided a channel to submit corrected documents, and support is not giving a path forward. What I’m asking the community Has anyone seen the “Contact Us to Continue” message triggered at the identity/address step and successfully fixed it? If yes, what specifically solved it? Is this typically an Apple Account eligibility/restriction flag, or can it be caused by address/region verification format issues? After an organization enrollment is declined, is there a known path to re-apply successfully (e.g., notarized translations vs translator-stamped, or having a different authorized representative apply as the Account Holder)? If documents were corrected after the decline (like the notary error above), is there any supported way to resubmit without starting from zero? Any concrete guidance would help. Thank you.

On January 1, 2026, we received a notice regarding the potential removal of our app with a 30-day resolution deadline. We treated this matter with immediate urgency and submitted an appeal on the same day. However, two weeks have passed without any feedback or clarification. As we have not yet received specific details regarding the violation, we are unable to identify the exact cause or take the necessary corrective actions. With only two weeks remaining in the compliance window, it is critical for us to understand the issue promptly to resolve it before the deadline. Could you please provide an update on the status of our appeal? We are fully committed to complying with App Store policies. If there are any additional materials required or proactive steps we should take while waiting, please let us know.

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)

This is my first iOS app release and I’m a bit confused. The initial version was reviewed in under 12 hours (rejected), and the corrected version was approved just as quickly. But my Product Page Optimization with only screenshots has been stuck in “Waiting for Review” for four days. Do these get reviewed only with new versions, or should I just wait it out?

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