Hello, respected Apple Developer Forums community. SKU: com.apatura.safenet Apple ID: 6762392582 I am writing here because for almost a month we have not been able to find a solution to the situation with publishing our app, and I sincerely hope to get advice from other developers or Apple representatives. We are developing a VPN service. Initially, at an early stage, we tried to submit the app to the App Store from an individual Apple Developer account. Later, we understood that for this type of service we should use an organization account. Over time, the old Xcode project was lost. Because of that, we created a new project with the same name and similar visual materials, and submitted the app from the organization account. After that, the app was rejected under Guideline 4.3(a) — Design: Spam. The App Review message says that the app shares a similar binary, metadata, and/or concept with apps submitted to the App Store by other developers. We assume that the system may have linked the current submission to our previous submission from the individual account. It was in fact our own project, not an attempt to create a duplicate. We already explained this to the App Review Team in App Store Connect and provided information about the previous submission. We were even able to completely remove that app from App Store Connect under the individual account. We also explained that the current submission is being made from the organization account. After that, App Review requested additional information about the VPN functionality: what data the app collects, why it is used, and whether it is shared with third parties. We answered this in detail. However, after that we received the same rejection again under Guideline 4.3(a) — Design: Spam, without any additional explanation of what exactly we need to fix. We tried once again to explain that this is not spam and not a duplicate of someone else’s app. We also removed the old app record from the individual account so that it could no longer create a conflict or be detected as a possible duplicate. Now we are in a very difficult situation. We are not trying to bypass the rules. We are not publishing a network of identical apps. We are not using someone else’s template, and we are not trying to clutter the App Store. This is one real VPN service that we want to publish on behalf of the organization that operates it. It is very difficult when you wait several weeks for review, answer questions in detail, explain the situation, but then receive the same generic response again without understanding what exactly is wrong and what specifically needs to be done. We truly want to resolve this situation correctly, without conflict and without violating the rules. We just need a clear path forward. Apple Review Team, please read our thread in App Store Connect before replying with the same response again without real attention to the issue. I would be very grateful for any help, advice, or experience from developers who have faced a similar situation. With each new review, we wait 7–10 days and then receive the same generic replies without any real engagement. Thank you.

I want to share how I truly feel about this situation. I have spent years building every single app on my account before publishing anything on the App Store. Each one represents months of work, testing, and genuine effort to create something valuable for users. I am proud of what I built and I stand behind every app I have ever submitted. I honestly do not believe I deserve this decision. I have never intentionally violated any guideline. I have never tried to deceive Apple or users. I have always engaged with the review process in good faith, even when it was difficult and took months. The notice itself states that automation may have been used as part of the review process. I strongly believe this was an automated mistake. A human reviewer who looks carefully at my submission history and my apps will not find evidence of concept switching or hidden features; because there is none. I am a student in France. This account is how I support myself. Losing it overnight, after years of work, without a proper human review, is devastating. I am not asking for special treatment. I am asking for a fair human review of my case before a final decision is made. Thank you for reading this.

I am unable to submit any app for review. Every attempt to add a build to an App Store version results in a 409 error, both through the App Store Connect website and directly through the App Store Connect REST API. Affected accounts: Account 1: My personal Apple Developer account Account 2: A company-owned Apple Developer account where I have Admin access Both accounts are completely separate — different legal entities, different enrollments — but exhibit the exact same behavior simultaneously. API errors observed When calling PATCH /v1/appStoreVersions/{id}/relationships/build: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "The specified pre-release build could not be added." When calling POST /v1/appStoreVersions to create a new version: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "You cannot create a new version of the App in the current state." What I have verified All builds are processingState: VALID and not expired usesNonExemptEncryption: false is set on all builds No build is already attached to another version Build version string matches the App Store version (1.1.0) App bundle ID matches the build bundle ID Localization, review contact details, and keywords are all filled in Banking info in Agreements, Tax, and Banking was recently updated on both accounts Issue persists on both the website and via the REST API, ruling out a browser/cache issue Question Has anyone seen 409 errors affecting two completely separate developer accounts simultaneously? Could there be a platform-level issue with App Store Connect that is not reflected on the System Status page? I opened a support ticket 1 week ago but I only got a reply today and it's just asking for more details.

