Hello everyone, where can I change the email address that is in the information section of the App Store? https://apps.apple.com/de/app/start7-der-handball-manager/id6443919324?l=en-GB Thanks! Simon

My app currently doesn't specify multiple different appearances (Any, Dark, Tinted) for the App Icon. I want to release an update in which I plan to create a new AppIcon resouce which is going to contain these 3 appearances so that users on iOS 18 can have better experience. Once I will provide the new App Icon with the Any, Dark and Tinted variants, which of these variants will the App Store use for my app on the App Store? Does it depend on the user's system-wide choice of appearance? That is, would the App Store show a different icon appearance for my app for a person using the "Dark" option and a different app icon for the person using the "Light" option? Can I force the App Store to always display the "Any" variant of my icon on the App Store, regardless of the user's dark mode setting? My app targets iOS 13. What would happen if a person running iOS 13 would install the new update of my app, which newly contains all 3 App Icon color appearances? Would the "Any" variant be displayed and would iOS 13 ignore the "Dark" and "Tinted" variants? Or is there no backwards compatibility and older iOS version would display a blank app icon (the icon used by iOS for apps, which do not specify an App Icon)? P.S. Is this documented somewhere? Perhaps in a WWDC video or in documentation? I could not find enough in-depth information on this topic (especially on app icon appearance behavior on iOS 17 and older).

Do either of these count as "third-party content" in the context of the Contents Rights declaration for an app? Fonts by other authors that I am permitted to use commercially. A relatively simple third-party script for an online high-score system that I am also allowed to use commercially. I have listed both in the copyright/credits in my app (a game). Although I say commercially, this app will be free with no in-app purchases.

Hi everyone, We are facing a persistent issue with our iOS app related to memory limits and would greatly appreciate any insights or guidance from the community. Context: Platform & Version: iOS Development Environment: Xcode 15.4, macOS 14.6.1 Runtime Configuration: iOS 17.6.1, iPad Air 1TB (16GB RAM) Issue Summary: Our app crashes when it hits memory usage around 5–6GB after being distributed through the App Store. To address this, we enabled the com.apple.developer.kernel.increased-memory-limit entitlement, which allowed much higher memory usage (up to ~15GB) during local testing with a development build. What We Tested: Local Build (Development Profile): Added the com.apple.developer.kernel.increased-memory-limit entitlement to the app. Tested on a physical iPad and found that the app could use nearly 15GB of RAM before crashing. This confirmed that the entitlement was having a positive effect in this non-App Store scenario. App Store Build (Distribution Profile): Used the same entitlement-enabled code and configuration for distribution. After installing the App Store version on the same device, we found the app now crashes around the 6GB RAM usage mark—essentially the standard limit. It appears that the entitlement is not taking effect in the App Store environment. Key Concern: Why is the com.apple.developer.kernel.increased-memory-limit entitlement not having any effect on the App Store version of the app, even though it works perfectly when testing with a locally signed development build? What We’ve Considered So Far: Entitlement Restrictions: Is com.apple.developer.kernel.increased-memory-limit restricted or only allowed for certain first-party or special partner apps? Profile Differences: Could differences between development and distribution provisioning profiles cause the entitlement to be ignored? App Store Validation: Does the App Store review or signing process remove or nullify certain restricted entitlements? Request for Assistance: If anyone has experience with this entitlement or similar restricted entitlements, we would greatly appreciate your advice. Specifically, we are looking to understand: Has anyone successfully enabled increased memory limits in an App Store build using this or a similar entitlement? Is there an official Apple process or documentation for requesting or enabling such entitlements for third-party apps? Are there any known workarounds or best practices for handling large memory usage within the standard limits? We’ve contacted Apple Developer Support, and they recommended posting this on the forum for community feedback before they proceed further. Any guidance or shared experiences would be extremely helpful. Thank you!

