I’m experiencing a critical issue with my app’s review process under my developer account (App ID: 6744330283). The app was initially approved and published, but starting with version 1.2 and later updates, every submission faces prolonged review times (over 1 week) only to be automatically rejected without clear justification. I’ve resubmitted multiple times, confirmed compliance with guidelines, and even tested with minor changes—same result. Meanwhile, a separate developer account of mine gets approvals within 24 hours for the same type of apps, suggesting an account-specific issue. Actions Taken: Appealed via the Resolution Center and App Review Board. Communicated via email and even a Meet call with Apple Support, but was told my account has "no issues." The app has real users and active IAPs, making this disruption unacceptable. Next Steps: I’m pursuing legal counsel in LA to escalate this, as the lack of transparency is harming my business. Questions for the community: Has anyone resolved a similar issue? Are there hidden account flags or escalation paths beyond standard channels? Any advice or shared experiences would be greatly appreciated.

Hey All! I keep receiving an email from Apple stating "You have a missing purpose string in your Info.plist" for the key "NSLocationAlwaysAndWhenInUseUsageDescription". The thing is, though, that we are setting that value within our build Info.plist. The data in that value is even reflected into the application after build, with the correct purpose string showing up when requesting location services. We currently do our builds via Azure Devops CI/CD, where we use xcodebuild for this process. The archive also generates an Info.plist without the location key, so I tried manually inserting it before deployment. Also no luck. Anyone else had this issue or know how to resolve it? Snippet to show how the location key is currently set during build: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>NSLocationWhenInUseUsageDescription</key> <string>Application uses location data for accurate maps display</string> </dict> </plist> Thanks!

My team has a robust digital accessibility program and processes for WCAG conformance in our apps. Because of this, there are definitely accessibility defects that get caught and addressed in order of impact and business priority like any other bug. Obviously we want to aim for 100% accessibility for our users, but it's a continual work in progress as new enhancements or changes are released. I'm stuck on the appropriate measurement to indicate support. If we have 50 common tasks and the most central 10 tasks are solid but some supporting (but also common) tasks have a contrast fail or accessibleLabel missing, does that make the whole app not supporting the feature? If "completing the task" is the rubric there are a whole range of interpretations for that. In a complex app, I anticipate that a group like ours will have strong support for many of the Accessibility Nutrition Labels accessibility features across tasks and devices, but realistically never be 100% free of defects for a given Apple Accessibility feature, even among core tasks. As I consider the next steps for Nutrition Labels, I do not see anything in the documentation that gives a sort of baseline or measurement for inclusion. We plan to test all steps to complete a task, and log defects accordingly with an assigned timeline for fixing them (as would be true for functional defects).

Hello Apple Support Team, We are developing a macOS application that allows users to import and view PST files (Microsoft Outlook archives). These files contain a complex, proprietary format that requires specialized parsing libraries. To achieve this, we are using Aspose Email for Java, which is currently one of the few reliable libraries that support complete PST parsing across platforms. Why we are using Java & Aspose The Aspose Email Java library provides a comprehensive API to extract mail data (including metadata, attachments, and folder structure) from .pst files. A native Swift or Objective-C alternative with full .pst parsing capability does not exist, which is why we opted for a Java-based helper module that runs in the background and communicates with the macOS app over a Unix domain socket. How we bundle it We package the AsposeEmail.jar and a custom JRE (Java Runtime Environment) created using jlink, tailored to run only our jar. This entire setup (JAR + JRE) is bundled within the Contents/Resources directory of the macOS app, and we invoke the Java runtime using standard process launch APIs from Swift. Problem during App Store Submission When we archive the app and submit it to the App Store, the validation step raises an error: ITMS-90284: Invalid Code Signing - The executable 'com.app.sample.appstore.pkg/Payload/Sample.app/Contents/Resources/custom-jre-universal/lib/cli ent/libjsig.dylib' must be signed with the certificate that is contained in the provisioning profile. ITMS-90284: Invalid Code Signing - The executable 'com.app.aample.appstore.pkg/Payload/Sample.app/Contents/Resources/custom-jre-universal/lib/cli ent/libjvm.dylib' must be signed with the certificate that is contained in the provisioning profile. When we attempt to code sign the custom JRE, especially the .dylib files inside, the runtime breaks. Java is unable to launch correctly and throws permission errors and execution failures. Alternative we thought of (On-Demand Download) To avoid the code signing issue, we decided to remove the JRE from the bundle and instead download it on demand when the user performs an action like "Import PST". However, we realized this may violate the App Store Review Guideline 2.5.2: Our use case, while not dynamically modifying features, does download and execute a Java runtime, which could be interpreted as executing new code post-installation. How can we proceed? We are looking for Apple’s guidance on the correct and compliant path forward: Is there a recommended way to bundle and codesign a custom JRE so it is accepted by the App Store? Is on-demand download of a custom runtime for a very specific parsing task permitted, assuming it doesn't modify app features but simply supports user-initiated operations? We would greatly appreciate any guidance or best practices on how to handle this situation, particularly with respect to App Store compliance. Regards, Maaz Hussain

