Our new app needs an essential Background Assets asset pack (hosted by Apple) to work. The app is currently failing to get through App Review because the reviewer doesn't have access to the asset pack. We submitted the asset pack together with the application for review. The asset pack is already approved. However, the error the reviewer reported indicates that their device can't find or download the asset pack. Or to be precise, on macOS (Catalyst) the model information cannot be fetched—the model is not found. iOS seems to see the model and get the information, but the download fails or never proceeds past the first 0% progress. We already had the same issue with our TestFlight beta (see this post for details). In the end, App Review let it pass through without verification because it was a known issue. This will probably not work for the main app review. We even tried switching the download policy of the asset pack to essential (was preFetch before) in the hope that the reviewer will then automatically download the pack together with the app. But this still didn't work. We can't be the only ones having this problem, right? This is completely release-blocking for us, and we already have a close deadline...

We’ve been dealing with a review issue that has become extremely frustrating, and I’d like to understand whether this is something other developers have encountered before. We received a rejection and provided App Review with an explanation and additional information showing why we believed the rejection was not valid. After that, App Review replied: “Your submission’s review will require additional time as we take this new information into account. We do not require any further information at this time.” They also explicitly said that once they completed the review, they would either contact us with any issues or approve the submission. So we waited. Then we sent several follow-up messages because there was no response. Still nothing. Eventually, we contacted Developer Support to ask why we weren't getting any update. Their response was simply: “Your app was rejected as of July 27th.” That was very confusing, because according to the App Review message, our additional information was still being reviewed and we were waiting for their final response.So now we have two completely different messages from Apple: App Review telling us that the submission is still being reviewed, and Developer Support telling us that it was already rejected. We’ve tried to communicate through App Store Connect, followed up multiple times, and contacted Support, but still don't have a clear answer about what actually happened. Has anyone experienced a similar situation where App Review stopped responding after saying that additional information was under review? How did you resolve it? Did escalating through Developer Support help, or did you eventually have to resubmit the app? Would really appreciate hearing from other developers who have dealt with something similar.

Hi, my app NovaNews has been rejected again under Guideline 5.2.3 because of its Internet radio player. It does not download, record, convert, proxy or retransmit anything. It simply lists Internet radio stations and plays their public live streams directly from the user's device. After the first rejection, I even removed my curated list of Italian radio stations, thinking that was the problem. I left only a generic Community Radio directory. It was rejected again, and the screenshot provided by App Review simply shows that list with an ordinary station (PBS FM Melbourne) playing. So I am genuinely confused: are developers now expected to provide written authorization from every single radio station included in a radio directory? What makes this even harder to understand is that I can find apps currently on the App Store offering Internet radio players and even third-party media services such as YouTube. I don't want to name or criticize other developers. I am only trying to understand why apparently similar or broader functionality is accepted while a basic radio player is rejected under 5.2.3. I have appealed the decision, but I'd really like to hear from developers of radio apps: have you encountered the same issue recently? Thanks,

ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Is not allowing my app to review.

Hi everyone, I’m looking for some clarification regarding Privacy Manifest requirements (PrivacyInfo.xcprivacy) after resolving a validation issue on my latest submission. In my previous build, I ran into an issue related to NSPrivacyTracking and NSPrivacyTrackingDomains. I updated the manifest to ensure NSPrivacyTracking is set to <true/> alongside our App Tracking Transparency (ATT) prompt, and restricted NSPrivacyTrackingDomains strictly to the required ad service endpoints (googleadservices.com, googlesyndication.com, doubleclick.net, etc.), removing any broad domains. I have just submitted the corrected build: • App Name: Girls vs Boys Tapping • Version: 1.1.2 • Build: 112 • Apple ID: 6809284204 • Status: Waiting for Review Since this is my first time submitting with the updated privacy manifest format after resolving that error, my question is: Once the build enters the review queue with these specific tracking domains and ATT configured, does App Review require any additional documentation in the review notes regarding the ad network tracking domains, or is the .xcprivacy file inside the bundle sufficient for automated validation and review? Just want to make sure everything is 100% in order so there are no unexpected hold-ups while it's in the queue. Thanks in advance for any insights!

Hi Apple Team and Developer Community, We are looking for guidance on how to best escalate / resolve an ongoing App Review issue. Our app has been going through multiple App Review cycles for nearly three months. Each time, we address the specific concern raised, provide clarification or documentation, and resubmit. However, after one issue appears to be addressed, a new or related issue is raised in the next round. This has resulted in a prolonged review cycle despite repeated responses and supporting documentation. The current issue relates to Guideline 3.2.1(viii) for an India financial-services app. We have provided detailed clarifications and supporting documents through App Review, including partner documentation, entity-structure documents, and explanations of the relevant user flows. We have also: submitted an appeal; requested expedited review; raised a Developer Support case; and requested an App Review appointment / call. The expedited review has been accepted, but we are still waiting for closure. The earliest available App Review appointment is much later, and the delay is causing material business impact. We are not looking to debate the guideline publicly or disclose confidential review materials here. We would appreciate guidance on the correct process to have the App Review team review all open issues together, or to arrange a call/escalation so that remaining concerns can be clarified in one discussion rather than through repeated review iterations. Thanks in advance for any guidance.

