I am building a Vision OS app that includes a File Provider and File Provider UI extension. Both work great in simulator. When uploading to TestFlight, this message is shown: Unsupported Platform. The extension bundle [...]/PlugIns/File ProviderUI.appex is not supported for this platform. If I exclude the File Provider UI extension from the build, it is accepted. If I even include a hello-world File Provider UI extension, the error shown above is returned by ASC. There is contradicting documentation on this subject: https://developer.apple.com/documentation/technologyoverviews/app-extensions states that File Provider UI extension is not supported on Vision OS, so that explains ASC behavior https://developer.apple.com/documentation/FileProviderUI (and all other framework docs) states that File Provider UI extension is supported on Vision OS, so that explains why it works on simulator. Now, which of these two is correct? My best guess at this point is that ASC's logic follows the first document linked above, while the OS and framework actually follow the second. The same discrepancy seems to hold for macOS, but I'm currently focusing on Vision OS. Ideas? Anybody using a File Provider UI extension on Vision OS?

No payments received since December 2023 - Zero response from support I have not received ANY revenue payments from December 2023 through October 2024. App Store Connect shows no error messages or problem notifications. Despite submitting multiple support inquiries over several weeks, I have received ZERO responses. Not even an acknowledgment. Absolutely remarkable operations, Apple. RIP Apple.

Hello everyone, I’m currently working on an iOS app built with Capacitor(5.0.6) with Cordova and vanilla JS. At the moment, my app uses Stripe to handle payments — on iOS I open a Safari View Controller so users can pay with Apple Pay or their credit card. However, I need to migrate to Apple’s In-App Purchase system to comply with App Store policies. I would really appreciate some guidance or a step-by-step outline on the following: The exact process to enable and configure In-App Purchases in Xcode and App Store Connect for a Capacitor-based app. How to properly set up local testing with StoreKit (or any other recommended approach) before submitting to review. Best practices for integrating In-App Purchases when using RevenueCat, since I’m considering it to simplify the implementation. Any pitfalls or gotchas that I should be aware of during the first submission (for example, the requirement to include the first IAP with a new app version). My goal is to fully comply with Apple’s policies and provide a smooth user experience for iOS users. I’m open to suggestions on frameworks, workflows, or tools that could make this easier. Thank you in advance for any help or examples you can share!

Hi everyone, we are currently facing an issue with one of our apps regarding the new icon requirements in iOS 26. • We created the app icon using Apple’s Icon Composer. • On the device, everything works perfectly: the app icon is shown on the home screen, and it can also be customized with the new iOS 26 features (colors, transparency, etc.). • However, in TestFlight the app icon is not displayed at all (in the TestFlight app on the device). • In App Store Connect, the icon is also not shown in the overview for the app. Interestingly, within the list of TestFlight builds in App Store Connect the icon is visible. What we have tried so far: • Created an archive and manually uploaded it to App Store Connect → no icon in TestFlight. • Took the working Icon Composer asset from another app target where everything works correctly, deleted the old one in this project, and copied the working asset into the problematic target. → Same behavior: visible on the device, but still missing in TestFlight and App Store Connect overview. In contrast, in another app (using the same workflow and also Icon Composer), everything works perfectly: the icon shows up on the device, in TestFlight, and in App Store Connect. Has anyone experienced a similar situation? Is there something specific that needs to be set in App Store Connect (e.g. Marketing Icon / Branding section), or could this be related to the new iOS 26 icon handling? Any help or hints would be greatly appreciated. Thanks in advance!

My app has ITSAppUsesNonExemptEncryption set to NO, but I am still required to answer the export compliance questions. Are there any specific conditions, APIs, or frameworks (like WKWebView or third-party SDKs) that are known to override this Info.plist setting and force a compliance review? I'm trying to understand what triggers this requirement even when the key is set to NO. Is there any documentation on this?

Until recently, I was able to upload my app with iTMSTransporter version 4.1.0 with the following command: /usr/local/itms/bin/iTMSTransporter -m upload -jwt {x.y.z} -v eXtreme \ -assetFile /Users/abc/Downloads/build.ipa \ -assetDescription /Users/abc/Downloads/AppStoreInfo.plist Starting this week, with iTMSTransporter version 4.1.0, the command fails with the following error: [2025-09-03 11:38:02 GET] <main> ERROR: No value present Package Summary: 1 package(s) were not uploaded because they had problems: /Users/abc/Downloads/build.ipa - Error Messages: No value present The same command still works when using the iTMSTransporter bundled with the Transporter app (version 4.0), so the issue appears to be specific to 4.1. Any guidance or confirmation from others experiencing this would be much appreciated.