Hi, I'm working on an app that currently support iOS 16+ I'm considering to raise the deployment target to iOS 26 For users on devices with version lower than iOS 26, I know they can continue to use the app they have already installed and can even redownload it via the last-compatible versions support. The question is simple - once the version with deployment target iOS 26 is released, is there any way to update the last compatible version of iOS 16+ in case a critical bug or security vulnerability has to be fixed? For example lets say that the current version is 1.2.2 (iOS 16+) new version 2.0.0 (iOS 26+) is released users with iOS 26 can install 2.0.0 existing users with iOS 16-18 can continue to use and reinstall 1.2.2 in the meanwhile, the app evolves and reaches 2.1.5 6 moths later, a critical bug or security vulnerability on 1.2.2 has to be fixed, so 1.2.3 version, based on 1.2.2 codebase with the necessary fixes has to be deployed to old users. How to update existing users with iOS 16-18 from 1.2.2 to 1.2.3? Is there any mechanism to achieve this? Does AppStoreConnect or AppStoreConnectAPI allow such thing?

How long was it between putting your first app on the App Store (that had a paid component to it like IAPs) and getting your first sale? I'm working on an app at the moment that I plan on putting up for a small one time fee. I'm curious to know what people's different experiences were with this. What was your app and how did it go?

Hi everyone, I made a mistake when submitting my first app and accidentally set my developer name as the app name instead of my business name. Now all my apps show the wrong developer name on the App Store. Apple support said it can't be changed after the first app, but I've seen some posts mentioning people got it changed through support. Has anyone successfully changed their developer name after initial setup? Is closing the account and starting fresh the only real option? Really don't want to lose my app's reviews and ratings. Any experiences or advice would be appreciated! Thanks

Looking at some of the latest release notes, it appears that lowest supported version is iOS 15.0 for all versions of Xcode 16. Considering that Xcode 16 is the minimum version for submitting apps to the App Store, I would assume that means that Apple expects apps to be on 15.0+. However, knowing that you can manually override this setting in Xcode, there seems to be a lack of clarity on what the true minimum is. Looking at the App Store, it appears there are some apps that can go back as far as iOS 12.0. Is there a definitive way to know what is the true minimum that the App Store accepts?

Dear Developers, I would like to suggest an optimization for the logic governing the download and installation queue for app updates. Currently, when multiple applications are awaiting updates, the prioritization does not appear to consider the update payload size. My proposal is to implement a logic that prioritizes the download and installation of updates with a smaller delta size (fewer MB) before those with a larger delta. Practical Example: A 1MB update would be processed before a 500MB update, even if their arrival order in the queue was inverted. Potential Benefits: Perceived Speed Optimization (UX): Users would gain access to functional applications more quickly, especially in scenarios with multiple pending updates. Network Efficiency: In limited or intermittent bandwidth scenarios, completing smaller downloads first can reduce the chance of download failures and optimize network resource utilization. Device Resource Management: Frees up temporary storage and processing resources more rapidly for smaller updates. I believe this optimization would bring significant gains in terms of User Experience (UX) and the operational efficiency of the platform. Thank you for your attention and consideration. Sincerely,

We are implementing an Advanced App Clip Experience for our App Clip, but encountered a blocking issue where the configuration is shown as valid in App Store Connect, but is not recognized on device. We have run out of ways to debug and would appreciate help. Setup Summary Our main app is live on the App Store and includes an App Clip target. The Advanced App Clip Experience is configured in App Store Connect Status: Received Domain validation: All checks are marked as passed ✅ The domain's AASA (apple-app-site-association) includes the correct App Clip bundleID. ❌ The Issue When scanning a QR code pointing to outs domain on an iPhone The App Clip card does not appear. 2.Using the Developer > App Clip Experiences > Diagnostics tool on iPhone, entering the domain returns: "No Advanced Experience is registered for this URL." I’m very confused about why the device behavior doesn’t match the configuration status in App Store Connect. Any insight or suggestions would be greatly appreciated!