This is my first time submitting an app for review. I'm unable to submit my iOS app for review due to a persistent 409 error when trying to attach a build to my App Store version record. This has been happening across multiple builds and version strings. { "errors": [{ "id": "80550434-590c-48c6-b2d3-5bd3b038539b", "status": "409", "code": "ENTITY_ERROR.RELATIONSHIP.INVALID", "title": "The provided entity includes a relationship with an invalid value", "detail": "The specified pre-release build could not be added.", "source": { "pointer": "/data/relationships/build" } }] } What I've tried: • Submitted build 34 (version 1.0) — same 409 error • Incremented to build 35, version 1.0.1 — same 409 error • Removed the build from the version page and re-added it — same error Environment: • Xcode 16 • iOS deployment target: 17.0 • Builds processed successfully in TestFlight (status: Ready to Submit) • Version record ID: 198605a5​-2671​-44d6​-bacb​-04157088319d Question: Has anyone encountered this? Is the version record itself corrupted/stuck? The builds show as valid in TestFlight but cannot be attached to the App Store version.

My app ActLike AI – Face Swap Video (Apple ID: 6761327996, Bundle ID: com.LCDMediaGames.ActLike-AI) has been stuck in “Waiting for Review” for almost two weeks. Normally, my app submissions move from “Waiting for Review” to “In Review” within 2–3 days. However, this submission has not started review yet. I have already tried the following: Contacted Apple Developer Support Called support Submitted an expedited review request Removed and resubmitted the build Unfortunately, the app is still stuck in “Waiting for Review”. This delay is affecting my release schedule and causing unnecessary backend/infrastructure costs because the app uses AI video generation services. Could someone from Apple please check whether this submission is blocked, delayed, or requires any action from my side? Any help would be appreciated.

My app SoulPal: AI Social Media (Apple ID: 6765955053) has been stuck in review since Friday. This is my second submission after addressing all rejection feedback immediately. I have submitted a Contact Us request but received no response. Every day without a resolution is adding unnecessary infrastructure costs. Any help would be appreciated.

Hello, My app Wecheerup 360 Booth (App ID: 676214516, bundle ID: com.wecheerup.wecheerup360booth.ios) has been stuck in the App Review process for longer than expected. Version 1.0.3 was submitted on April 13, 2026 and has been in “In Review” status for over 15 days. There are no messages in the Resolution Center and all metadata appears to be complete on my side.

To the Apple Review and Developer Support Teams, I am writing to request guidance and assistance regarding a persistent rejection my React Native application is facing under Guideline 2.1 - Performance (In-App Purchases). My app has been rejected multiple times with the following specific note: "The In-App Purchase products in the app still exhibited one or more bugs which create a poor user experience. Specifically, the subscription screen failed to load any subscription plans. Review the details and resources below to troubleshoot this issue." The screenshot provided by the review team shows a completely black screen where our paywall options are intended to populate, indicating that the product array is returning completely empty during the review process. The Dilemma: We are completely unable to reproduce this behavior on our end. Everything functions flawlessly within our TestFlight builds across multiple physical test devices and various sandbox tester accounts. On TestFlight, the paywall renders instantly, local pricing fetches immediately via SKProductsRequest, and test transactions process without a single error. Our Current Implementation & Verification: Product Status: All subscription products are explicitly marked as "Waiting for Review" in App Store Connect with one In-App product Rejected for not being attached with a bin but I've since submitted the app once again. All the subscriptions and the in-app product have been actively attached to this specific app submission version. Agreements: The Paid Apps Agreement is active, signed, and fully up to date within our Agreements, Tax, and Banking configurations. Identifiers: We have strictly verified that the hardcoded product identifiers in our React Native codebase match the App Store Connect product IDs exactly. Because this error only occurs within the App Review environment and never in TestFlight or local sandboxes, we are at a loss for how to debug or resolve this issue. Could the App Review team or the Developer Support technical team please clarify if there is a known environment mismatch, storefront routing discrepancy, or specific network configuration (such as IPv6 handling in the review sandbox) that would cause production-ready StoreKit products to return an empty array exclusively to the reviewer? Any direct guidance, logs, or steps on how we can successfully surface our plans to your review team would be deeply appreciated. Review Environment Submission ID: 5a35279c-1621-4972-b6c6-7c1fb202b2f0 Review date: May 20, 2026 Review Device: iPad Air 11-inch (M3) Version reviewed: 1.0.2 (8) Thank you for your time and assistance.