HI, I am an iOS developer working in finance sector. I just wanted to clarify the following thing once the user deleted the App Store app in the EU region. Impact on Already Installed Apps After Deleting the App Store App If a user deletes the App Store app in iOS 18.2, will already installed apps remain functional? How does the OS manage app updates for these installed apps? Are updates delivered automatically via the system's update mechanism, even when the App Store app is uninstalled? Accessing the App Store Through Safari Can users still browse the App Store via Safari in iOS 18.2? Will this access allow users to manually download updates for their installed apps if the App Store app is not installed? Please help to understand how this is handled.

Hello! Everybody. We receive messages from our partners and customers about Enterprise Program Cancellation at 12 of February 2025. Is it a worldwide phenomenon and the Enterprise program will no longer be available for everyone or it is an issue with our customers and partners? Thank you very much for your replies!

I am facing a serious and urgent issue. I am trying to build my app for an update on the Store, but in Xcode, instead of archiving the expected Runner application, the archive is successfully created, yet it is not associated with the correct Runner. As a result, I am unable to upload and distribute the app to the Store after the build. I have been stuck on this issue for two days, trying every possible solution, but I cannot identify what is wrong or causing the problem. Could someone please assist or guide me on how to resolve this? I would greatly appreciate any help. Thank you in advance. Please check the screenshots:

For over a week now my ads have been live and the status is running but I have $0 spend, impressions, etc... Any ideas about what I'm missing would be greatly appreciated!

Hi all! Our app is published on the app store and from an iPhone we can grab the store URL (if eg name is 'test' and id is '123') https://apps.apple.com/us/app/test/id123 This works perfectly if you open the link from an iPhone, but when you open it from any desktop (multiple devices, multiple browsers tested) it does a 301 redirect back to itself and the browser eg Chrome says 'This page isn’t working. apps.apple.com redirected you too many times.' This seems to only be happening to our app and we can't figure out what's going on. Our app isn't viewable by Google Searching either. New builds hasn't fixed it (we thought maybe some Apple caching issue) and it doesn't seem like we could change the app / SKU URL either to try to force a rest. Thank you so much to anyone with insight!

Hello, I am getting the error : "This app cannot be installed because its integrity couldn't be verified" when the app is installed using Apple configurator. The same .ipa works when deployed to app store. I am using App Store Connect distribution provisioning profile type. I want this .ipa to be deployed to multiple devices without having to add these devices to the provisioning profile list. Any insights? Thank you, Prateek

We are working on one product, with three independent code bases, one each for iOS, iPadOS, and MacOS. Functionality is basically the same for each device version and they sync between each other. Can we use one name for these three versions - as, for example apps from Adobe, Microsoft and Apple do?

I have been receiving this error on gummy drop but only on one purchase. I have asked all involved parties for a resolution but each one blames the other.

Hi everyone, We’re encountering an issue with a Custom Product Page (CPP) deep link configured in App Store Connect, and its execution seems inconsistent. Here are the scenarios we’ve observed: 1. If the app is already installed and I open it via the custom product page, the deep link executes as expected. ** If I install the app from the custom product page** and immediately open it, the deep link does not execute. If I install the app from the custom product page but wait 3+ seconds before tapping "Open," the deep link works as expected. Additional context: The deep link is processed in the SceneDelegate and points to an associated domain that redirects to a purchase funnel. The behavior in (3) makes me suspect a timing issue. The main challenge is debugging this, as testing the deep link’s execution requires installation from the App Store. Does anyone have suggestions for improving the reliability of deep link execution in this scenario? Any insights into what might cause this timing-related behavior would also be greatly appreciated. Thank you! Thomas

The Search Ads website made a big announcement about new supported countries, featuring a prominent banner on their homepage. One of the newly supported countries is Bulgaria. I have apps localized in Bulgarian. However, the official App Store language for Bulgaria is English (UK), so my Bulgarian localization is placed under the English (UK) tab in the App Store. Promoting such an app in Search Ads is impossible. I was told the language of the app must be English. So, while Bulgaria is now listed as an option for ads, I cannot run ads for my Bulgarian apps. How is this possible? I would appreciate your advice!

