My app has been under review for exactly 35 days. There are no response since the first day, it is just waiting in the In review stage. I canceled it thinking it was a bug and sent it again, but there is no progress. I have sent more than 10 tickets, but no response. I opened a topic in the forum, but there is no response eitheri this is second. There is no place I can reach or ask for help. The Apple team is working great, you are great :) They will probably reply to this post with the words "click this link to get support" and direct me to the link I have previously submitted +10 tickets and have not received a response.

Hi everyone, I’m facing a recurring issue with my macOS app being rejected during App Store review, and I’d really appreciate any guidance. The subscription flow in my app is implemented using StoreKit, and everything works perfectly in our development environment using a StoreKit configuration file. It also behaves as expected in Sandbox testing and TestFlight — I even had few beta testers confirm that the subscription information is displayed correctly and the purchase flow completes without issues. All required subscription details are configured in App Store Connect: • Subscription duration and the description of the services offered • Price and price per unit where applicable • Paid apps agreement and related forms are correctly filled However, when the app is submitted for review, the subscription screen fails to display the expected information. From what I can tell, the product information fails to load from the App Store in the review environment — even though everything is working fine on our side. We’ve already submitted a video to Apple showing the subscription UI working in the Sandbox environment, but the app continues to be rejected under guideline 3.1.2 due to missing subscription info in the binary. Is anyone else experiencing similar behavior during review? Could there be a caching issue or delay in StoreKit syncing for newly configured products? Any help or suggestions are very welcome. Thanks in advance!

We are currently implementing the payment flow, and for handling payment details — including card entry and validation — we are utilizing a WKWebView. The webview securely loads the payment provider’s page, ensuring sensitive information such as card numbers are entered and validated directly within the web context. I’d like to clarify that this change has not yet been released to Production. As part of a feature enhancement to our existing payment flow, we are transitioning to a new payment vendor, SnapPay. While trying to load the SnapPay URL embedded within an iFrame in our iOS app, I observed the following error in the Xcode console. While this error may be generic, I wanted to highlight it: 825a18 - [pageProxyID=7, webPageID=8, PID=67346] WebPageProxy::didFailLoadForFrame: frameID=24, isMainFrame=0, domain=NSURLErrorDomain, code=-999 Upon investigating, we compared the headers from our existing payment URL and SnapPay's URL, and found that SnapPay includes the following Content-Security-Policy (CSP) header: Content-Security-Policy: frame-ancestors ... "Content-Security-Policy" value="default-src 'self'; script-src 'self' https://hcaptcha.com https://.hcaptcha.com https://code.jquery.com https://www.gstatic.com https://code.jquery.com/jquery-3.3.1.min.js https://test.lightbox.cardx.com/v1/lightbox.min.js https://www.ssa.gov/accessibility/andi/ https://c.evidon.com 'unsafe-inline' 'unsafe-eval'; style-src 'self' https://hcaptcha.com https://.hcaptcha.com https://fonts.googleapis.com/css https://stage.snappayglobal.com/Resource/ https://www.ssa.gov/accessibility/andi/andi.css 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' *.googleapis.com *.gstatic.com ; connect-src 'self' https://demo1.cditechnology.com https:; form-action https://hcaptcha.com https: 'self' *.ipg-online.com secure.bluepay.com https://test.api.lightbox.cardx.com https://3ds-acs.test.modirum.com/ https://demo1.cditechnology.com/; frame-ancestors https://snappaydirect-perf.fiserv.com 'self' file: https: http; frame-src .snappayglobal.com 'self' https://hcaptcha.com https://.hcaptcha.com https: https://www.google.com .ipg-online.com secure.bluepay.com https://.cardconnect.com https://test.api.lightbox.cardx.com/ https://test.lightbox.cardx.com https://paywithcardx.com/payment/auth.cgi securepayments.cardpointe.com *.cardpointe.com https://3ds-acs.test.modirum.com/ https://www.yokohamatire.com http://uat1-txt.ad.portal.texas.gov https://uat1-txt.ad.portal.texas.gov " After multiple working sessions with the SnapPay team, we were able to confirm that when they disable CSP or remove the frame-ancestors directive, the iFrame loads successfully within our app. However, SnapPay cannot change on their CSP. To enable the iFrame to load in the iOS app, we added the following line of code: webView.configuration.preferences.setValue(true, forKey: "allowFileAccessFromFileURLs"). This resolved the issue with loading the iFrame. Note: the file being loaded is a local .html file,. Before submitting this update to the App Store, I’d like to confirm whether this usage of allowFileAccessFromFileURLs is acceptable for App Store review. I wanted to confirm that with this change is there a security concern for WKWebview?

