We have an app with a few App Clip Advanced Experiences. Since around 28th of August the status of the experiences seems to be stuck in either CREATE_SUBMITTED or UPDATE_SUBMITTED and they don't get updated to PUBLISHED anymore. I found this in the experiences JSON loaded by AppStoreConnect when editing the experiences: "statuses": { "doc_count_error_upper_bound": 0, "sum_other_doc_count": 0, "buckets": [ { "key": "PUBLISHED", "doc_count": 182 }, { "key": "CREATE_SUBMITTED", "doc_count": 7 }, { "key": "UPDATE_SUBMITTED", "doc_count": 3 } ] }, This shows that 10 experiences are stuck in other status than PUBLISHED. I created a Feedback with ID FB15041208 and a DTS last week. This is REALLY important for us to be fixed immediately since we have customers that rely on this!

Hello, I have an app with a few essential asset packs currently totaling to ~8GB. I've noticed that when trying to install the app fresh from TestFlight, there is a significant delay between tapping install and the app appearing on the device in the loading state. The delay is long enough where it's hard to tell what's happening, or if the installation has failed. This also appears to be an issue in App Review, as I've had my app rejected twice due to the app not loading on the reviewers device. The reason they gave is UIRequiredDeviceCapabilities is blocking the installation, but UIRequiredDeviceCapabilities is empty. Note: I'm not looking for App Store review help, simply sharing the extent of the issue. Thank you

My app that's been around since the dawn of the Mac App Store, and which uses its own receipt validation code for 15 years now, recently sometimes triggers a "does not support the latest receipt validation requirements" error message with my app's users. But I cannot reproduce it, even if I freshly install the app on a M4 Mac running macOS 26.2. So I have a hard time testing my fix. Does someone have a sample receipt file they could share with me (including the MAC from "en0" / GUID device ID), or do you know where I can find one that uses the new SHA-256 hash? In fact - when reading https://developer.apple.com/documentation/appstorereceipts/validating-receipts-on-the-device it seems that there's only a SHA-1 after all. So why do some users get the "receipt validation requirements" message at all? I'm only reading the receipt, decoding the ASN.1 fields and then validate the hash from the receipt (field 5) against the SHA-1 from the GUID+receipt, as always, calling libCrypto's SHA1() function. So, what would even trigger the message, as I'm not invoking any higher-level APIs that would verify the receipt for me, and thus would know when something is wrong?!?

Guideline 2.5.1 - Performance - Software Requirements The app uses or references the following non-public or deprecated APIs: Iobmobile Classes: • __SwiftValue The use of non-public or deprecated APIs is not permitted, as they can lead to a poor user experience should these APIs change and are otherwise not supported on Apple platforms. Can anyone she some light as to what __SwiftValue even means?

Can't Edit Age Ratings in App Information Section of App Store Connect for released App Versions. I only have option to View. I think some of the Age Rating questions are still unanswered but when I view them, I can't Edit them. Non-released apps of mine in App Store Connect allow me to edit answers to the Age Ratings questions but I can only View Age Rating questions for released apps. Do I have to create a new version/build and submit to App Store Connect to be able to Edit the Age Questions?

What am I missing here? 😐 Prepare all required actions Run ./.github/actions/verify-copyright Run echo "📋 Checking copyright file..." 📋 Checking copyright file... ✅ Copyright file exists at: fastlane/metadata/en-US/copyright.txt 📝 Copyright value: © 2025 Enterprise Support ✅ Copyright format valid: © 2025 Enterprise Support ✅ Copyright metadata validation passed

Hello everyone, My app has been rejected under guideline 4.3(a) – Design – Spam. It is a padel sports-tracking app with: – Bluetooth sensor connection – live session tracking – AI-generated coaching feedback – community feed and notifications – video analysis features The review states that my app “shares a similar binary, metadata and/or concept as other apps with only minor differences”. However, this app is fully custom developed, not generated from any template, and not a reskinned clone. It is part of a larger project including custom hardware sensors and backend. I would like to better understand what exactly triggered the rejection: – Is it the design? – A specific feature? – The metadata / screenshots? – Or similarity detection with another app name or concept? My goal is to comply fully with Apple guidelines and improve the app if needed, but I need more concrete direction to do so. Any guidance from Apple engineers or other developers who have faced 4.3(a) would be appreciated. Thank you in advance 🙏