Hello, for applications using Signin with Apple feature, it seems a particular process needs to be followed when you want to transfer the app to a new owner. Generating transfer identifier before the transfer of ownership to identify a particular user. There is already "email" registered for the user, personal email or relay email (doesn't matter). Why would we need to trouble ourselves with the transfer identifier? The documentation doesn't explain anything about the background of this. It is very weak. It doesn't explain the impacts/changes when app is transferred so that one can fully understand its impact. Thank you.

Hello, why Apple use a generic billing descriptor for charges (e.g., "APPLE.COM/BILL", "APL*APPLE"), which does not include the app name? As a result, unexperienced users associate any Apple charge on their bank statement with our app, even if it's a charge from another app or service they’ve used. This is leading to: Confusion and mistrust from our users An increase in wrongful refund requests Support burden for an issue outside of our control We kindly request Apple to consider including the app name in the billing descriptor (like Google Play does). We understand Apple manages all billing, but the current setup causes confusion that unfairly impacts our app’s reputation and support load. Thank you

My app was accepted onto the app store yesterday, but i just found out that my subscriptions were rejected for some reason. The localization of each subscription said there was something wrong with it so i changed them and resubmitted them. The issue/question that i have is that now that my app has been accepted with my 1.0.0 version, do i have to submit an update for them to review my subscriptions? or do they review the subscriptions separately because you have to submit the subscriptions for review, the same way you have to submit builds. I just don't want to be waiting around because i can't market my app without those subscriptions accepted

I am planning to gradually phase out the app and make it unavailable for new users. However, we would like to ensure that users who have already installed the app can continue to receive updates and support during this transition period. Please advise if this is possible? If so, what are the necessary steps or settings we need to configure in the App Store Console to achieve this? In addition, I would appreciate your guidance on the following questions: What is the process for uploading or releasing an update for an app that is currently "Removed from Sale"? If an app is "Removed from Sale", can it be republished later? What are the steps to do that? Are there any limitations when changing the app’s distribution region (e.g., is there a maximum number of times the region can be changed)? Thank you.

My application has been in "In Review" status since May 30, 2025, and it is still in that status today. Please check the status of my app, LS Tools. Our customers are waiting for the latest version

My app uses Apple IAP. With the recent US external payment changes (May 2025), I plan to use Stripe via Superwall. Superwall allows me to remotely toggle my paywall for US users between Apple IAP and Stripe checkout without a new app build. Is it permissible to activate Stripe for new US users on an already live app version (approved with only Apple IAP) without first submitting a new build for Apple to review the Stripe integration? Or does this dynamic switch create a risk of takedown/compliance problems? Concerned about new users hitting an unreviewed Stripe flow during any potential review period for a new build. Seeking clarity on Apple's stance or community experiences. Thanks!

I initially released my app in English only and after about a year I added support for 4 more languages, now English is not being shown in the list of languages on the App Store. The primary language in App Store Connect is English (U.K.). The app seems to work fine, the content is being shown in English for me. Anyone know how I could fix this?

Hello everyone, I’d like to propose Sense & Store — a seamless integration between Safari and the App Store, powered by on-device AI, designed to understand what users are reading, searching, or selecting in Safari, and suggest relevant apps that match their current context or intention. 🔍 Key Idea: “Sense” the user’s need through intelligent analysis of web content, then “Store” — offer the most relevant app, either already installed or available in the App Store. 🌟 Core Features: • AI-powered context detection directly inside Safari • Real-time app suggestions based on user intent • Smart overlays when selecting text or data (e.g., phone numbers, emails, tools) • Privacy-first: All AI runs on-device (Apple Neural Engine) • Instant App Launch or Installation via StoreKit ✅ Examples: • Reading an article on productivity? → Suggests Notion or Things. • Looking up meditation tips? → Recommends Calm or Headspace. • Selecting a phone number? → Offers CRM or spam blocker apps. • Exploring code samples? → Suggests Pythonista or developer tools. 🔒 Privacy & Performance: • 100% on-device intelligence (no data sent to servers) • Follows Apple’s privacy framework • Works with SafariKit + StoreKit + CoreML ⸻ I’m happy to provide a full prototype roadmap and technical architecture. Feedback and collaboration are welcome! Would love to hear your thoughts — especially from developers who build for Safari, App Clips, or work with CoreML. Thanks! by: Apple lover....

Hello everyone, I’d like to propose Sense & Store — a seamless integration between Safari and the App Store, powered by on-device AI, designed to understand what users are reading, searching, or selecting in Safari, and suggest relevant apps that match their current context or intention. 🔍 Key Idea: “Sense” the user’s need through intelligent analysis of web content, then “Store” — offer the most relevant app, either already installed or available in the App Store. 🌟 Core Features: • AI-powered context detection directly inside Safari • Real-time app suggestions based on user intent • Smart overlays when selecting text or data (e.g., phone numbers, emails, tools) • Privacy-first: All AI runs on-device (Apple Neural Engine) • Instant App Launch or Installation via StoreKit ✅ Examples: • Reading an article on productivity? → Suggests Notion or Things. • Looking up meditation tips? → Recommends Calm or Headspace. • Selecting a phone number? → Offers CRM or spam blocker apps. • Exploring code samples? → Suggests Pythonista or developer tools. 🔒 Privacy & Performance: • 100% on-device intelligence (no data sent to servers) • Follows Apple’s privacy framework • Works with SafariKit + StoreKit + CoreML ⸻ I’m happy to provide a full prototype roadmap and technical architecture. Feedback and collaboration are welcome! Would love to hear your thoughts — especially from developers who build for Safari, App Clips, or work with CoreML. Thanks! Jose Luiz Horta Barbosa Maurity Cruz - Apple lover...

I have been appealing to Apple to delete this rejected build since we have a new API and an upgraded new build with new IOS version to submit but we must up a version from 2 to 3. But the review BOT, I believe, doesn't read my appeal. It keeps responding with exactly the same rejection notes as before. I don't see the [+] button top left so I can't add a new version. I sent emails and made appeals to the "Review Board" link and submitted a case. There has been no response. It's been over a month. Can anyone recommend a solution, please?