I noticed that https://developer.apple.com/news/upcoming-requirements/ is no longer being updated with SDK requirements. You would think this would be a nice place to check for upcoming requirements for app submissions etc. Can we get the Xcode 26 requirements added?

Hi all, I've been attempting to implement the Texas age range restrictions for an app I work on. I've banged my head against it for the last week and have a flow that is 99% working. I have all of the cases working exceptt when a significant change is approved. The issue I'm running into, is that let responsesSequence = AskCenter.shared.responses(for: SignificantAppUpdateTopic.self) is not receiving a response the first time it's called. It's only after the second time it's called that a response is registered and then I allow a user to access my app. When I set significant app change declined, then responses(for: ) returns on the first call to it. I can't for the life of my figure out why one works and the other doesn't. Has anyone else encountered this or have suggestions for me? I'm happy to post more code here in order to come to a resolution on this issue.

It is the beginning of February and we have not yet received our 1099 from Apple. Has anyone received theirs? Can I download it somewhere or does it only come via snail mail? Thank you

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

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?

Hi all i released my first app and it has passed the review 3 days ago. I can open the link on my pc but not on iPhone or iPad. https://apps.apple.com/us/app/the-wolff-timer/id6758272038 any idea what could be wrong?

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

Hi, I enrolled in the Apple Developer Program as an individual and my order page shows “Enrollment Complete”, but my developer account page at developer.apple.com/account still shows “Pending”. In Xcode, under Settings/Preferences → Accounts, I only see Personal Team (no paid Program team), so I can’t use TestFlight / App Store Connect for external testing.

Hi Apple Team, I hope you are doing well. I am reaching out regarding the upcoming watchOS architecture requirements announced in your official communication. According to the notice, beginning April 2026, watchOS apps uploaded to App Store Connect must include the arm64 architecture and be built with the watchOS 26 SDK. zoom current watchOS app, however, only supports arm64_32, and the app size is already over 60 MB in its current form. If we add support for both arm64_32 and arm64, the binary will almost certainly exceed the 75 MB app size limit, and potentially violate the size constraints for each architecture slice as well. This raises practical concerns about how a dual-architecture watchOS app can remain within the required size limits. Could you please advise whether Apple has any recommended approach or best practice for this scenario? For example: Does Apple suggest that developers transition to arm64-only and drop support for arm64_32 devices? Are there any exceptions, additional guidelines, or alternative mechanisms for handling apps that exceed the size limit when including both architectures? Are there recommended techniques specifically for watchOS to reduce binary size when supporting multiple architectures? Any guidance would be greatly appreciated, as we want to ensure our watchOS app remains compliant with the new requirements while continuing to deliver a reliable experience for our users. Thank you very much for your support, and we look forward to your advice.

Hi team, I wanted to share some friendly feedback based on my experience as a relatively new developer submitting apps to the App Store. The documentation states that 90% of submissions are reviewed within 24 hours. However, across my submissions, I've found the average review time to be closer to five days. I completely understand that review volumes are likely substantial, and there may well be differences between iOS and macOS review queues. This isn't a complaint - just a suggestion that adjusting the stated timeframes might help set more realistic expectations for new developers. When I first started submitting apps, the longer wait times left me wondering whether I'd done something wrong. Thanks

Hi everyone, I’m facing an issue with my App Store seller name after changing my Apple Developer account type, and I’d like to know the correct and up‑to‑date way to fix it. Previously, my Apple Developer Program account was enrolled as Individual. Recently, I converted it to an Organization account using my company D‑U‑N‑S number. In the Apple Developer “Membership” page, I now see: Entity name: COMPANY ALBABGHA ALNATQ LLC Enrolled as: Organization Team ID: LC9U6F8EBW I am the Account Holder of this team. However, on the App Store, the Seller / Developer name for my existing apps is still displayed as my personal name (e.g. “Ahmed Alahmadi”) instead of the company name “COMPANY ALBABGHA ALNATQ LLC”. In App Store Connect → App Information, I don’t see any option to change the seller name for the app. I understand that this is usually controlled by the account / legal entity, not per‑app, but it hasn’t updated automatically after the conversion to Organization. My questions: After converting an account from Individual to Organization (with D‑U‑N‑S verification), is the seller name supposed to automatically change to the company’s legal name for all existing apps? If not, what is the correct procedure in 2026 to update the seller/developer name from my personal name to the company name? Do I need to contact Apple Support to manually update the seller name at the account level, or is there another setting / process in App Store Connect that I’m missing? I do not have a separate old personal team and a new company team; it’s the same account that was converted to Organization. In this case, I assume I don’t need to transfer the apps to another team, just change the seller name. Is that correct? Any official guidance, recent experience, or links to updated Apple documentation would be greatly appreciated. My goal is that all my apps show COMPANY ALBABGHA ALNATQ LLC as the seller, not my personal name. Thank you in advance!