Dear Apple App Review Team, I hope you are doing well. I am writing to respectfully request assistance regarding my app review status for the following application: App Name: Lang-Talk : Language Lessons App ID: 6761159353 The app was submitted to App Store Connect on March 27, 2026, and it is still showing “Waiting for Review” after more than two months. I previously contacted Apple Developer Support regarding this issue under: Case ID: 102863904030 I received responses on April 15 and April 21 stating that the app was still in the queue and that there was nothing I could do to speed up the process. However, since then, there has been no progress, no review activity, and no additional communication regarding my submission. Because of the unusually long delay, I also posted a question on the Apple Developer Forums to seek guidance from other developers. In my forum post, I explained that: The app has remained in “Waiting for Review” since March 27, 2026 No rejection or feedback has ever been received This is the app’s first submission Many other apps and updates submitted after my app have already been reviewed and released Several developers mentioned that this waiting period is far longer than normal App Store review timelines, which increased my concern that there may be an issue preventing the review process from starting properly. I also submitted an expedite review request, but unfortunately there has been no change in the status. I completely understand that review times may vary depending on internal workload and review requirements. However, after waiting for more than two months without any feedback or status change, I kindly request that the App Review Team please investigate whether there is any hidden issue, account-related problem, or technical reason causing this delay. If any additional information or action is required from my side, I would be happy to provide it immediately. This project is very important to me, and the prolonged uncertainty has become extremely stressful. I would sincerely appreciate any clarification, assistance, or escalation that could help move the review process forward. Thank you very much for your time and support. Kind regards, Sameen Zaka

Hi, My App(6705133649) is in review for a month with no status change. I tired calling the developer team, emailed them and expedited the app review process last week. But no change. I am not sure, what else am i supposed to do. Please help.

Hello everyone, I would like to ask whether other developers are currently experiencing unusually long App Review delays for new apps. Here is the timeline for my app (Apple ID: 6759361892): Build 1 — Feb 19, 2026: Initial build submitted Feb 21, 2026: Rejected because ads were not working properly Build 2 — Feb 23, 2026: Updated build submitted Build 3 — Feb 26, 2026: Another updated build submitted Mar 11–18, 2026: Status remained “Waiting for Review” and never entered the “In Review” stage Mar 18, 2026: Submission cancelled and resubmitted Current status: Still “Waiting for Review” During this period, I have already tried several ways to resolve the issue: Contacted Apple Developer Support multiple times Submitted an expedited review request Sent several follow-up emails regarding the delay Contacted Apple Support and asked them to leave messages for the App Review team Each time, I was told that the situation would be checked or that the review would “begin shortly.” I have now received that same response multiple times, including after my expedited review request was accepted, but there has still been no visible progress or transition into active review. While browsing the Developer Forums, I also noticed that several recent posts seem to describe similar situations, especially involving new app submissions remaining stuck in “Waiting for Review.” So I would like to ask: Are other developers currently experiencing similar delays? Has anyone recently seen their app finally move from “Waiting for Review” to “In Review” after a very long delay? Could this possibly be related to a broader App Review queue slowdown? I’m mainly trying to understand whether this is an isolated issue or something other developers are also currently facing. Any recent experiences or information would be greatly appreciated. Thank you.

