Hi everyone, I’m reaching out because I’m really struggling to understand what’s happening with my app’s review status. My app was successfully approved and published with: Version 1.0 on May 12, 2025 Then updated to 1.1 on May 18, 2025 Everything was going smoothly — users were engaging, and within the last 20 days alone, in-app purchases totaled $2,100. However, when I submitted a new summer update (with fresh features and an in-app event), both: Version 1.2 and Version 2.1 ...were rejected under guideline 4.3(A) – Spam. This is incredibly confusing because: My app has a completely original design and functionality It provides distinctive value and content There is real user activity and sales I tried everything — submitted explanations, requested a manual review, even scheduled a Webex meeting with Apple. But the meeting was vague, and I still haven't received any concrete details on what exactly violates 4.3(A). Everything just refers back to "not complying with Apple's guidelines" without specifying how. 🆘 App ID: 6744330283 Has anyone faced something similar? Does anyone have insight on how to move forward or how to escalate this issue for a proper manual review? Any advice or help would be greatly appreciated. Thanks in advance, Bao Duy

Hello, I am working on app clips and I wish to know how is the code packaged when the build gets uploaded to App Store Connect? Is there any documentation around this or can you help me with what happens while generating the binary? I added 7 files to app clip target. Some are of 1 KB and others are of 2KB when I look for it's size on my MacBook. However when I upload a build to App Store Connect with these 7 files, I am noticing the size of App Clip increasing by almost 1MB. These files are code files i.e. .swift files and not assets. How is it possible to that the App Clip size grows by an MB for these 7 files? Even if I consider them to be 2KB each, shouldn't the app clip size increase just by 14 or so KB's?

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?

Hello! we're currently in the process of trademarking a company name for an application we're building here in the US. As this has occurred, an app built for UK users has been published with the exact same name. As we understand our trademark wont be enforcable in the UK from the US, we are disappointed as it seems we can no longer use that exact name for our application. How similar can names be in the app store? for example if their app was FunFriend, could mine be "FunFriend - US"? or "FunFriends"?

Hi, We are the developers of an enterprise iOS application for internal distribution. Since a few hours, we start to receive "(app name) is no longer available" error message and can't open the app. But the certificate is still valid, Do you have any advice for an immediate solution?

Hello, please someone help me this outrageous i worked so hard on this game for many months and payed apple developer fee to get my app Rejected for being spam which is completely FALSE my app genre is endless runner which is very popular and have a lot of apps but my story is original my music is composed by a professional musician specifically for my game, the UI designed by ME, yes my control mechanics is the same as many apps—this is expected due to genre standards, not duplication. The presence of similar controls codes does not automatically make a game spam. If this logic applied broadly, many top games on the App Store would be at risk of the same guideline violation, Yes i did use some free to use commercially Unity assets (which is entirely permitted under Apple’s policy), i have customized and integrated them meaningfully into the game, so how is this spam?

So game I created a racing game with open world , all content was made by me from scratch , I understand the appstore was flooded by racing games like mine , but if u compare , test and etc it has been much better , when I started to develop this game , I think about quallity and good experience for users because I've seen what a trash games on the appstore , with screenshots from gta 5 and the game by itself is really just an asset , I aldo bought an asset , but I modified amd added an half of things in this car physics asset , more than half of this asset modified , I'm worked on this game about 4 years , I have big plans for this to update and work more to give to users a console like physics and experience , right now I tried to add some features to my game and adding online mode , the main idea of The game was an open world racing game like forza horizon , with similar car physics , tuning system , and in feature updates with online races , rankings and etc , so what to do right now idk , just to add this online , I've spend 4 years for nothing guys ?)

We submitted our app for review on June 10, and it entered the "In Review" status on June 12. As of today (June 17), we have not received any further updates or feedback. Our customers are eagerly awaiting the release, and we’re becoming increasingly concerned about the delay. We would greatly appreciate it if someone could take a look or let us know if any additional steps are required on our part.

Hi, I have submitted my app for review since 13/06/2025. Today is 17/06 it still in Waiting for Review status. Please help me look into this issue. We need to release it ASAP AppName: 面试虫 AppleID: 6698863686 Thank you

Hi, I have submitted my app for review since 05/26/2025. Today is 17/06 it still in Waiting for Review status. Please help me look into this issue. We need to release it ASAP AppName: 面试虫 AppleID: 6698863686 Thank you

We are working on a screen capture app. I have provisioning setup for a developer id certificate for do direct distribution and a distribution certificate for Mac Store distribution; I submitted the app to the store with the distribution certificate provisioning active. We need to add documentation so while we are waiting, we decided to distribute the app directly and this is where the problems come in. I made the developer id certificate and archive->exported the app. Then I manually stapled the app with "xcrun stapler staple Madshot360.app". I created a dmg file with the exported app. The problems are; The app captures screen area with ScreenCaptureKit. A prior version of the app used a development certificate. When a user runs this new developer id cert app. the macos gets confused because it doesn't connect the new version to the already permissioned older app version. The user has to manually delete the old permission and then restart the app so the new version creates a new record which can then be enabled. This is confusing for the user since the permission says the app is enabled but it really isn't. We experimented with IT using a command line to delete the old app permission. That did not remove the old permission but now the user can't delete this record at all. What can I do to force the removal of a permission that is broken. The command we ran was this. "sudo tccutil reset ScreenCapture com.madwire.Madshot360" The app used to display it's normal warning that screen recording needed the users permission. This is the permission I talk about above. Now there is a second permission screen that states the following; "Madshot360" is requesting to bypass the system private window picker and directly access your screen and audio. This will allow Madshot360 to record your screen and system audio, including personal or sensitive information that may be visible or audible. Allow, Open System Settings. This is basically what the normal alert does. Why the second window and how can I stop it from appearing when the user has already allowed it. Is it because the binary is distributed directly from my computer? Summary: What can I do when a permission is broken? Is there a command that IT can use to remove any old permissions before installing the app. This app is to be used internally. Is there a command line that will remove a specific app's permission before installing the app? Remember, the command line I showed you basically further broke the permissions for this app. What is causing this second warning dialog to be displayed?