Hi all, I'm developing fitness app and I use healthkit to track user's "STEPS" count from their iphone devices. I have been receiving this rejection and can't seem to get past this: Guideline 2.5.1 - Performance - Software Requirements The app uses the HealthKit or CareKit APIs but does not clearly identify the HealthKit and CareKit functionality in the app's user interface. Apps using these APIs should be clearly indicated to provide transparency and valuable information to users. Next Steps To resolve this issue, it would appropriate to clearly identify the HealthKit and CareKit functionality in the app's user interface. Resources Learn more about software requirements in guideline 2.5.1. I have modified my app: adding user permission prompt, adding healthkit notification, adding healthkit indicator in the UI, adding healthkit information in the onboarding process. I keep getting the same message. When I asked the reviewer what else could be done to satisfy the requirement, I only get boiler plate message above. Anyone know what they really looking for? Any insights is appreciated. Thanks!

I have several subscription plans in the App Store that I no longer wish to offer to new users. In my app, these old subscriptions are hidden, but they remain active so existing subscribers can continue their plans and be charged as usual. However, some new users are still able to switch to these old subscription plans through the App Store. What is the best solution for this situation? I want to continue serving existing subscribers while preventing new users from subscribing to these legacy plans. Thank you.

My iOS app currently holds a 3.5★ rating with limited reviews, and I’d like to raise it by motivating happy users to share feedback. I’m looking for ethical ways to do this without being pushy. What are the best strategies and timing for review prompts to boost ratings while keeping users satisfied?

For ~8 weeks (10+ support replies) I’ve been unable to switch my app’s Primary Language from en-CA to en-US. App Store Connect shows: “Primary Locale couldn’t be saved because you must first provide all the required screenshots for each version in this language.” State: Default product page has complete iPhone + iPad screenshots for en-US and en-CA (live/approved). Issue began before any CPP existed; I have since removed all CPPs. Error persists, which suggests a stale/ghost CPP localization still being validated, or other issues. Questions: What does “for each version” precisely validate (live / in-prep / historical; default vs CPP)? Can deleted/never-approved CPPs still be validated, and how can they be purged? Anyone seen this after CPP removal—what fixed it? Happy to DM an Apple Staffer the case ID, a HAR of the failed save, and a short screen recording. Thanks! P.S. This has been open for ~8 weeks; I’m seeking an engineering-owned view to identify the specific unmet validator requirement or confirm a product issue. P.S.S. the App Catalog Report for my account is currently returning an empty file (Email) (requested via Apps → … → Reports). If others have seen this recently, is there a workaround - or should I file Feedback?

I’ve observed several areas in iOS where user experience could be enhanced, such as keyboard flexibility, animation speed, biometric options, cache management, background uploads, navigation reliability, and automation features. Addressing these aspects would not only improve usability but also align iOS more closely with diverse user needs across regions and use cases. What enhancements would you consider most valuable?

To make an iOS app available on Apple Silicon Macs, we need to enable the availability option under Pricing and Availability in App Store Connect. But unfortunately, macOS 26 is not still available as a choice there and I don't want to make the app available on earlier macOS versions. Does anyone have any solutions? Would adding the LSMinimumSystemVersion key to Info.plist work?

I have been trying to get an app I invented published and sent to Testflight / sandbox and then after feedback get it authenticated for the Mac OS distrubution store. I am stuck in a circular loop trying to get this to work. I have restarted 5 times now. ANY HELP or can I hire someone to walk me through it

The specific identifier (com.utel.prod) is not getting listed in app creation form in app store connect. I hereby attached my screenshot.

I've been waiting since I had Organizer sent my latest IPA to iTunes Connect servers 40 minutes ago. But the App Store Connect site doesn't show it. Is anyone having the same issue? I hate it when it happens because you don't know how long you have to wait.

I had everything working with Revenue Cat. Then my app got rejected for not loading subscriptions, which was odd because a previous built was rejected for wording on that same paywall. I checked, and realised I suddenly can't fetch products in testFlight either. I can only see products in Xcode using the store kit configuration file. I've found many issues like this online and everybody point to the same solutions (that seem to work for most), but here's what I tried so far: Checked that all my agreements in App Store Connect are active Checked that ids match between Xcode / revenue cat / App Store connect Store kit config file is syncing with App Store Connect correctly I removed revenue cat and used the store kit api directly to fetch products. The array of products is empty in all environments that don't have access to store kit config file. Checked status of all subscriptions (all waiting for review -- as they were when the paywall worked) Nothing seems to work... Any suggestions? Many thanks