My app was removed and my account terminated without any notice. Apple indicated that I violated section 3.2(f) of the ADP, but I did not engage in any unlawful or misleading acts in my business practices. So I submitted an appeal to clarify the situation, but there has been no response. I also tried reaching out for help via general email, but still received no reply. Any advice on how to get a response from Apple? It seems my termination was automated, and no human has reviewed my appeal. I appreciate any help you can provide.

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. Around two weeks ago, I started getting the following error when trying to create external TestFlight builds: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Since then: I cannot create any external TestFlight tests Internal TestFlight builds appear, but cannot be downloaded (“The requested app is not available or doesn’t exist”) My apps do not progress properly through review One app got stuck in “In Review” for ~10 days; I eventually withdrew it and resubmitted it At this point, I cannot update two existing apps, and I can’t start testing a new app at all Important details: This is an individual developer account I am the Account Holder All contracts appear active and valid The issue affects multiple apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!

Hi, My macOS app, Notiz Me, received a "Guideline 2.1 - Information Needed" message on September 3, 2026. This was flagged as a new developer account with limited App Review history, and I was asked to provide additional information about the app. I replied the next day (September 4) in the Resolution Center with detailed answers to all six requested items, plus a screen recording demonstrating the app's core functionality. I also added the same information to the App Review Information Notes field, as instructed in Apple's message. It has now been over a week with no response. I sent a follow-up message today, but there has been no update in App Store Connect since my original reply on September 4. Submission ID: 1301bf30-de8f-419e-9fe1-75edd8b6884b App: Notiz Me (macOS) Bundle ID: com.prakashyuvaraj.notizme Could someone please help check the status of this submission, or surface it to the App Review team? Happy to provide any additional information needed. Thank you.

Six people. Four years. One app on the App Store since 2022 — completely free, no payments, no in-app purchases, no subscriptions. Sixteen released versions. Real users. In May 2026 Apple flagged our developer account for termination. The stated reason: "dishonest or fraudulent activity" under Section 3.2(f) and Guideline 5.6.2. That was the entire explanation. Not which app. Not which metadata. Not which action. Not which build. Nothing. We asked. Six times over three months. We offered to revert our branding, remove any feature they named, re-verify every piece of company information. We asked, plainly: tell us what we did wrong and we will fix it today. The App Review Board answered twice — the same template both times. "A pattern of manipulative or misleading behavior," followed by a generic list of things such behavior "can include, but is not limited to." Not one specific. Not once. In four months. What that looks like from our side: — Three apps pulled from the App Store overnight — Earnings frozen — App transfers disabled — Three months of "we are experiencing a higher case volume" — A final decision that repeats the original accusation word for word — A reinstatement petition filed on 27 August. Thirteen days. No response. No phone call. No human being. No specifics. No appeal beyond a web form that answers with a template. Apple's own Guideline 5.6.2 reads: "Providing verifiable information to Apple and customers is critical to customer trust." Verifiable. Apple demands verifiable information from developers, then terminates them on grounds it refuses to specify, and calls that a review process. Six people lost their work. Their families lost their income. Four years of building on a platform that can end your business overnight and owes you no explanation. If you build on the App Store, understand what you are building on. If you have been through this — reply here. I want to know how many of us there are.

Hello, We have submitted our app on August 10th, and still "Waiting for Review" for over 20 days. Can anyone help us resolve this issue?

Hello, I’m posting here to ask for guidance and to see if anyone has experienced a similar situation. More than 30 days ago, I submitted an appeal to the App Review Board after receiving a Pending Termination Notice for my Apple Developer Program account. However, I have not received any response or update since submitting the appeal. In the notice, Apple mentioned that my account was associated with “dishonest or fraudulent activity” related to app submissions. I want to clarify that I did not intentionally attempt to bypass the App Review process. The only change I made around that time was editing some app metadata (subtitle keywords) while trying to optimize my Apple Search Ads campaign. Looking back, I now understand that some of those keywords may have been interpreted as referencing content that Apple considers inappropriate for the App Store. After realizing this might have caused an issue, I immediately: Canceled the latest app submission that contained those metadata changes Explained the situation clearly in my appeal to the App Review Board Confirmed that I would avoid using similar metadata in the future Despite providing this explanation in my appeal, I have not received any reply or update for over a month, so I’m unsure about the current status of the appeal. If anyone here has gone through a similar process, could you share: How long it took to receive a response from the App Review Board? Whether it’s normal for appeals to take this long? Also, if any Apple staff happens to see this post, I would sincerely appreciate any guidance on whether my appeal is still under review or if there is anything further I should provide. Thank you very much for your time and help.