Our IOS app is restricted to India only. The Apple review team is unable to review the whole functionality of the app because the app's API does not work outside India. Apple's review team is continuously rejecting our app. As per the RBI's guidelines, we cannot allow the API outside India. We had already asked them for the IP Addresses that need to be whitelisted but they are not providing any additional information . We are having a more than one month communication with the apple team but unable to live the app. Can you please help us with the next step, or do you have any idea about the Apple review team's IP address?

Hello, I'm writing this as I've recently been struggling with the app review process. Nearly 14 days ago, I tried to push an update for submission, as it contained an update for my app that was urgent. I have a second app that I recently developed and launched, roughly 3 days ago. However, I have not gotten any updates on the review process. I contacted support via email twice, in regards to the first app's update. The first time, I recieved a response saying Apple themselves has expedited my app. I did not request an expedited review, I simply asked why the review was taking too long. I assumed the app would be reviewed shortly after, as it was expedited, according to Apple. The second time, I emailed because there were still no updates. I recieved a similar response, saying my app is still waiting for review and the reivew should commence shortly. However, after waiting multiple hours, there are still no updates. Here is the response I got the first time. Here is the second: I want to add that both times, I did not ask for an expedited review. Additionally, I did have to cancel my submission a couple times. Once due to an error in the binary, and once due to overlooking a mistake in the naming, which I had forgotten to click "save" in the metadata (after experimenting with naming) that contained a trademarked phrase. Upon noticing this, I quickly rectified the error. Because of this, I'm wondering if there is an issue with my account that needs to be cleared, rather than just a delayed review process. If this is the case, I want to maintain that I had no intention of infringing the Review Guidlines. If anyone knows anything about this, help would be greatly appreciated. Thanks!

Hi everyone, We’ve developed an iOS app that is working perfectly across our internal testing environments including: TestFlight iOS simulators Physical iPhones and iPads within our organization However, during App Store review, the build gets marked as incomplete, and the review team reports the following issues: Issues Reported by App Review: Login error message: "device token must be string" Sign In With Apple: Reviewers are redirected back to the login screen after authentication. No error message is shown, but the user isn't logged in. Account creation: The team is unable to create a new account using the provided credentials. Everything functions correctly in TestFlight, simulators, and local builds. The issue only seems to happen in the App Review environment, making it difficult for us to reproduce. We suspect that push notification permission might not be granted or the token is not being generated in the App Review sandbox environment — leading to a null/undefined value that breaks login. The "device token must be string" message likely appears when our backend validation expects a string, but receives a different type or undefined. Also, the Apple Sign In redirect and account creation failures may be related to Keychain, token handling, or review sandbox behaviors.

Hi, My app currently offers a non-consumable in-app purchase to unlock all its features, and I would like to provide this full access for free to an organization with a few thousand Macs. Since Apple limits non-consumable in-app purchase promo codes to 1000 per app, this isn't sufficient for the organization's size. So I'm considering an alternative approach using an auto-renewable annual subscription with offer codes: Create a few thousand offer codes for an annual subscription. Users within the organization would redeem these codes. Instruct users to immediately unsubscribe after redeeming the code. The app would then check the in-app purchase receipt. If the receipt contains a transaction redeemed with an offer code, the app would treat this as a permanent unlock of all features. My concern is that repurposing an auto-renewable subscription in this manner—effectively turning it into a lifetime unlock triggered by redeeming an offer code and immediately cancelling—might violate App Store guidelines. Is using an annual subscription and offer codes this way likely to be compliant with App Store guidelines? Thank you for your guidance!

Hello, I am new application developer that has been developing several applications in the productivity and finance sections concurrently for about 1 year. One of my applications is nearly ready to be submitted to the App Store. I have received a lot of discouragement from people who have submitted apps in regards to putting submitting as a paid app, however due to all of the upfront and ongoing investment I've made, I do not wish to release my application for free initially. (I am learning how to best integrate storekit and in-app purchases and subscriptions, but I'm not ready to implement that yet) QUESTION: When releasing an app as a paid app and then converting to a FREE app with subscription later on, is there anything I need to be aware of technically or in regards to guidelines so I don't shoot myself in the foot when changing pricing? Any advice is greatly appreciated. Thank you.

