I submitted my iOS app for review with the "On Hold" status, but I uploaded the build using an older SDK version. According to the guidelines, starting April 24th, apps need to be built with the updated SDK. If my app is approved and ready for release, will I be able to release it after April 24th, even though it uses the older SDK? Also, how long can the app remain in the "On Hold" status before I need to take further action?

Hello everyone, my application has been stuck in the "Information Submitted" status of Apple's review process for several weeks now. The system shows "Thanks for providing additional information—it is currently processing and will be reviewed shortly," but there has been no progress. During this time, I cannot access App Store Connect, and payments may be delayed. This situation has continued for weeks, seriously affecting my development and operational plans. Has anyone experienced a similar situation? Are there any methods to contact Apple to expedite the process or understand the specific reason for the delay? What additional information should I provide to move the review process forward? Thank you for your suggestions and help! @Apple

Hi everyone, I’m experiencing an unexpected delay in the review process for my app (RadioBar), and I’d appreciate your guidance. Here’s the timeline: March 24: Received feedback from the review team stating that identified issues could be resolved in the next update. Same day (March 24): Fixed the issues immediately and resubmitted the app. March 24–28: App remained in "In Review" status with no updates. March 28: Resubmitted the app again, assuming possible system issues. Status returned to "In Review." March 31: Requested an expedited review via the Resolution Center due to urgent bug fixes impacting users. As of April 2, the app remains stuck in "In Review" with no progress. This delay is disrupting my development schedule and affecting users awaiting critical fixes. Steps taken: Ensured compliance with all guidelines. Responded promptly to initial feedback. Submitted expedited review request. Could you kindly investigate the delay and prioritize the review? Any clarification or assistance would be greatly appreciated. Thank you for your support!

I received an email from app_notification @apple.com about violating section 11.2 roughly 21 days ago. There is nothing in resolution center (there doesnt seem to be a way for me to access resolution center). I have tried ringed apple dev support but they dont know anything about it and suggested replying to the email. I have replied to the email and had no response. The 30 days is almost up. Is it possible to speak to somebody about this please as it is very urgent? Thank you

I've seen other similar posts with no clear answers and solutions. My Unity app has been rejected several times with this message: The UIRequiredDeviceCapabilities key in the Info.plist is still set up in such a way that the app will not install on the device used in review. Review device details: Device type: iPhone 13 mini OS version: iOS 18.4 Next Steps Please check the UIRequiredDeviceCapabilities key to verify that it contains only the attributes required for the app features or the attributes that must not be present on the device. Attributes specified by a dictionary should be set to true if they are required and false if they must not be present on the device. I have made sure the submitted app has only one value for UIRequiredDeviceCapabilities, arm64, which is required by Unity. Initially Metal was listed as well, but I've removed it in trying to fix this problem. Additionally, I've ran the app through TestFlight and it functions fine. I'm not sure what else to try to fix this issue, though I've seen from other posts that indicate this type of rejection could possibly be a bit of a red herring and the real issue could be something else. Any help would be appreciated

Lately TestFlight has been having unexpected delays for me. For context, I have an app that I am just testing internally right now, so whenever I have a new build the process I follow is: Upload build to App Store Connect Wait for build to finish processing (typically less than a minute) Add compliance info in App Store Connect Wait for build to be distributed via TestFlight For the last few months, after I entered the compliance info, my app would be available for TestFlight distribution almost immediately after I entered the compliance info. I would get the email notification and I could see my new build on TestFlight. I am getting the notifications from App Store Connect that my build has completed processing within a minute or two of uploading it. Then, I enter the compliance information in App Store Connect. Lately, it has been taking multiple hours in between when I provide the compliance info and when the new build is available on TestFlight though. So there is a seemingly random time period in between when I enter the compliance information and when the app is actually distributed to TestFlight. I am not sure why this process that used to be immediate now has multiple hours of lag. There also does not appear to be any way for me to manually check on the status or anything. After I enter the compliance info, it is an entirely hidden and automated process to then push that build out to TestFlight. Is there anything I can do to improve this, or are there any known causes for this issue? I have tried re-submitting another new build version to try and "flush the pipeline", and that worked once before, but it doesn't appear to be working anymore.