Hi everyone, my name is Donovan, I am sharing here the official response I received from Apple following my appeal with App Review Board (image attached). For context, I am an independent developer and a student, working alone. This application was originally created as a student project, with a very simple goal: to improve my skills in mobile application development and to understand the entire creation cycle, from the initial idea to a genuinely usable application. What was meant to be an exercise gradually became a real product. Over time, many people tested the project, used it, provided positive feedback, and encouraged me to take it all the way. That is why I decided to continue it, structure it properly, and finalize it with the level of seriousness expected from a public-facing application. Today, the application is a dating and social connection app, entirely free, with no blocking paid features, funded only by light and optional advertising. It follows the rules, works correctly, and offers features that Apple itself acknowledged as useful and informative. And yet, after review, the message is clear: it is not the quality that is being questioned, but the category. Because it is a dating app, a category considered saturated, two years of independent, self-funded work, carried out seriously and in compliance with the rules, can simply be dismissed. What is being judged here is not the work itself. It is the right to enter. The “unique and very high-quality experience” being required appears to be a threshold reserved for those who are already established, visible, or funded. For a serious student project carried by a single developer, the door remains closed, cleanly, politely, definitively. For those who still wish to see what the application looks like, I have attached a few images illustrating the interface and the main features. Unfortunately, this will likely be the only way to discover it on iOS. Under these conditions, the conclusion is pragmatic. Rather than continuing to defend the very existence of an honest and free project, it becomes more coherent to invest my energy where it is genuinely accepted. On its side, Android validated the project without difficulty. It still allows an independent developer to propose an idea, let it evolve, and bring it to completion without requiring prior success just to earn the right to try. It is therefore very likely that these two years of development will never make it to the App Store. Not out of frustration. Out of clarity. I am publishing this message not to provoke, but to inform other independent developers: Apple is a remarkable platform, provided you are already established on it. And this is a reality worth knowing before turning a student project into a life project. Screenshots:

Hello, Our iOS app (Flutter + Swift) was rejected under Guideline 2.5.1 with the following message: The app uses or references the following non-public or deprecated APIs: Runner Classes: __SwiftValue From our investigation, __SwiftValue appears to be an internal Swift runtime class automatically generated by the Swift compiler for Swift–Objective-C bridging. It is not imported, referenced, or used directly in our source code. We verified that: The symbol exists only in the compiled Runner binary It is not referenced by any third-party framework explicitly It appears in standard Swift runtime behavior We previously removed a legitimate private API (PGHostedWindow) from a dependency and resubmitted, after which this new rejection appeared. Questions: Is __SwiftValue considered a private API usage by App Review, or is this a false positive? Are there recommended build settings or mitigations to prevent this symbol from being flagged? Should this be escalated for manual review? Any guidance from Apple engineers or developers who encountered similar rejections would be greatly appreciated. Thank you.

We are planning to migrate our application from an iOS In‑App Purchase (IAP) subscription flow to an external web purchase flow. The intended user journey is: The user taps a “Subscribe” button in the app. The user is redirected to a web-based checkout to complete the purchase. The user returns to the app, and subscription access is unlocked based on entitlement verification from our backend. Our app is currently listed in the Education category. Before we begin this refactor, we would like confirmation on the following: Entitlements / permissions Do we need to request any specific Apple entitlements or approvals to implement this external purchase flow (e.g., external link or alternative payment related permissions)? Compliance / review requirements Are there any specific App Review compliance checks, disclosures, or review process requirements we must satisfy when moving from IAP to an external purchase flow? If relevant, are there constraints based on app category (Education) or product type (subscription)?

Apple Developer Support The situation is as follows: Recently, we upgraded from an individual developer account to a company account about 2–3 weeks ago. When it came time to renew the account, it was strange that the fee displayed was $99 instead of $299. We had no way to change this, so we proceeded with the $99 payment. After that, Apple introduced new terms and conditions. When we tried to accept them, the account status did not change at all. I clicked “Accept” many times, but it remained in pending status. When I checked the browser console (F12), I noticed that Apple was returning a 500 error, but this error was not shown anywhere in the UI. I have called and emailed Apple support many times. However, they insist that our company account is already active and that we just need to accept the terms and conditions. Unfortunately, we are unable to accept them due to the error returned by Apple’s system. I explained this to them, but they still insist that we simply follow their instructions. As a result, we are currently stuck and do not know how to proceed so that the account can be fully activated and our app can return to the Apple App Store: We accepted Apple's terms on the 22nd. Organization account with $99, unclear why: I've clicked accept many times but it didn't work (Apple error 500), and the status remains pending: Therefore, I am hoping to get help from this forum in case anyone has experienced a similar issue and found a solution.

