App Store

RSS for tag

The App Store allows users around the world to discover and download your iOS and iPadOS apps.

Posts under App Store tag

200 Posts
Sort by:

Post

Replies

Boosts

Views

Activity

App Store updates are being throttled down
After posting a new version of our app, we used to have 80% of our userbase on the new version pretty quickly (usually 72 hours, sometimes less). Over the past few weeks, we've noticed that the App Store has throttled down app updates, and it now takes much longer for a new version of our app to reach 80% (approximately 15 days, so 5 times slower). He is an update graph before: And a similar update graph after: We've published several versions over the past couple of weeks, and we've seen the same slow update behavior for all of them. What could explain these differences ? At the time of this writing, the update graph has very slowly reached 80% and is now flat. In the past it would easily reach 90% (the last 10% were always slow to get).
0
0
43
13h
App using wrong Apple login service ID from another app — how to preserve existing users?
Our app (app1) was recently transferred from Team A to Team B. While reviewing the Apple login implementation, we discovered that "Sign in with Apple" had been incorrectly set up to use the Service ID and App ID of another app (app2) — specifically, it was using app2.service as the Service ID and app2 as the App ID. In other words, app1’s users were authenticated through app2’s credentials due to a misconfiguration on our part. Now that app1 has been transferred to Team B, we’re trying to preserve those users. However, app2 is still in Team A, and we cannot maintain Team A anymore — meaning app2 must also be transferred to Team B if we want to retain access to the user data. One idea we considered is submitting app2 for App Review (even though it's non-functional) just to fulfill the transfer requirements, and then transferring it to Team B solely to retain the Apple login setup. Is this approach acceptable? Are there any recommended ways to handle this kind of misconfiguration while preserving existing Sign in with Apple users?
0
0
49
18h
App Store blocker related to the use of a private iOS class, NSBlock
Hi, Our recent security scans, performed by Data Theorem, have flagged a potential App Store blocker related to the use of a private iOS class, NSBlock. We are concerned that this identified warning may lead to our apps being rejected during the next App Store submission. Issue Summary: We integrate a library, this SDK is developed using Kotlin Multiplatform, and during compilation, Kotlin automatically generates Objective-C/Swift interoperability code. As a result of this code generation, the compiled framework includes a reference to a private Apple class, NSBlock. It’s important to note that: No methods or functionality from NSBlock are being invoked or used. This reference is auto-generated by Kotlin’s ObjCExport.mm module. For additional context, you may refer to a related discussion on this issue: https://github.com/ricohapi/theta-client/issues/98 https://github.com/JetBrains/kotlin-native/issues/1642 https://github.com/JetBrains/kotlin-native/pull/1652/files We would like to confirm whether the presence of this unused reference to NSBlock will result in the rejection of our application during App Store review. Thankyou
0
0
65
1d
Unable to Complete Developer Program Purchase – "Card Could Not Be Approved" Error
Hello, I recently created a new Apple Developer account and I'm trying to purchase the Developer Program, but I'm running into a payment issue. Every time I attempt to make the payment, I receive the following error: "The payment you want to make with your card could not be approved." Here is what I have tried: I used multiple cards (Visa and MasterCard) from different Turkish banks. All cards are active, have sufficient balance, and are open to international payments. I confirmed with my banks that there are no issues on their side. Despite all of this, the payment still fails. Additionally, I noticed that my Developer account shows a "Pending" status in the dashboard. There is no further explanation about this status, and I am unsure whether any additional verification is required. I also contacted Apple Support via email, but I haven’t received a response yet. I would like to ask a few additional questions for clarification: After successfully purchasing the Developer Program, how long does it take for the account to become fully active? Once the account is activated, how long does app review and publishing usually take? Is this kind of delay and unclear messaging common with Apple? Or am I experiencing an exceptional case? Any insight or similar experience would be greatly appreciated. Thanks in advance for your support! Best regards, Harun Altaş Turkey
1
0
155
5d
Rejected for Spam 4.3 (A) Without Clear Reason – Previously Approved App Now Stuck in Review for Weeks! [App ID: 6744330283]
Hello Apple Developer Team and Community, I’m writing to raise a serious concern regarding my app (App ID: 6744330283) which is now being repeatedly rejected under Guideline 4.3 (A) – Spam, despite being previously approved and published for at least two earlier versions. We have had multiple rounds of communication with the App Review team in the past, carefully addressing every request and making adjustments accordingly. These previous versions were reviewed and approved without any reference to 4.3 issues. However, since a recent update, we’ve been receiving rejections citing Spam 4.3 (A) — without any specific explanation or detailed reasoning. Even more frustrating: Each review now takes over a week to process, making our release cycle extremely difficult to manage. It required dozens of phone calls and emails just to get the app reviewed at all. I even had a meeting with an App Review team member, where I was told: “The recent updates are considered Spam 4.3, while the earlier versions that were approved are not.” But I am truly confused by this, because all the updates share the exact same codebase — there are no material differences between the approved versions and the ones now being rejected. This inconsistency and lack of clarity is making it impossible for us to move forward. We respectfully request: A clear and actionable explanation for why the recent versions are now considered Spam 4.3 (A), while earlier versions were not. Specific guidance or examples to help us understand what triggered this new interpretation. Transparency about what exactly changed — either in review criteria or policy enforcement — so that we can comply properly. We are committed to fully adhering to the App Store Review Guidelines and improving the app accordingly, but we can’t do that without transparency and fair communication. Any insights from the Apple team or other developers who’ve faced similar issues would be greatly appreciated. Thank you.
1
0
86
5d
Custom Events in the Apple Ads Campaign UI
Hi! Looking at some documentation for reporting metrics available for apple search ads, it says: "Reports don’t include view-through or total metrics. Also, Apple Ads doesn’t support the use of third-party tracking URL variables or include data for in-app purchases. The Apple Ads Attribution API is also available to help you measure and attribute app downloads." Can someone verify and clarify these things: Does this mean I'll never be able to view custom conversion metrics in the apple ads campaign dashboard (https://app-ads.apple.com/cm/app), or will I be able to if I use the Ads Attribution API and set up custom events? Do I need to use an MMP (like Branch?) to be able to view reports on these kinds of metrics What is the point of sending events via the Ad Attribution API if we can't view reports on them (given that you can't view reports)? Do campaigns still learn on custom events? Thank you SO MUCH for help, I can't find any information online.
0
0
111
6d
Mismatch between App Store Server API `expiresDate` (July 23) and iOS UI “Expires on” date (July 22) for 1-month subscription
Hi everyone, I’m seeing a consistent one-day discrepancy between the expiresDate returned by the App Store Server API and the “Expires on” date shown in the iOS Settings / App Store subscription list. I’d like to confirm whether this behavior is expected or if I’m misunderstanding the way Apple rounds dates. Reproduction steps Step Action Result 1 Purchase a 1-month auto-renewable subscription on 23 June 2025 14:00 JST (UTC+9) Transaction succeeds 2 Immediately fetch the transaction with GET /inApps/v1/subscriptions/{transactionId} Response contains "expiresDate": "2025-07-23T05:00:00Z" (= 23 July 2025 14:00 JST) 3 On the same device open Settings › Apple ID › Subscriptions (or App Store › Account › Subscriptions) UI shows Expires on: 22 July 2025 The same happens for every monthly renewal and on multiple devices. Region is Japan, device time zone Asia/Tokyo. What I understand so far (and my hypothesis) Apple’s docs say a monthly subscription renews “on the same calendar date” of the next month, so renewal in this example is 23 July. If the renewal is scheduled for 23 July at 14:00 JST, the subscription is fully usable until the end of 22 July in calendar terms, because the new billing period starts the moment the 23rd begins in Apple’s canonical time zone. Therefore, it might be intentional for the UI to display 22 July—i.e., “you can keep using it through the 22nd; on the 23rd it renews.” This hypothesis makes sense internally, yet it still looks confusing to end users who read “Expires on 22 July” and assume access ends at 00:00 on the 22nd, a whole day earlier than in reality. Questions Is showing the day before the renewal date the official/expected behavior? If so, could Apple clarify that the “Expires on” label represents the last full calendar day rather than the exact expiry timestamp? Which value should we surface in-app when telling users “Your subscription is valid until …”? The server’s expiresDate (precise to the second, converted to user time zone), or A UI-style date that’s one day earlier, matching Settings / App Store? Does Apple have a public document describing this rounding/visual convention? Have other developers encountered user confusion about the apparent 1-day “shortening” and, if so, how did you word your in-app messaging? Any insight from Apple engineers or fellow developers would be greatly appreciated. Thank you!
0
0
158
1w
Xcode can't upload visionOS app CFBundleIcons.CFBundlePrimaryIcon Validation Failed
I'm developing a visionOS app and was able to upload new builds without any problems to the App Store. A couple pf days ago I wanted to ship another update, but now I can't submit it to the App Store anymore, because the validation failed, something related to the App Icon seems to be the issue, the logs mention CFBundleIcons.CFBundlePrimaryIcon. I have setup the App Icons here: The validation error I first got was this, mentioning a plist entry (that has not been necessary in the past) is missing. I've then added that plist entry, as described in the reference doc for CFBundleIcons.CFBundlePrimaryIcon. My info.plist now includes this, following the mentioned docs: However, now I get a type missmatch error when validating — however the types are as described in the docs: What am I missing? Why even is this plist entry required now? Or is this a Bug? Help please
1
0
51
1w
My app rating stucked
Hi, One of my application doesn't get rating updates on AppStore. On https://appstoreconnect.apple.com/ Ratings and Reviews page I see that app got 19 Ratings with average 3.8 out of 5. But on AppStore it just have 5 ratings with average 3.4 out of 5. See attached screenshots: AppStore: AppStore Connect: . Please help me to figure out with this issue and hope we can fix rating on AppStore page accordingly to AppStore Connect. Thanks, Alex
2
0
96
1w
InApp Review Implementation
So from the documentation of apple for implementing the in app review feature we can't test it without releasing our app to App Store since in test flight it doesn't approve the api call is there a way to test it where we can check if the rating or review entered is visible on a console so that we can test the end to end work flow? this happens in android in internal test track? is there any provision for this in iOS?
0
0
36
1w
Enrollment Button not working on Apple Developer App
Hello Apple Support team, I hope You are doing well this is Muhammad Musaab and i am currently applying for the apple developer program i have successfully completed my apple profile and when i logged in to my developer app on macbook and also on my iphone the enrollment button gets grayed out and unclickable, please i do not want to sign up on web page i am asking help regarding the grayed out button i am getting on apple developer app. Kindly resolve this issue as soon so that i could provide my unique games and apps to apple users. Thanks!
0
0
33
2w
App Updates Consistently Delayed and Auto-Rejected Despite Account in "Good Standing" (App ID: 6744330283)
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.
2
0
61
2w
Uploaded Build Missing NSLocationAlwaysAndWhenInUseUsageDescription Key Despite this Key Being in the Info.plist File
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!
1
0
39
2w
how accessible is enough for Accessibility Nutrition Labels?
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).
1
0
45
2w
Guidance on Java JRE Usage for PST Parsing in Mac OS Application– Code Signing & App Store Compliance
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
6
0
92
1w
How to update the last compatible version on AppStore
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?
1
0
70
3w
Selling your first app
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?
0
0
32
3w
Updating developer name on the App Store
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
0
0
40
4w
Where can I find the minimum iOS version requirement for App Store submissions?
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?
1
0
56
4w