We're a premium paid app - currently listed in Maps & Navigation as our primary category, with Travel set as secondary. We’ve been in Maps & Navigation for ~9 years and consistently rank in the top 5. However, aside from one other app that regularly shares that top-5 position with us, most apps in this category don’t appear relevant to our product or audience. They also don’t seem to reach the same type of user we’re targeting. By contrast, the Travel category contains a much higher concentration of apps that serve the same type of user as ours, and feels like a more natural discovery fit. What’s unclear to us is: Why a secondary category exists if the app does not appear to surface in that category for browsing/discovery. The implications of swapping our primary and secondary categories. Specifically, if we reverse Category 1 and Category 2: Do we retain our existing ratings and review history? Are there any penalties or long-term impacts beyond potential short-term ranking changes? We’re comfortable with an initial ranking reset if that’s expected, but after 9 years in market, we want to be certain there’s no loss of accumulated reviews or other irreversible downsides before making the change. Any clarification from those with experience would be appreciated.e for an "experiment".

I am a developer, and I first launched the tvOS app. Users purchased it from the Apple Store and can use the tvOS app. Then, I uploaded the iOS app again, but some users (those who did not use the promotional code) were unable to download it due to the "purchased" status displayed on the Apple Store. How can I solve this problem? At present, it has been tested to restart, exit with ID, and log in again. Another question to ask, does a promotion code correspond to a platform? Can't it be universally used across all platforms, right?

Hello Apple Developer Forums, I’m preparing to submit an app update that includes an in-app subscription. As part of the submission, I need to provide screenshots showing where the user initiates and completes the subscription purchase flow. The issue is that App Store Connect keeps rejecting my screenshot upload with an “incorrect size” (or size invalid) error. I have already tried exporting the screenshot in all sizes and resolutions described in Apple’s documentation, but none of them are being accepted so far. Could you please advise: What exact pixel dimensions / format requirements App Store Connect currently enforces for these screenshots (including file type and color profile, if relevant)? Whether there are any known issues or common causes for this error (e.g., metadata, alpha channel, scaling, or export settings)? Any recommended workflow/tools to generate a compliant screenshot that reliably uploads? Thank you in advance for your help.

Im getting this error when try see my apps on App Store Connect:  Bad Gateway Correlation Key: PRFC7IOFSRO3NZQIRHHWVUMUIE

Dear Apple Support, We are experiencing an issue where iPhone-only apps (marked as "Designed for iPhone" in the App Store) are not appearing at all in the App Store on newer iPads running iPadOS 26.2 (A16 chip model), including in managed distributions via Apple Business Manager. The app in question is X App, and it works fine on older iPads with previous iPadOS versions. Is there a policy change or stricter enforcement starting from iPadOS 18 or later that prevents iPhone-only apps from being searchable, visible, or assignable on iPad devices (especially supervised/managed ones)? If yes, does the developer need to update the app to Universal or add explicit iPad compatibility in App Store Connect for it to become available again? We would appreciate any official reference or confirmation on this behavior. Thank you for your assistance.

Hi! Tried to enroll, proceed with payment but it's been already 10 days but no confirmation but acknowledged says 2 business days, please can you tell me what should I do?

Hello! I recently submitted a request for the Family Controls (Distribution) for my app, and I’d be super happy if i could have some information about how long this process usually takes so i can plan accordingly. It would help immensly since we want to ship the app as soon as possible. I submitted the request around a week ago. Is there anything I can do on my end to help the process move more smoothly? Thanks in advance!