Hello Developer Community and Apple Staff, Like many others I've seen posting here recently, I'm facing persistent Guideline 4.3 Spam rejections for my puzzle games. I'm hoping for guidance as I believe I've identified and corrected the initial technical cause, but I'm still facing rejection and need help understanding why. My Situation: I develop grid-based puzzle games in Unity, often using my own well-developed reusable codebase (for GridManager, Tile logic, etc.). My last successfully approved app ("Seat Em All!") used my standard workflow: New empty Unity project + import my necessary code = No 4.3 issues. The 4.3 rejections started with my next game ("Twisty Train"). My mistake: Duplicated the entire "Seat Em All!" project folder, including all .meta files/GUIDs. I now understand this likely triggered spam flags due to identical technical IDs, despite adding new mechanics. My subsequent game ("Egg Pack") unfortunately repeated this flawed copy process from "Twisty Train" and was also rejected under 4.3. Corrective Actions Taken for Latest Submission: For my most recent submission, ("Egg Factory: Sorting Puzzle" - conceptually similar to Egg Pack but built to fix the issue), I took specific, major steps to address the technical duplication: Used a new, unique Bundle ID. Used the "GUID Fixer" tool to regenerate unique GUIDs for ALL assets within the entire project folder. Used a new app name and icon. The Current Problem: Despite these steps to eliminate technical duplication and ensure unique identifiers, "Egg Factory: Sorting Puzzle" was still rejected under Guideline 4.3 Spam. Seeking Specific Feedback & Potential Causes: I'm now trying to understand what, beyond unique technical identifiers, is causing this. I design my games ("Seat Em All!", "Twisty Train", "Egg Factory") to have distinct core mechanics and themes, even if they share my Unity codebase and a visual style. Could the automated review be detecting structural similarities in my own reusable code, even with unique GUIDs, and potentially misinterpreting it as template usage (similar to issues some devs using specific game engines have reported)? Is the consistent visual art style across different themes being flagged? Is the core puzzle/sorting loop considered too similar despite mechanical differences? Request for Call: Getting generic 4.3 feedback isn't helping me resolve this. I've seen other developers mention that a direct call with the App Review team was invaluable for clarifying complex situations like this. Would it be possible to schedule a call to discuss my case? Understanding the specific reason "Egg Factory" is still flagged, despite the technical fixes, is crucial for me to move forward correctly and ensure compliance. Any insights from the community, or specific guidance/a call from Apple Staff, would be incredibly helpful. Thank you, UtkuG

Our app has been stuck in the "Waiting for Review" status for over two weeks now. We've reached out to the App Review team through the official contact form, but haven't received any update or change in the status since then. We understand that review times can vary, but this delay is longer than what we've typically experienced. We're starting to get concerned as it’s beginning to affect our timeline. Just wondering if anyone else has faced similar delays recently, or if there’s any additional step we can take to help move things forward. Any advice would be greatly appreciated. Thanks in advance!

We've been struggling for weeks to upload our app in the App Store, but we keep receiving the same rejection. Here's the exact response from Apple: "The app provides loan services but the domains listed on the app's Product Pages are still not clearly under your control or ownership. Since users may use these domains to contact you to request support, the domains used on the Product Page for loan apps must be under your control or ownership. Update the Product Page metadata in App Store Connect to only include domains that are associated with Apple Accounts registered to your developer account." The issue is that we've always listed the same domain that we used when registering our Apple Developer account. If you visit our website, the company name and address are clearly displayed in the footer. We have already provided all the evidence that all the links in the developer's account are on our domain. We also provided evidence that this domain is ours. But it did not help. We've tried asking for clarification, but we keep receiving the same generic response without any specific details. This situation is extremely stressful for us.

Our app was submitted for review on ​March 19, but it wasn’t reviewed until ​April 1, when it was rejected due to issues. We fixed them and resubmitted ​the same day (April 1), but by ​April 8, it still hadn’t entered review. We then uploaded a new binary and resubmitted, but as of ​April 14, there’s still no progress. From ​March 19 to April 14 (nearly a month), our app has only been reviewed ​once, causing significant delays to our launch timeline. We’ve contacted App Review multiple times via email and App Store Connect, but received either no response or automated replies (Case ID: ​2000009630897). Is the review team experiencing unusual circumstances? We urgently need assistance to move this forward.

