I just had an app approved and pending developer release. As part of my release checks, I always download the app using a promo code (even for free apps). This time, on both iOS and macOS, redeeming a promo code for the respective builds gives this error: Unable to Redeem. This content is incompatible with the current software on this device. Update your device to the latest software version and try again. The app targets iOS 26.0 and macOS 26.0, and my devices are on the latest releases. Has anything changed with promo code redemption for approved apps? I typically use promo codes for updates, but have not released a new app in a while.

Hi, I recently built an app and I’m planning to publish it on the App Store. Since the Swift Student Challenge (SSC) is coming up, I’m also considering submitting the same project by converting it into a Swift Playground (with some content trimmed to meet the rules). I believe both I and the project are eligible. My question: if I publish the app on the App Store first and then submit it to SSC, could that violate the rules or lead to rejection? I also have a concern: because I’m a minor, Apple requires the App Store developer name to be my mother’s. However, the app was entirely developed by me. my mother and anyone else did not participate(My mother can't even use a computer.). I’m worried this might create confusion and make judges think I copied someone else’s work, which I did not. Would you recommend publishing on the App Store now, waiting until after SSC, or taking a different approach? Thank you.

Hello, When I recently distributed my app, I received the following warning message: "Starting April 2026, all visionOS apps must be built with the visionOS 26 SDK or later, included in Xcode 26 or later, in order to be uploaded to App Store Connect or submitted for distribution." However, the Apple Developer News page dated February 3 (https://developer.apple.com/news/?id=ueeok6yw) states that apps submitted to the App Store must meet the version 26 requirement starting April 28, 2026. I need to clarify whether the mandatory enforcement begins on April 1, 2026, or April 28, 2026. As the major specification changes in version 26 are significantly impacting our current app development, the exact deadline is critical for us to determine our updated development schedule. https://developer.apple.com/forums/thread/814892 Thank you.

Hi All! I'm being asked to migrate an app which utilizes iCloud KVS (Key Value Storage). This ability is a new-ish feature, and the documentation about this is sparse [1]. Honestly, the entire documentation about the new iCloud transfer functionality seems to be missing. Same with Game Center / GameKit. While the docs say that it should work, I'd like to understand the process in more detail. Has anyone migrated an iCloud KVS app? What happens after the transfer goes through, but before the first release? Do I need to do anything special? I see that the Entitlements file has the TeamID in the Key Value store - is that fine? <key>com.apple.developer.ubiquity-kvstore-identifier</key> <string>$(TeamIdentifierPrefix)$(CFBundleIdentifier)</string> Can someone please share their experience? Thank you! [1] https://developer.apple.com/help/app-store-connect/transfer-an-app/overview-of-app-transfer

Environment OS: iOS 26.2 (Beta/Release) Framework: StoreKit 1 (or StoreKit 2) Environment: TestFlight / Sandbox Device: [Insert your device model, e.g., iPhone 15 Pro] Description I am encountering a persistent issue where SKPaymentQueue.default().finishTransaction(transaction) does not successfully remove the transaction from the queue. Every time a new purchase is initiated, the observer triggers an immediate update with the previous transaction's ID (Transaction ID). The system then displays a system alert stating: "You've already purchased this In-App Purchase. It will be restored for free." Even after explicitly calling finishTransaction, the same transaction reappears in the updatedTransactions array upon the next app launch or purchase attempt. Steps to Reproduce Add a transaction observer in didFinishLaunchingWithOptions. Initiate an In-App Purchase in TestFlight. Upon success (.purchased), call SKPaymentQueue.default().finishTransaction(transaction). Attempt to buy the same non-consumable item (or any item) again. Result: The previous transaction is pushed again, and the queue never clears. What I’ve Tried Ensured finishTransaction is called on the main thread. Verified that the observer is added at app launch. Manually iterating through SKPaymentQueue.default().transactions and finishing all entries. Signed out of the Sandbox account and used a completely new test account. Deleted and reinstalled the App via TestFlight.

Hi, I have a completely new release of my app coming out with a new tech stack. I noticed that only 1% of my users were on iPad so the new app was not created to be 'compatible' with iPad including how it looks on iPad. Can I release this new version of the app only for iPhone? Or because it was previously available for iPad I have to release for iPad as well? Really appreciate any support/guidance on this. Thank you!

We have submitted our app as both iPhone and iPad compatible - we want to remove iPad, but can't find how to do that in the App Store Connect console - any ideas? Thanks in advance Kjell

Dear App Review Team, Our app – Apple ID 6756967338, has been stuck in the “In Review” status for over 10 days (Jan, 19 at 1:33 PM). Normally, reviews begin within a few days, but in our case, it seems unusually delayed. Could you please clarify: • Is there a specific reason for this hold? • Is any action required from our side? • When can we expect the review to finish? Thank you very much for your time and assistance.

Hello everyone, I’m currently enrolling as an Organization from Albania and I’ve been stuck on the "Enrolling" status for 8 business days now. I have my D-U-N-S number sorted and everything was submitted. I sent an email last week to the support but I haven't heard back yet. I’ve already sent another support message 2 days ago but no reply so far. I’m curious to hear from others who have enrolled recently (especially in 2026): How long did your organization verification take? Did you receive a verification phone call, or was it just approved via email? For those in the Balkans/Europe, did you have to provide extra local business registry documents (like the QKB extract) manually? I’m trying to time my launch with my Google Play release, so I’m a bit anxious about the "black hole" of waiting. Any experiences or "nudge" tips would be greatly appreciated! Thanks!

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?

Transaction can not finish in OS26.2 TestFlight

I had a Watch-only app on the AppStore, and decided to add an iOS companion app now. Technically this was very easy, adding just an according target to my project. TestFlight tests where successful, IAPs remained valid for the whole setup etc., watch app could remain standalone as well -- so everything looked "Go" for release. But now customers that already previously downloaded the watch app just see "Purchased" in the AppStore for the app, and they neither automatically get the iOS companion through the update process, nor can they force a download (as there is no cloud icon to explicitly do so -- just the greyed-out "Purchased" button). The watch app updates automatically to the new version, but it seems impossible to initiate the iOS app download. The initial download of the watch-only app also doesn't show up in their list of purchases/download (only on the watch AppStore app, but from there, the iOS app won't be forced to install either). Did anyone face this also and can recommend a solution that can be communicated to affected (i.e. all so far...) customers?

Hello everyone, I’m looking for some guidance regarding the App Store review process. We submitted our app Desteno (iOS version 1.0.1) for review for the fifth time on Tuesday, and as of Saturday, it has been more than four days. The app is still not live on the App Store, and we haven’t received any update, rejection, or message from the App Review team. We understand that review times can vary, but this delay after multiple submissions is a bit unclear for us. There are no pending messages or requests visible in App Store Connect. Has anyone else experienced a similar delay recently? Is there any recommended next step—such as contacting App Review through Resolution Center or waiting longer? Any insights or suggestions would be greatly appreciated. Thank you in advance. — Kartikey (Desteno)

When I update my app name, the App Store URL also changes, and since the app URL contributes to ASO performance, this is a concern for me. I would like to know whether it is possible to change the app name without affecting the URL, or if the previous URL automatically redirects to the new one.

In App Store Connect metadata I added keywords expecting App Store and Apple Watch searches to surface my app using those terms. However searching those keywords does not show my app and it only appears when I search by the app name so I am unsure what is incorrect.

I’m launching my game on May 9 and have been going through Apple’s App Store course. It’s informative but also feels like a marketing push. For those who’ve tried App Store campaigns, did they actually drive results like views, conversions, or in-app purchases? Sharing your app/industry for context would be super helpful.

I’ve been working on marketing my iOS app, but it’s been quite frustrating so far. ASO hasn’t brought the results I expected, and I’m not sure what to try next. I’d like to learn more about indie app marketing beyond keyword tweaks-any blogs, courses, books, or communities you’d recommend for understanding effective strategies and improving app visibility?

I have had an App (AngelNav) available on the App Store since 2023 which was written for iOS v15.0 or later. I am working on a new version which has the same functionality, but a radically new interface as well as taking advantage of the latest features in SwiftUI. I am writing it from the bottom up for iOS26 to ensure a clean codebase to ease maintenance. As I understand it I have the following options: Issue an update to the existing app. This is easy to do but creates a problem for those users with iOS26 who prefer the old interface. In addition I can't see a way to implement bug fixes for previous versions Create a new app (AngelNavNeo). This would allow users with iOS26 who prefer the old interface to stick with it, and I can issue bug fixes on the old version. However, there is no way to share already purchased in-app purchases between versions without a server-side solution and the need for user accounts on my server (neither of which I want to do). Is my understanding is correct, and have I missed anything?

Hi there, I’m writing this because I’m feeling incredibly frustrated and downbeat. I launched my app about two and a half weeks ago, and while it’s been a success in terms of users—with over 2k downloads and 35 five-star reviews via Reddit—it is currently invisible when searched for on the App Store (it can be found by direct link or Google search). Even when searching for the exact app name or my developer name (Robert Lothian), nothing comes up. It’s as if the app doesn't exist in your search database. To make matters worse, the app was featured in several articles, podcasts, and live streams last week. Because of this search issue, potential users who heard about the app couldn't find it. This has not only stunted my growth during a critical launch window but I fear it is causing genuine damage to my reputation as a developer. I raised a ticket last Saturday (102811242184) but haven't heard anything back, I just did a follow-up ticket just now, as it has been a week. I truly believe this is a backend synchronisation issue that just needs a quick look from the engineering team to reset the index for my App ID. Please, can someone look into this or escalate it? I’ve worked so hard on this launch, and it’s heart-wrenching to see it blocked by a technical glitch. App Name: Archivist Browser App ID: 6756570654 Best regards, Robert Lothian

Apple’s documentation indicates that iOS now supports A/B testing for app icons, but I haven’t been able to get it working. My app already includes alternate icons within the same binary, yet when I try to set up an A/B test in App Store Connect, there’s no option to change the icon-only screenshots can be updated in a new treatment.