Hello everyone, I’m looking for advice from developers who have experienced a similar App Store rejection under Guideline 5.6 – Developer Code of Conduct. My app is called Al-Saqar. It is a specialized marketplace and auction platform for falconry enthusiasts. The app includes: Falcon listings and physical product sales Falcon food and accessories Real-world falcon auctions Live auction viewing and bidding Falcon farms and clinics directory Search and filtering User accounts and account deletion All products and auction items are physical goods. There are no digital goods or subscriptions being sold through the app. For auctions, users can view the auction and watch the bids. To participate, they need to complete identity verification and pay a security deposit. The deposit and final payment are handled outside the app through our support team and bank transfer because these are real-world, high-value transactions. Apple rejected the app under Guideline 5.6 with the following message: “We've identified a pattern of unusual behavior with the app that is commonly associated with fraudulent activity. Specifically, the app contains features that appear to have been intentionally hidden during the review process.” The problem is that Apple did not identify which feature, screen, account state, or behavior they believe was hidden. There are no hidden features intended to be shown only to normal users. The functionality available to users is the same functionality available during review. I have already tried to clarify this with Apple and provided additional information and a screen recording demonstrating the functionality on a real device. I have also submitted an App Review Board appeal, but I am still trying to understand what could be triggering this rejection. Another thing I noticed is that the review appears to have happened extremely quickly, which makes me wonder whether some automated detection or account/runtime behavior could be involved. I obviously cannot confirm that this is the case. I have been trying to publish this app since August 18, 2026, and I have now reached a point where I don't know what I should actually change because Apple has not identified the specific issue. Has anyone experienced this exact Guideline 5.6 rejection, especially the wording about: “features that appear to have been intentionally hidden during the review process” and successfully resolved it? If so, I would really appreciate knowing: What was actually causing the rejection? Did Apple eventually identify the specific feature or behavior? Was it related to remote configuration, server-side logic, feature flags, account states, device/region checks, dynamic content, or third-party SDKs? Did contacting Apple Support or requesting an App Review appointment help? Did you need to submit an appeal, or did a new build eventually resolve the issue? I am not looking to bypass App Review. I simply want to understand what Apple is detecting so I can fix the actual problem instead of making random changes and repeatedly submitting builds. Any experience or advice from developers who have gone through the same situation would be greatly appreciated. Thank you.

Hello App Review team, Could you help investigate a possible false-positive similarity classification across my apps, or advise which channel can examine these review events together? My concern is based on the recorded timing, the different purposes of these apps, and a previously approved bowling app whose update was rejected twice under 4.3(a), then subsequently approved. Striker: Bowling Coach and Fotij Striker is a bowling coaching app. Fotij is a color analysis and personal styling app. These were the two apps rejected together in the August events below. App Store Connect records: August 21, 2026: Striker 1.0 was approved and became Ready for Distribution. August 28 at 00:23: Striker’s 1.01 update and Fotij 0.1.0 both entered In Review and were marked Rejected within that same displayed minute. August 28 at 18:22: Both apps again entered In Review and were marked Rejected within the same displayed minute. Both rejection messages for each app cited Guideline 4.3(a). Striker 1.01 was submitted again. On September 5, it entered review at 14:16 and became Ready for Distribution at 14:19. The completed submission shows 1.01, build 4, Approved. The later approval was for the same marketing version, 1.01. Whether the binary or metadata differed across individual attempts should be checked against Apple’s submission records. Camera1X: a separate, later occurrence of the same pattern Camera1X is a native photography app combining depth capture, interactive 2.5D parallax and 3D Motion export, guided Moon/Stars/Moon + Landscape capture, and private on-device spatial reconstruction. Its review history shows: August 6: In Review at 09:21, Rejected at 11:25 — approximately two hours. September 7: In Review at 17:25, Rejected at 22:47 — approximately five hours. This review returned a specific Guideline 2.1(b) purchase issue, which we addressed. September 9: In Review at 01:34, Rejected under 4.3(a) at 01:34. Fotij also entered In Review and was rejected under 4.3(a) at 01:34 that day. The two replies already sent for Camera1X In my first reply, I disputed the 4.3(a) finding and explained Camera1X’s functional capture and processing workflows. I raised the concern that similarity screening might be incorrectly grouping independent apps. I requested a manual review and identification of the specific binary components, assets, metadata, or app concept behind the finding, including a comparison app where possible. In my second reply, I clarified that Camera1X had previously undergone two reviews lasting hours, while the latest rapid rejection coincided with separate apps receiving the same finding. I again requested an individual assessment of each app’s actual functionality and a concrete explanation of the alleged overlap. I also explained that I would resubmit Camera1X first and wait for its review to conclude before resubmitting the other new apps. Camera1X 1.0.0 (6) is currently Waiting for Review. All times above are displayed in App Store Connect in UTC+03:00. The history has minute precision, so matching timestamps alone do not prove that a decision was automated. However, the repeated timing across apps with different purposes, together with Striker’s subsequent approval, raises a concern that I would appreciate Apple investigating. Could App Review staff: Compare these events and check whether an erroneous similarity association could explain the pattern? Identify the concrete overlap behind the 4.3(a) findings so I can address a specific concern? Advise how to provide the full review histories, submission IDs, and both Camera1X replies privately, and which support or appeal channel should track the investigation? Thank you, Aziz Saba