Hello, my app address: https://apps.apple.com/cn/app/%E4%B8%89%E5%9B%BD%E6%88%98%E4%BA%89%E7%AD%96%E7%95%A5slg/id6741073714?ct=Tap725796 I submitted a version update request for version 1.23.1 on April 10, and submitted an accelerated review application, but it has not been reviewed yet. Today, I have updated the new version to 1.23.2, and submitted an accelerated application request, but it has not been reviewed yet. Maybe because the online version review is stricter, I also submitted a review request for the TestFlight version, which has also been stuck waiting for review. This is an online battle SLG game, which has been updating its version every week for half a year. Because the Android version has been updating steadily, the Apple version has suddenly been unable to update in the past two weeks, resulting in the unusable networking function. Currently, there are a large number of complaints from Apple players. I really don’t know if there is any suitable solution. I will try my best to cooperate as long as I can. I hope that Apple’s official reviewers can provide timely help to developers and Apple players. This is an online battle slg game, which currently has 4 independent gameplays. I learned from the server log that the reviewer did not log in to the online account I submitted, and two of the gameplays were not experienced at all. This is a game that has been developed for half a year. Some interfaces or functions may be similar to other applications. This is just a similar function. A complete game is composed of a large number of various interfaces and functions. It is completely unreasonable to conclude that it is exactly the same as other applications because of one similarity. It is like two people who are completely unrelated look alike. This is common in reality, but they are very different because of their different experiences . The same two different applications may be similar in some places, but the overall difference is huge because of the author's goals and preferences. I just hope that Apple reviewers respect the work of every developer and all users who choose to buy Apple phones to experience Apple applications. This app has been updated weekly for half a year. The link https://www.taptap.cn/app/725796?os=android basically records the development process. During the development process, a large number of players participated in the problem feedback and provided a lot of valuable suggestions, a large part of which were implemented in the game, which made this game unique. Of course, the achievements of this game will also cause jealousy among some psychopaths. They can only satisfy their personal perverted pleasure by constantly giving bad reviews, reporting faults, etc. The suggestions of such extremists are not of much reference value.

Hey everyone, I posted here a few days ago explaining that my app has been "in review" for 10 days. In the meantime, when I click on it, it says "waiting for review". I have been having very inneficient back and forth with App review Support by email. These are the emails: Today I get a review telling me my App was rejected, yet on Appstore Connect, it's still in review. I wouldn't mind a rejection, as it would mean I can fix the problems, but this hiatus is just tanking all momentum we had. It feels extremely unprofessional on their part. The system is quite opaque. It's already cost me a launch, and now all of my marketing efforts are going down the drain, and I'm losing my customer's goodwill. I'm hesitant about cancelling my submission and relaunching it. Especially if I'm in "expedited" as they say. As an indie dev, this is quite disappointing. As I said, I wouldn't mind a rejection as it would mean I could do something, but being held up because of logistics is quite worrying. Any feedback would be appreciated.

Hi everyone, I’ve been facing an issue with TestFlight external builds that I haven't encountered before, and I’d appreciate any insights. Background: I have an iOS app that was recently approved and released to the App Store. Prior to this, I’ve regularly submitted TestFlight builds (with updated version and build numbers) to both internal and external tester groups. Internal builds would appear instantly, as expected. External builds were also available almost immediately after selecting “Ready to Submit.” This was consistent for many iterations. Current Issue: After pushing the latest version to the App Store (which went through the standard review process and was approved), I prepared a new version for TestFlight testing. Here’s what happened: Uploaded a new build with a new version number and build number. It appeared instantly for internal testing as usual. When I tried adding it to the external tester group, the build got stuck in the “Waiting for Review” state. I uploaded this on Saturday night, and as of Monday noon, the status has not changed. I also cancelled that build and uploaded a fresh one with an incremented build number — still stuck in the same status. Additional Notes: The app’s ITSAppUsesNonExemptEncryption key is set to false in Info.plist. There is no missing export compliance warning on App Store Connect. The changes in the new build are minor — a few small updates, nothing significant. I tried decreasing the build number temporarily (which caused an error), then increased it again. No changes were made to permissions, app capabilities, or metadata that would typically trigger a longer review. Questions: Is this expected after an App Store release? Has anyone else experienced delays like this recently for TestFlight external builds? Is there anything I can do to expedite the review? Thanks in advance for any help!