Hi, I have submitted my app for review since 28/03/2025. On 31/03/2025, I don't see any review so i cancel then resubmit. Today is 1/4 it still in Waiting for Review status. Please help me look into this issue. We need to release it ASAP AppName: Breadstack Live Chat AppleID: 1622537456 Thank you

I have an unpublished app that we use as our development environment, and we need to transfer it to another Apple Developer account. Since the app is not published, the standard App Transfer process in App Store Connect does not apply. Is there any workaround to transfer the app without creating a new developer account, changing the bundle ID, or reconfiguring all the associated certificates and provisioning profiles? We would like to avoid the need to rebuild and reconfigure everything from scratch. Any guidance on this process would be greatly appreciated!

I want to submit my app for review, but I'm getting this error. When I click 'Edit' under iOS Submission, it redirects me to the 'Prepare for Submission' page, but it doesn't specify exactly what I need to edit. Can you help me with this issue?

Hello I'm writing on this forum to find if anyone has solution for this issue. I've submitted my app on March 14th. And today is the end of March. I've stayed patient, not trying to bother whomever related to the review or Apple for two weeks. Then I've tried requesting expedited review, but couldn't hear anything for days. I've mailed developer support to know what's taking so long, and to tell that I'm willing to submit additional information about the app and the developer if that helps or if necessary. But couldn't hear anything. I sincerely respect the policy of Apple and the reviewing process, and I truely want to adhere to it, but my experience of not getting anykinds of respond is surely unpleasant. I had to dramatically change my app launching schedule due to the delay. Let's say the delay is reasonable. But waiting for half a month, replanning my launch again and again without knowing anything about what's going on in the review? I'm willing to fully cooperate with whomever related to my app's review. If anyone has solution for this please let me know. Thank you.

Im getting Invalid Binary error the last 48 hours, I cant find a solution for this problem, also the apple dont give more information about the error. Please can you provide more information about the Invalid Binary rejection.

Hi, I have a question about Section 3.1.1 of the App Store Review Guidelines regarding In-App Purchases. Is it mandatory to include In-App Purchases in my app? My app is an extension of my website, which has been online for four years and serves a large student base. We offer courses that students purchase through the website. Once purchased, they can access lessons, watch videos, download files, answer quizzes (optional), participate in group chats, and review courses. In the app, users can view all courses and categories, access some free lessons to decide if they want to buy the course, and search for courses—similar to platforms like Udemy. I do not wish to use In-App Purchases or any external payment systems within my app. Instead, I prefer that users purchase courses on the website and then access them via the app. I will not include external links, calls to action, or any mentions that direct users to purchase from the website. Essentially, I plan to inform users that purchases are not supported in the app, and they will understand this implicitly. Is this approach acceptable?

Hello, I am a first time app developer and a few days after my app was approved I got a termination notice and an app removal notice from apple without any info, proof or explanation. I do not believe I did anything wrong so I submitted an appeal within an hour after receiving the termination notice. I didn’t receive any confirmation that they received the appeal or any resolution (and it has been 16 days). I contacted support through email and got a generic response something like ‘we are working on our backlog, you need to wait’. the thing is that my account is going to be terminated in less than 2 weeks and I’m panicking and don’t know what to do. did anyone have any similar experiences and how did you resolve it? this is a part of the message I received: Upon further review of the activity associated with your Apple Developer Program membership, it's been determined that your membership, or a membership associated with your account, has been used for dishonest or fraudulent activity, in violation of the Apple Developer Program License Agreement. Given the severity of the identified issues, all apps associated with your Apple Developer Program account have been removed from the App Store and your account has been flagged for removal. Because your account has been flagged for removal, any earnings payments are paused and app transfers are disabled. Creating new accounts after receiving this message may result in the termination of the new or associated accounts. Evidence of Dishonest or Fraudulent Activity App submissions from your account have engaged in concept or feature switch schemes to evade the review process, such as dynamically populating different app content after review, submitting apps with hidden features, repeatedly submitting misleading apps, and/or submitting apps with concrete references to content that you are not authorized to provide or is otherwise not appropriate for the App Store.