Even the best apps struggle to get noticed—over 5 million apps compete in stores, and most never hit 1,000 downloads. Visibility, not quality, is the real challenge. App Store Optimization (ASO) is the key to breaking through. Optimizing your app’s title, keywords, visuals, and description, combined with ongoing testing and competitor analysis, can drastically improve discoverability and downloads in 2025.

Hello Support Team macOS : Sequpia 15.4.1 Xcode : 16.3 ・Certificates ・Profiles I recreated the above and registered them in the keychain. I can build in Xcode Product → Archive ・Validate App ・Distribute APp I have done the above but I am unable to update When I try to update the app, I get the following error Missing or invalid signature. The bundle 'Bundle ID' at bundle path 'Payload/App Name.app' is not signed using an Apple submission certificate. How can I do this?

When submitting our app to AppStore connect we received the following error: ITMS-90034: Missing or invalid signature - The bundle 'com.xxxxxxx' at bundle path 'Payload/XX.app' is not signed using an Apple submission certificate. Solved We just resubmitted the app.

Builds rejected with generic ContentDelivery 409 “corrupted binaries” (no email, no Activity entry) App ID: 6752832930 Bundle ID: com.taleway.tw Toolchain: Xcode 16.0 (build 24319) on macOS 15.6.1 (24G90) What happens Archiving (Release, manual signing) succeeds. Upload/validation via Xcode Organizer or xcrun altool immediately fails with: Validation failed (409) The app contains one or more corrupted binaries. Rebuild the app and resubmit. (ID: ef414ced-bf4e-40a6-8f5f-d4ba744c9433) altool also reports a preceding 500 “internal server error” (L4JS7YJVZYJMHBI4ISC4L3UQBM) before the 409. No system-generated email ever arrives (nothing under App Store Connect → Activity). We therefore have no specific error message or file name to fix. What we’ve checked Archive entitlements and embedded provisioning profiles match: App entitlements: CarPlay audio, App Group group.com.taleway.tw, get-task-allow=false. Intents extension entitlements: com.taleway.tw.TWIntents, get-task-allow=false. Profiles decoded via openssl smime—entitlements align exactly. No embedded frameworks at all; main binary is arm64 only (file TW). No bitcode sections (otool -l shows no __LLVM segments). No distribution Activity entries; case 102703979882 with Developer Support has bounced back twice with boilerplate “check your email”. The new validation ID (ef414ced-bf4e-40a6-8f5f-d4ba744c9433) and 500 code are all we have. Reproduction Archive TW scheme in Xcode (Release, manual signing). Upload via Organizer or: xcodebuild -exportArchive ... -exportPath /tmp/TWExport xcrun altool --validate-app -f /tmp/TWExport/TW.ipa -t ios -u -p altool output: ERROR: RETRIEVE UPLOAD OPERATIONS … internal server error (500) Validation failed (409) … (ID: ef414ced-bf4e-40a6-8f5f-d4ba744c9433) Log bundle: /private/var/folders/.../TW_2025-09-23_23-21-30.952.xcdistributionlogs (happy to share privately). Question Can someone from Apple reveal the actual validation rule that’s failing for ef414ced-bf4e-40a6-8f5f-d4ba744c9433? I’m not getting the auto email, and Activity shows nothing. Looking to know whether this is the known Xcode 16 validator bug (arm64e/BrowserKit, bitcode, etc.) or if our archive is missing something. Thanks! • App Apple ID 6752832930, bundle id com.taleway.tw • Xcode Version 26.0 (17A324), macOS 15.6.1 • Validation IDs: da15f377-df62-456e-b876-323401f3b2b2, bb6f914d-3488-48dd-9cde-4e4eef9897eb, ef414ced-bf4e-40a6-8f5f-d4ba744c9433 • altool output showing the 500 and 409 • We never receive the promised email, nothing appears under App Store Connect → Activity • Archive entitlements/provisioning profile match (list the keys) • No embedded frameworks, arm64-only, no bitcode • Log bundle path: /private/var/.../TW_2025-09-23_23-21-30.952.xcdistributionlogs