Need assistance in implementing this device management feature. Our free plan lets each person use one special device. To make this work, we need to set up device control right after they log in. Because of this, we can’t let people use our app on more than one device or platform at the same time. If we don’t ask them to log in, we won’t know if they have already used their free device on Android or the Chrome extension. But Apple wants us to give people free access to things that don’t need an account. Can you help us find a way to do this?

Issue Description The submission did not include all the required information for apps offering auto-renewable subscriptions. The app's metadata is missing the following required information: A functional link to the Terms of Use (EULA). If you are using the standard Apple Terms of Use (EULA), include a link to the Terms of Use in the App Description. If you are using a custom EULA, add it in App Store Connect. Next Steps Update the metadata to include the information specified above. Resources Apps offering auto-renewable subscriptions must include all of the following required information in the binary: Title of auto-renewing subscription (this may be the same as the in-app purchase product name) Length of subscription Price of subscription, and price per unit if appropriate Functional links to the privacy policy and Terms of Use (EULA) The app metadata must also include functional links to the privacy policy in the Privacy Policy field in App Store Connect and the Terms of Use (EULA) in the App Description or EULA field in App Store Connect. Please let me know where I have to add this link (EULA). And by EULA, they mean a simple terms of use link, or is it something else?

Hello, I am facing an issue with App Store Review Guideline 4.3(a) - Design - Spam. My app was rejected because it was found to be similar to another app previously uploaded on a different Apple Developer account. However, I have lost access to my old developer account and cannot remove or modify the previous submission. Currently, I am unable to: Log in to the old Apple Developer account Remove or update the app that is causing the conflict My new app is intended for internal testing only and is not yet published on the App Store. I have made efforts to modify the app, but the system still detects similarities with the old app. I would like to ask for advice or assistance on how to proceed in this situation, as I no longer have control over the previous account. Has anyone experienced a similar situation, and is there any way Apple can help resolve this? Thank you very much for your support.

Dear community, in order to modernize our build pipelines, I wanted to try out the new App Store Connect build upload API that was introduced in the WWDC video "Automate your development process with the App Store Connect API". However, when POSTing to https://api.appstoreconnect.apple.com/v1/buildUploads, I receive the following error message: { "errors": [ { "id": "9fb916ea-4d26-4712-8c55-d1d4b5320bf2", "status": "404", "code": "PATH_ERROR", "title": "The URL path is not valid", "detail": "The resource 'v1/buildUploads' does not exist" } ] } Is this API not yet available or am I doing something wrong? If it is not yet available, is there an ETA? Thanks in advance & best regards, Yannik

Hello, We want to upload an app for our customers that uses our company's authentication system which will enforce 2factor (2fa) soon. The App review section in App Store Connect accepts only username and password. What is the desired way to interact with the review process now? Will Apple themselves register an account to use with 2fa? Or how could we provide access to the token? Can someone help? Regards

I have submitted my app for review on 3rd of June 2025, and its status is stuck at 'Waiting for Review' since then until today (16th June 2025). I have requested expedited review and contacted support multiple times, but to no avail. I am posting it here hoping that it can get expedited as our stakeholders depend on this app update. Thank you. My support ticket are as follow : 102617392761

Hi, My developer payment was marked as "Paid" on June 5, 2025 in App Store Connect. As of June 16, the funds have still not arrived in my bank account. Apple only provides a Transaction ID (324756355), but no EFT or SWIFT reference number. My bank confirmed there is no record of any incoming or returned payment. Other developers have received their June 5 payments already. Mine seems to be either not sent or stuck. Apple support keeps telling me to wait 30 days, but without proof of actual transfer, this isn’t acceptable. Has anyone experienced this kind of delay before? Thanks.

Hi, I have uploaded the Main App with App Clip to Apple Store Connect and launch in TestFlight. But at first build I wrote wrong App Clip's associated domains in the App build target ,and also mistakes in the AASA file. Then I correct it like appclips:com.***.***.AppClip in both places. However, I tried many uploaded version and it still display "The app clip in not currently available... " error. The domain is successfully verified in App Store Connect and the test version can dowloaded to device for testing. Only that it can't show the right Card as expected. I want to ask if I set the wrong domain in the beginning few builds, and correct it later. Will it work again or not? Moreover, the tester email is not the same as apple id for tester's mobile phone. I have corrected it . I don't know will it affect the result ,and maybe something have stored in Apple backend server for testflight data and need to be refresh to make it work. Thanks and please advise. Best regards Sunny.

Whenever I use third-party apps on my iPhone SE 3, they don’t work properly. The apps even start crashing after using them for a while. please fix this bug in the next beta release?