Hello, Our first App Store release, 2ndBook 1.0.0 (build 251), has remained in “Waiting for Review” since August 29, 2026 and has never moved to “In Review”. App: 2ndBook Version: 1.0.0 Build: 251 Platform: iOS / iPadOS Bundle ID: kz.stybaye.secondbook Submitted: August 29, 2026 Current status: Waiting for Review The binary has been successfully processed and there are no outstanding actions or messages shown in App Store Connect. We have already contacted Apple Developer Support regarding the review status and an official support case has been opened. Could someone from the Apple App Review team please verify whether this submission is correctly present in the review queue, or whether it may be affected by an internal routing or processing issue? We do not want to withdraw and resubmit the application, because we would prefer to preserve the existing submission and its current queue position. Please let us know if any additional information or action is required from our side. Thank you.

Hello, our app Rezzy Baby (App ID 6807484857, build 1.0.0 (4)) was submitted on Sept 2 and received a Guideline 2.1 Information Needed request on Sept 3. We answered all six questions the same day at 19:43, attached a 5-minute screen recording, and put the same details in the App Review Information notes. Demo accounts and the backend have been online the whole time. There has been no reply since Sept 3, and the status still shows Rejected with Resubmit disabled. We sent a follow-up in the message thread today. Is there anything else App Review needs from us to continue? Thank you.

I'm an iOS developer in India, not yet enrolled, and I want to confirm my distribution architecture before I incorporate and pick an account type. What I'm building: patient-facing appointment and clinic-management apps for independent single-doctor clinics. One shared codebase; branding, clinic details, and backend configuration differ per clinic. The clinics will not enrol in their own Apple Developer Program accounts. I would register a company and enrol as an Organization, that company provides the software platform, while the medical services are provided by the individual clinics. Under 4.2.6 and 4.3(a), is a separately branded app per clinic viable from a single Organization account? My reading is no, and that the aggregated or "picker" model, one app where patients select their clinic, is the intended path. Is that correct? Under 5.1.1(ix), for that aggregated app, is my company an acceptable seller given that the medical services themselves are delivered by the clinics? Or does Apple expect each clinic to be the seller? If separately branded per-clinic apps are only possible when each clinic enrols in its own account, can I be added to their teams and submit on their behalf, or must the clinic itself submit? Are there additional review requirements for apps tied to medical practices, clinic licensure documentation, proof of authorisation to publish on their behalf, or a regulated medical device declaration, where the app only handles appointments, records, and clinic administration rather than diagnosis or measurement? Developer Support case 20000147392668 (they directed me here for the guideline questions).

Hello App Review Team, I'm writing to request an urgent status update and expedited review for our app, BlockP (App ID: 6705133649). Our most recent update has been in review for over 13 days, well beyond Apple's typical review window of 24–48 hours (and even beyond the outer bound of 7 days we've referenced in prior communications). This delay is materially affecting our business: A critical bug fix /feature our users are waiting on is stuck in this build users are affected by the issue this update resolves Details: App name: BlockP App ID: 6705133649 Build/version currently in review: 3.0.2 Date submitted: 2 sep 2026 Days in review: 13+ Could you please: Confirm the current status of this build and whether it requires any action from us Advise whether anything in this submission is causing an extended manual review Expedite this review given the above impact We're happy to provide any additional information needed. Thank you for your help resolving this quickly. Best regards,

Hello, Apple! I accidentally uploaded a version with a critical bug. Apple, please accept my new version—it’s urgent. Thank you very much.

We are a team of developers, and our company is involved in creating mobile applications. Recently, our developer account was terminated, and all active apps were removed from the App Store. The email mentioned that our app violates section 3.2(f) of the Apple Developer Program License Agreement. We've been trying to identify the issue since then, but we're not involved in any fraudulent activities. Our company is facing a critical situation as it is essential for us to have the apps back on the App Store as soon as possible. We are unsure of how to proceed and would greatly appreciate any assistance or guidance. Thanks. Our app ID com.seriktes.kz App name Seriktes