Dear Apple Developer Community, I have been facing repeated 4.3 Spam rejections for my game on the App Store, and I am struggling to understand the reason behind it. My game is a multiplayer racing and drifting game, fully designed and developed from scratch. Every aspect—including UI, 3D assets, game mechanics, and netcode—has been built independently. While I have used some paid assets, they are strictly for visuals only (such as models and textures), not game templates or code templates. Additionally, these assets have been significantly modified to fit my game’s unique style. To address the rejection, I have made numerous changes—some major and some minor—including: Modifying gameplay elements Adjusting UI and mechanics Updating the App Store listing (title, screenshots, description, and category) Despite these efforts, I continue to receive the same 4.3 Spam rejection. I have also tried to appeal multiple times but have not received any response. My game is categorized under Racing and Simulation (with Racing as the main category), but I even tried submitting it under just Games without subcategories—yet the rejection persists. I’m truly frustrated and unsure what else I can do to resolve this issue. If anyone has faced a similar situation or has any advice on how to proceed, I would greatly appreciate your insights. Thank you in advance!

Hello, I am in the process of developing a peer-to-peer parking app and would like clarification on whether my payment system requires In-App Purchases (IAP) or if I can use custom payment system embedded in-app such as Stripe for transactions. About the App: Users can add empty parking spots they find on a map. Other users can pay to unlock a group of spot coordinates (availability is not guaranteed). Users can also host their own occupied parking spot and sell it to another user, guaranteeing availability. The app uses a virtual currency (“coins”), which represent real money and are used to pay for unlocking spots and purchasing hosted spots. Users can fund their account with coins, and coins they earn from selling spots can be cashed out via PayPal once a minimum threshold is met. Users cannot cash out coins they purchased—only the ones they earned. The funds/coins are controlled by the app’s servers acting as a middleman. If a purchase transaction occurs, the app deducts the coins from the purchaser‘s account and credits the sellers account minus service fee of the app. My Question: Since the app facilitates real-world transactions between users, can I use Stripe to allow users to purchase coins, or does Apple require In-App Purchases (IAP) for funding accounts? If not do you have any suggestions on different methods? I want to ensure compliance with App Store policies before proceeding. Thank you! Best regards, Mubin

Lately, when adding a new advanced experience with a new path (with the same domain), it is taking more than a week to get published, when it used to take around 24h. Am I doing something wrong that causes the long delay? Someone else is having this problem? Is something wrong with our assumptions of how it works? Some assumptions and observations we have around app clip advanced experiences: Once the app and its appClip are published, new advanced experiences (new paths + cards) don't require a new app review When adding a new advanced experience, it gets reviewed before being published There is some bug where even after the experience is published, its status only shows 'Received' Edits of existing url paths (changing text or image) take less than 24h to propagate As a workaround we are publishing paths we are still not using with general app clip metadata and then editing when we require them, but this does not allow us to have custom path names for the experiences as we need to 'reserve' them beforehand.

I have submitted two apps and both have been pending for a week. I usually get a response within 24 hours. Is this happening to anyone else? how did you solve it?

My flagship app that took months to make was rejected for spam, then accepted, updated several times no problem and then suddenly rejected again for spam. Made no sense. Then I appealed it and have been waiting 3 weeks already. Is this even normal? I really regret paying the membership fee since I've had nothing out of it so far.

as a forum of developers and apple engineers do you think an app like this could be published? Thanks

Hello everyone, I’m implementing external purchases in my app and I’m using ExternalPurchase.linkToExternalPurchase() on iOS 17.4+ to display the Apple modal for external purchases. However, I need to handle purchases on iOS 15.4 - 17.3, where StoreKit’s external purchase APIs do not provide tokens and return false. Questions: What is the recommended fallback for iOS 15.4 - 17.3 since the Apple modal is not available? Should I display a custom modal or directly open a WebView with the purchase page? On iOS < 15.4, since external purchase APIs are unavailable, is it acceptable to open the external purchase page directly in Safari instead of within the app? Will Apple reject the app if I use a custom modal for purchases on iOS 15.4 - 17.3 instead of the Apple-provided one on iOS 17.4+? I want to make sure my implementation complies with Apple’s guidelines while providing the best experience for users on older iOS versions. Thanks in advance for your help!