I'm developing a B2B team collaboration app. My customers are businesses, and I plan to charge them on a per-user per-month basis. Payers are companies, not individual users, and the company pays for all its employees simultaneously. Implementing the logic mentioned above using in-app purchases looks quite challenging; I will need someone from the company to pay for the whole company and constantly upgrade/downgrade the subscription level as the team size changes. So, is my app required to have in-app purchases in this case? According to guidelines, I may allow users to access externally purchased subscriptions. Does it mean I don't have to implement in-app purchase logic in my app? 3.1.3(c) Enterprise Services: If your app is only sold directly by you to organizations or groups for their employees or students (for example professional databases and classroom management tools), you may allow enterprise users to access previously-purchased content or subscriptions. Consumer, single user, or family sales must use in-app purchase. I would be grateful for any help and advice.

Hey folks, I'd like to know if anyone faced the same problem and how did you overcome it. We're considering depreciating one of our app's platform but will continue developing and introducing new features to the rest of athe pp platforms. Imagine there's an app called "Great app" and it has 4 platforms configured (and all in sales) in the App Store Connect: it has iOS, macOS, tvOS, and visionOS. However, you come to a decision to discontinue development and support for e.g. tvOS app/platform but will continue improving the rest of the app platforms. What is 100% clear - there is no way to remove the platform that has been submitted and in sales. Also, there's no way to manage some platforms independently from the rest app platforms (any changes to e.g. country availability affect all app platforms). We clarified this with Apple already. So there's a dilemma: you will always have the app in production and in sales which has a platform that is not anymore supported, maintained, etc. That's very sad from users' perspective as they can still find the tvOS platform app, download it, and become pretty disappointed. Would love to hear thoughts/suggestions/ideas from anyone who faced the same. How did you manage it? Did you prepare some kinds of funneling into your sideload app platform, or put some depreciation screens/information for users, how did you overcome the limitations set in App Review Guidelines, etc. Cheers.

Error Domain=SKErrorDomain Code=5 "(null)" UserInfo={NSUnderlyingError=0x3086335a0 {Error Domain=ASDServerErrorDomain Code=3504 "找不到此项目。" UserInfo={NSLocalizedFailureReason=找不到此项目。}}} 线上App出现这样的报错（大部分用户是好的） 在该报错用户的配合下我们尝试引导：重新登录appid账号、重新设置付款信息、重新下载应用，都不行 而且这个appid登录后可以买别的产品，但是买不了我的内购 请问怎么解决

Hi everyone, I’m facing an issue with setting Azerbaijani as the default language for my app. The app is designed specifically for the Azerbaijani market, where the primary language is Azerbaijani, although Russian is also widely spoken. During the submission process, I couldn’t find an option to set Azerbaijani as the default language. To move forward, I selected Russian, assuming I could change it later. However, I’ve hit a roadblock—I can’t figure out how to make Azerbaijani the default language now. Has anyone else encountered this problem? Is there a workaround or solution to enable Azerbaijani as the default language? I’d greatly appreciate any advice or guidance from the community. Thanks in advance!

Good morning, I'm new to the apple developer program and I'm working with someone I'm not in the same continent with. If I travel for a long time and I have to renew my subscription ($99), will there be a risk that my card for this new residence will not work? If I subscribe with a card from a well-defined region, will I necessarily need a card from this region for renewal? Thanks…

I just received this email, no changes have been made to any of my apps on my side, nor have any third-party services been contracted for any reviews, does anyone have any idea how to fix this? Section 11.2 (Termination) states: (g) if You engage, or encourage others to engage, in any misleading, fraudulent, improper, unlawful or dishonest act relating to this Agreement, including, but not limited to, misrepresenting the nature of Your Application (e.g., hiding or trying to hide functionality from Apple’s review, falsifying consumer reviews for Your Application, engaging in payment fraud, etc.).