Hello, We are posting here in hopes of getting some help or advice regarding a critical situation we’re currently facing. We submitted our iOS app last month, which was developed for an international event that officially began yesterday. This app is part of a national project with high visibility, involving government officials and ministers. However, we are stuck in the "Waiting for review" status since the initial submission, in March 21 (24 days ago). Note that we already submitted a few IOS applications in the past with the same account, and we didn't have any problems. Here is a quick summary of what we tried in the store: Initial submission: March 21, 2025 Resubmission: March 25, 2025 Last submission attempt: April 8, 2025 Expedited Review Request: accepted, but the review still hasn't started We’ve contacted Apple Support multiple times through mails and phone calls, and received confirmation that our expedited review request was approved. However, no progress has been made since then, and the app remains in “Waiting for Review” status, now 1 day past the critical launch deadline. We understand that expedited reviews are not always guaranteed, but given the urgent and national importance of this project, we are doing everything we can to try and ensure the review begins as soon as possible. If anyone from the App Review team sees this post, or if any developers have experienced a similar situation and can offer advice, we would be truly grateful. Thank you in advance for your time and support.

Recently, I have encountered this issue multiple times and have been rejected by the AppStore for review. Despite repeated modifications, I still cannot pass the review. I am very confused now. Can anyone help me specify what information I should modify or provide to meet the AppStore's review requirements? Thank you very much！ Guideline 3.2.1(viii) - Business - Other Business Model Issues - Acceptable The app provides loan services but the domains listed on the app's Product Pages are not clearly under your control or ownership. Since users may use these domains to contact you to request support, the domains used on the Product Page for loan apps must be under your control or ownership.

Hi, I have submitted my app for review since Apr 9, 2025. On Apr 10, 2025, I don't see any review so i cancel then resubmit. Today is Apr 14, it still in Waiting for Review status. Please help me look into this issue. We need to release it app. AppleID: 6744261681 Thank you.

Hi everyone, I’m an indie developer and recently published our first app on the App Store. It was an exciting milestone, but on April 4, 2025, after the app had been live for about 1–2 weeks and one update had been pushed, we received a notice from Apple stating that our app had been removed from the store and that our developer account is scheduled for termination within a month. Understandably, this was incredibly alarming—but we stayed calm, carefully read through the allegations, and tried to handle the situation with patience and professionalism. The reason given was: 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. This was cited as a violation of Section 3.2(f) of the Apple Developer Program License Agreement. We were accused of dynamically changing game content after review, but we do not have the capability to do anything like that. The game has stayed exactly as it was when submitted, and the single update we pushed included only the changes listed in the “What’s New” section. They also mentioned hidden features. While we don’t hide anything, our game does include progression-based unlocks (such as new upgrade cards or mechanics unlocked as you play). We believe this is standard for many games, and we’ve explained this in our appeal. We also addressed another possible issue—some light pop culture jokes in push notifications—which we are more than happy to remove immediately if they were deemed inappropriate. We’re not here to argue or avoid accountability. If we’ve made any mistakes, we’re more than willing to correct them. But terminating the entire account for a first-time submission, without any discussion or specific feedback, feels incredibly harsh—especially for a small team trying to break into the industry. We submitted an appeal to the App Review Board over a week ago but have not received any response or update since then. So I’m posting here in the hopes of catching someone’s attention—whether that’s Apple or anyone in the community who’s been through something similar and can advise. I know the $99 annual fee might not be a huge deal for many developers, but for someone just starting out, it represents more than money—it’s a foot in the door. I’m not looking for sympathy, just a chance to make things right, follow the rules properly, and keep building on the platform I admire. Thank you for reading, and I truly hope someone can help guide us on the next steps. Best, Veekshith Kolanupaka

In my experience, submissions are typically reviewed within a few hours, even for resubmissions after a rejection. However, my most recent submission has been "Waiting for review" for almost 24 hours now. I’m wondering why this might be happening. Could it be due to the timing—it’s the weekend before Good Friday, so perhaps there are fewer reviewers available and a higher volume of submissions? Or maybe the fact that this is a resubmission after a rejection is causing the delay? Have others noticed longer wait times during holidays or for resubmissions? I really appreciate the hard work of the review team and all Apple employees. To help ensure a smooth review process, I always try to make sure my app meets all the guidelines and include detailed release notes. Are there any other best practices I should follow to avoid delays? Thanks!