Dear App Review Team, I am writing to follow up again regarding our app review, which has now been pending for over 20 days. App ID: 6705133649 Status: Waiting for Review since April 30, 2026 Despite previous communication indicating that the issue was being investigated and that we would be contacted via App Store Connect, we have still not received any update or outreach. To summarize: April 30 – Submitted for review May 5 – Apple responded that the issue is under investigation Multiple follow-ups since then Today – Over 20 days with no progress, no communication This ongoing delay is significantly impacting our users and business operations. Given that our app reviews were previously completed within 24–48 hours, and considering the extended delay in our last submission as well, we are concerned that there may be an underlying issue affecting our account or app. We kindly request: Immediate escalation to a senior App Review team member A clear explanation for the delay Confirmation if any action is required from our side An estimated timeline for resolution We are fully available to provide any additional information, demo credentials, or clarification needed, and will respond promptly to any requests. We respectfully request that this matter be treated as urgent. Thank you for your attention. Best regards, Bishwajit

My app has been stuck in “Processing for Distribution” for several days. The version was approved, but it never fully completed the distribution process. In App Store Connect, I cannot create a new version because the “+” button is missing. I also cannot submit a new build, update metadata, or cancel the current process. The release pipeline is completely blocked on my side. I contacted Apple Developer Support, and the issue has been escalated to the engineering team under an internal engineering ticket. However, I am still waiting and there is no action available to me in App Store Connect. Has anyone experienced this exact issue before? If so, how long did it take Apple engineering to reset or unblock the app version state?

Hello, I'm posting again — and unfortunately, I already know how this thread is going to go. My app (ID: 6756186616) has now been stuck in "In Review" for 80 days. To save everyone time, here is the reply I expect to receive within a day or two, copy-pasted from the response on my last thread: "Thank you for your post. We're investigating and The App Review team will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us." Nothing actually happened after that reply last time. No follow-up in App Store Connect. No further communication. Just silence. When I escalated to Developer Support (case #20000111565861), I was told explicitly that Developer Support has no way to reach the App Review team and no authority to intervene on submissions stuck in review. So Developer Support points back to App Review, and the standard forum reply points back to "contact us" — which loops back to Developer Support. This is a closed loop that doesn't actually resolve anything for an independent developer. Concrete questions: Is there any real escalation path that doesn't end in an automated reply? Why has a submission been "In Review" for 80 days with zero communication? What should a solo developer do when both Developer Support and the forum response are dead ends? I'm not asking for special treatment. I'm asking for the review to actually move — in either direction. A rejection with feedback would be infinitely more useful than 80 days of silence. Thank you.