The situation is as follows: Recently, we upgraded from an individual developer account to a company account about 2–3 weeks ago. When it came time to renew the account, it was strange that the fee displayed was $99 instead of $299. We had no way to change this, so we proceeded with the $99 payment. After that, Apple introduced new terms and conditions. When we tried to accept them, the account status did not change at all. I clicked “Accept” many times, but it remained in pending status. When I checked the browser console (F12), I noticed that Apple was returning a 500 error, but this error was not shown anywhere in the UI. I have called and emailed Apple support many times. However, they insist that our company account is already active and that we just need to accept the terms and conditions. Unfortunately, we are unable to accept them due to the error returned by Apple’s system. I explained this to them, but they still insist that we simply follow their instructions. As a result, we are currently stuck and do not know how to proceed so that the account can be fully activated and our app can return to the Apple App Store: We accepted Apple's terms on the 22nd. Organization account with $99, unclear why: I've clicked accept many times but it didn't work (Apple error 500), and the status remains pending: Therefore, I am hoping to get help from this forum in case anyone has experienced a similar issue and found a solution.

I get a lot of downloads from outside USA but almost no conversion (subscription/IAP) from those countries. Apple App Store does the price conversion based on currency conversion and VAT but it does not take into account that $10 in India or Argentina is a much bigger portion of ones income compared to a US person. Converting all these prices (175 of them) manually is very cumbersome for each subscription tier and for each region.

The title says by itself. We've been using advanced app clips a lot and have created more than hundreds of advanced app clips for the customers. Suddenly, few days ago, the most recently created advanced app clips stopped working as they got stuck with CREATE_SUBMITTED status. It seems like it has already happened before to someone else: https://developer.apple.com/forums/thread/763374 It probably be OK if it showed a Safari notification but it shows an error due to another bug reported here: https://developer.apple.com/forums/thread/803187

Our Application [7 Dawns: Echoes] was recently rejected by the App Store for Guideline 4.3 Apple ID:6753892922 Bundle ID:com.ark.jylhgl.ios Change of Operating Entity Our company, has obtained exclusive global operating rights (excluding Mainland China, Hong Kong, Macau, Taiwan, and certain regions of South Korea) from the copyright owner. The previous distributor’s version, Eternal Sword M (App ID 1369681345, Bundle ID com.emagroups.ea2), has been fully removed from the App Store. Our cooperation with them officially ended on December 29, 2023. New Version Updates This submission is not a duplicate, but a newly operated and updated version. We introduced new gameplay systems (7-day seasonal competitive mode, team-based PvP, dispatch and multi-pet strategy systems), optimized monetization and in-game economy, and improved performance and UI (including redesigned app icon and key interfaces). Evidence Submitted We have provided the Operating Authorization Letter and Software Copyright Certificate via App Store Connect and email to the review team. and we have submitted Review Support but no reply!

When I distribute my app, is it possible for it to be approved by apple when not complete, maybe with reduced levels. Once I add more levels, I release another update? Would apple approve my app with reduced levels, or would they say ot enough content.

Good afternoon, everyone! I received a notification that my app was rejected for the following reason: "We noticed that the user is taken to the default web browser to sign in or register for an account, which provides a poor user experience." The app is a directory of partners that offer a benefit to our members. So the intent of the app is for users that are already registered with our nonprofit to access their benefits using existing account credentials. (Note: The sign-in itself is handled within the app after the account is created.) Is there any way to make this compliant with guidelines without having to offer a duplicate registration form within the app and sync them?

I understand that private APIs are not permitted under Apple’s App Review Guidelines. However, our application requires I²C communication, and we are currently considering the following APIs: IOAVServiceReadI2C IOAVServiceWriteI2C IOI2CSendRequest Could you please confirm: Is there any provision to use these APIs in a Mac App Store–approved application? Are there public alternatives available for achieving I²C communication on macOS? Thank you for your guidance.

If an app is rated 4+, does it have any additional obligation due to the SB2420 beyond this rating on the AppStore ?

There’s still debate on what drives App Store rankings, but some confirmed factors include app name, subtitle, keyword field, downloads, ratings, and in-app events. Likely influences are stability, retention, conversion rate, and user behavior. Search relies most on metadata, Top Charts focus on download velocity, and Featured spots are editorially chosen. Elements like promo text, long description, and release notes don’t impact rankings.