Hi all, We are developing an iOS app that includes private user-to-user chats, commercial offer details with monetary value, and customer identification data. In line with OWASP MASVS-PLATFORM-3 requirements regarding unintentional sensitive data exposure, we need to protect these specific screens from screenshots and screen recording. We have carefully reviewed the relevant App Review Guidelines (2.5.1 on public APIs, 2.5.2 on self-contained bundles, 5.1.1 on privacy) and the related Human Interface Guidelines. From this analysis we have observed the following: iOS does not expose a public API to globally disable screen capture (no direct equivalent of Android's FLAG_SECURE). The SwiftUI .privacySensitive() modifier is effective for Lock Screen widgets and Always-On Display, but it does not appear to prevent screenshots or screen recording of an app's main UI while in the foreground. A number of widely distributed App Store apps (banking, authenticator, secure messaging) implement some form of screenshot protection on sensitive screens. Several established open-source libraries leverage the system behavior of UITextField with isSecureTextEntry as a wrapping container for arbitrary views, in order to achieve pixel-level protection for sensitive content. We would appreciate clarification on the following points: For privacy-driven protection of sensitive screens (private chats, customer data, monetized offers), is there an officially recommended approach we may have missed? Are there public APIs intended specifically for this use case beyond .privacySensitive()? Is the practice of leveraging UITextField with isSecureTextEntry as a wrapping container for arbitrary views considered an acceptable use of public APIs under Guideline 2.5.1, or does it carry App Review risk? Are there official recommendations or documentation for apps handling sensitive personal data that wish to align with industry standards such as OWASP MASVS-PLATFORM-3 for screenshot and screen recording leakage prevention? The intended use is strictly limited to a small number of screens marked as containing sensitive data (private messages, deal details, customer information). The protection would be selective and clearly communicated to the user via in-app messaging, not global to the app. Thanks in advance for any clarification, including pointers to existing documentation or threads we may have missed. Deployment target: iOS 15+

Dear forum, I would love your help with this issue or if anyone ever experienced this. I'm working on an app. weeks and weeks of work and dedication, testing endlessly with users, perfecting my app, just to get rejected for - "The usefulness of the app is limited by the minimal functionality". it's the 2nd time it happens. insulting it is, i'm trying to put my feelings aside and solve the problem. apple reviewer's are using IPad to check my Iphone only apps, claiming their not useful, non Hebrew speakers (app is in Hebrew) are checking my app and telling me it's not useful without even understanding it's purpose. when i've uploaded the app apple reviewer responded after less then a minute, not even enough time to read all the materials I've uploaded for the app or wating for it to do it's thing (daily updates), no question was asked or a discussion was made, just one insulting line. i'm super frustrated, i've paid for the developer program just to get the most horrible service. Did anyone deal with that? solved it? have any ideas? I would love your help. Thanks :) Or

Hello App Review Team, I'd like to ask for guidance on an update that has been stuck in "Waiting for Review" longer than expected. SUBMISSION DETAILS App name: RhumArrangé App ID: 6767041700 Bundle ID: com.maximesaltet.rhumarrange Version: 1.2 (Build 8) Platform: iOS Submitted: 2026-05-14 Current status: Waiting for Review (5 days, as of 2026-05-19) Submission ID: 5d69e9ee-cb48-4218-9404-c171a252a5d5 Version ID: cc12db07-3303-49c9-b22e-0cfd73fad082 CONTEXT Previous versions (1.0 and 1.1) were reviewed and approved within 24–48 hours. Version 1.2 contains critical bug fixes for users already running the app in production (no new functionality, no policy-relevant changes). An Expedited Review request was filed but no action has been taken. App account is in good standing, all agreements are accepted. No messages in Resolution Center, no Missing Information state, no metadata rejection — the submission appears to simply not be picked up from the queue. WHAT I'M ASKING Could someone from App Review verify whether this submission is routed normally, or whether it is technically stuck in the queue? I am not asking for special treatment — I just want to confirm there is no backend issue or hidden flag preventing the review from starting, so that the bug fixes can reach the existing user base. Thank you for your time and help.

Hello Apple Developer Relations / App Review Team, Our first app release has been pending review significantly longer than expected, and we urgently need assistance. We had a coordinated marketing launch scheduled yesterday based on the standard review timelines communicated in App Store Connect. The delay is now impacting launch commitments, marketing campaigns, and user onboarding plans. Current status: First app submission Build status: waiting for review No messages or requests received in Resolution Center App is fully tested and production ready We respectfully request assistance or escalation for an expedited review if possible. We understand review times can vary, but we would sincerely appreciate any help or visibility into the current delay. App name: LiveVibe App ID: 6767975462 Thank you very much for your time and support.

Hello, Our app VIOO has been in "In Review" status for 15 days as of today (May 19, 2026), with no communication from the App Review team. Submission details: App name: VIOO Version: 1.0.0 (build 14) Bundle ID: com.vioo.klient Submission ID: eac3a31c-f8cc-47f2-afea-f41e00df3079 Date submitted: May 4, 2026 at 22:38 CEST Team: EcoMotionDrive Sp. z o.o. This is our initial submission (version 1.0). There are no messages in App Review or Resolution Center. We have not been contacted by a reviewer. We are preparing a public launch of our ride-hailing service in Białystok, Poland, scheduled for May 2026. The extended review period is blocking our launch coordination across iOS, Android, marketing, and B2B contracts. I have just submitted an expedited review request through the official form. Posting here in parallel as recommended by other developers experiencing similar delays. Any guidance or escalation assistance would be greatly appreciated. Thank you, Kamil Laskowski CEO, EcoMotionDrive Sp. z o.o.

My app has been stuck in “Waiting for Review” for a very long time and I’m honestly getting really frustrated. I already fixed all previous issues and submitted everything properly, but there has been no update at all. This delay is seriously affecting my launch plans and business operations. I understand reviews can take time, but the waiting period feels unusually long compared to my previous submissions. Has anyone else experienced this recently? Is there anything I can do to speed up the review process or get an update from Apple? I’d really appreciate any advice or shared experiences. Thank you.