App Review

RSS for tag

App review is the process of evaluating apps and app updates submitted to the App Store to ensure they are reliable, perform as expected, and follow Apple guidelines.

Posts under App Review tag

200 Posts

Post

Replies

Boosts

Views

Activity

Developer account terminated under ADP 3.2(f) — Kalvero, App ID 6789877937
Hello, Fibo Business Limited’s Apple Developer Program membership was terminated under Section 3.2(f), citing unspecified indications of fraudulent conduct. App name: Kalvero App ID: 6789877937 Bundle ID: com.fibobusiness.kalvero Support case: 20000117968758 Kalvero is an original physical-goods shopping app developed and operated by our company. We have not manipulated ratings or rankings, hidden features, switched the app’s concept after review, offered fraudulent subscriptions, or attempted to evade App Review. The app uses Shopify checkout for physical goods and does not sell digital subscriptions. The dedicated review credentials only facilitate authentication; reviewers and ordinary users receive the same features, catalog, prices, and production backend. We have submitted a formal reinstatement request, but the termination notice did not identify a specific action, build, date, or account association. We understand that account-specific decisions cannot be resolved publicly. Could Apple Staff please confirm that our app submission and support case can be located, and advise whether any additional information is required through the official support channel? Thank you.
0
0
198
4w
Supported architecture and organization requirement for an on-device iOS domain blocker
I am planning an iOS security and content-blocking app for unmanaged consumer iPhones. The app would not provide a traditional VPN service. It would not offer: Remote VPN servers Geographic location switching Access to a private corporate network IP-address masking as a service Anonymous browsing Instead, the app would allow the user to: View destination domains contacted by the device Classify destinations such as trackers, advertising, analytics, or potentially malicious domains Manually block selected domains Keep connection history and filtering decisions on the device I understand that NEFilterDataProvider and NEFilterControlProvider are the APIs intended for network content filtering. However, according to TN3134, these providers are not generally deployable for an unmanaged adult consumer iPhone. I also understand that TN3120 says NEPacketTunnelProvider should not be used as a general-purpose local content filter. This appears to leave a gap for an unmanaged consumer security app whose core feature is user-controlled, system-wide domain blocking. I am considering whether NETunnelProviderManager with an NEPacketTunnelProvider could support the feature, but I do not want to use the packet-tunnel API outside its supported purpose. My questions are: Is there currently a supported Network Extension architecture for system-wide, user-controlled domain blocking on an unmanaged adult consumer iPhone? Can an app with this purpose use NEPacketTunnelProvider, or would that necessarily be considered the unsupported general-purpose filtering use described in TN3120? If such an architecture is supported, could an app with this purpose be treated as an approved security or content-blocking provider under Guideline 5.4 rather than as an app offering a traditional VPN service? App Review Guideline 5.4 states that apps offering VPN services must be submitted by developers enrolled as organizations. It also states that parental-control, content-blocking, and security apps from approved providers may use NEVPNManager. For an app that does not provide a remote VPN service but uses Apple’s VPN configuration infrastructure only for local security and user-controlled blocking, must the developer still enroll as an organization, or may an individual Apple Developer Program member submit it?
1
0
535
4w
Guideline 4.3(a) - Design - Spam
Dear Apple Review Team & Develpers! Could anyone clarify why Apple Reviewers, when rejecting the app under Guideline 4.3(a) - Design - Spam, do not provide any specific details? Each time my app is rejected, I receive a generic, automated response. In contrast, I provide detailed information and request clarification on the exact reasons for the rejection- specifically, what aspects of the app do not meet Apple's requirements. However, the responses I receive are always the same standard message without any useful details. Am I correct in understanding that the review process is entirely automated, with no human evaluation, resulting in repetitive, unhelpful replies? I would appreciate a more detailed response that can genuinely help me address the issue and ensure my app complies with Apple's guidelines. Here is their standard generic response to any my reply where I provide details and ask questions, but Apple Reviewer answer alsway with the same text: Guideline 4.3(a) - Design - Spam This app duplicates the content and functionality of other apps on the App Store, which is considered a form of spam. Specifically, this app appears to be identical to apps already on the App Store from other developers. Apps that duplicate content or functionality create clutter, diminish the overall experience for the end user, and reduce the ability of developers to market their apps. Next Steps It would be appropriate to revise your app to provide a unique experience or submit a new app that does not duplicate the content and functionality of other apps on the App Store. Resources Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third party Submitting several similar apps across multiple accounts Learn more about our requirements to prevent spam in App Review Guideline 4.3(a). Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Provide feedback on this message and your review experience by completing a short survey. Review Environment Submission ID: c4a62f43-b02a-40f0-b763-e00fcc996512 Review date: March 04, 2025 Version reviewed: 11.4.1202
1
0
1k
4w
Does expedited review carry over to a build resubmitted after rejection?
Does expedited review status carry over to a build resubmitted after a rejection? As I understood the expedited terms it does, but my resubmission has now been in Waiting for Review for three days. App: Hibi Calendar: Daily Journal Apple ID: 6762520622 Submission ID: ab5ae098-30c3-4185-a723-5f7901980dfa Timeline: Mid-July: submitted v3.0, a major update (first iPad build, Apple Pencil, a day-page customization layer). Sat in Waiting for Review over a week. Jul 20: requested expedited review, citing a live marketing campaign. Granted. Jul 21, 1:47 PM: rejected on one issue, Guideline 5.1.1. A pre-permission priming screen used the button label "Grant"; the reviewer asked for neutral wording like "Continue." Build 3.0 (35). Jul 21, 2:54 PM: uploaded build 3.0 (36) with the wording fixed, about an hour later. Today, Jul 24: still Waiting for Review. Roughly three days on the new build, two weeks since the original submission. Two things I got wrong(?), up front: The rejection included the Bug Fix Submissions offer (reply to the thread, keep the current submission). I declined it and uploaded a new binary instead. Believing I was still in the expedited queue, I filed a second expedited request two days after resubmitting. It shows as granted, but nothing moved. I know repeat requests are discouraged. I've also emailed App Review with no reply for over a week, and I haven't cancelled the submission - I don't want to reset the clock over a one-word fix that's already in the binary. My questions: did uploading a new binary rather than replying to the rejection thread drop me out of the expedited queue? Anything actionable on my end, or is the only thing I can do is wait?
0
0
137
Jul ’26
Title: Build stuck in "Waiting for Review" after resubmit — usually under 24h
Hello App Review team, My app (App ID: 6745896828) was rejected on Friday, July 17. I addressed the points raised and resubmitted the same day. Since then, the build has stayed in "Waiting for Review" with no update or response. This is highly unusual for our account: I have shipped regular updates for over a year, and every single review has been completed within 24 hours. Something appears to be stuck on this specific submission. This is a major version that our partner venues are actively waiting on for a business-critical feature (in-app reservations), so the delay has a direct impact on us. Could the App Review team please look into why this submission is stalled? Case ID: [102945425814] Thank you.
3
0
397
Jul ’26
Extended App Review Delay After Resolving Guideline 2.1 Issue – Looking for Guidance
Hi everyone, I'm looking for advice regarding an unusually long App Review process. Our app was initially submitted on July 7, 2026. During the review, Apple rejected the app under Guideline 2.1 – Information Needed because the demo account was not available due to a backend deployment ("User not found"). We immediately resolved the issue by creating and verifying the demo account, replied to the App Review team with the working credentials, and requested an expedited review. However, after providing the updated credentials, our app has remained in the review queue for several days without any further updates. We have also contacted Apple Developer Support and followed up multiple times through the App Review thread, but we have not yet received any information about the current status or whether there are any remaining blockers. This is our first App Store release, and the continued delay is affecting our planned public launch, business commitments, and customer onboarding. Has anyone experienced a similar situation after resolving a Guideline 2.1 issue? Is there any additional action we can take to help move the review forward, or is waiting the only option at this stage? Any guidance or suggestions from the community or Apple engineers would be greatly appreciated. Thank you!
0
0
118
Jul ’26
Explanation of App Review Following Successful Appeal under Clause 5.6
Dear App Review Team, First, I must admit my mistake and sincerely apologize for wasting your time. After my app was previously rejected under Guideline 5.6, I filed an appeal, which was subsequently approved. You instructed me to submit a new binary for review. Due to an error on my part, I submitted a new version and removed the previous submission record; consequently, the new submission was not linked to the ID associated with the approved appeal. I am writing today to provide the ID for my new submission: 0760b84f-00b6-4c77-a1a3-ab9040143c06 The submission ID associated with the approved appeal was: fb5b0474-3ed0-4a38-82c8-3e7553743d1f My App Apple ID : 6764726742
0
0
271
Jul ’26
ITMS-90111 vs ITMS-91065 catch-22: current-SDK third-party framework rebuild loses Apple SDK signature
We're hitting a submission deadlock with a Capacitor-based iOS app that I suspect will affect any app using Capacitor/Cordova (or similar frameworks distributed as prebuilt binaries) once Xcode 27 ships. Setup: App built with the current Xcode, targeting the current SDK. Embeds Capacitor.framework and Cordova.framework (via ionic-team/capacitor-swift-pm). The loop: Using Ionic's latest official release: these prebuilt frameworks are still built against an older Xcode/iOS SDK. App Store Connect rejects the upload with ITMS-90111 (stale SDK), even though the app's own target and every other embedded framework are current. To fix that, we rebuilt Capacitor.framework/Cordova.framework from Capacitor's open-source iOS source (MIT-licensed, same version as the official release) using the current Xcode — confirmed via archive that every framework now reports the current SDK. That upload is then rejected with ITMS-91065 (missing signature) — the rebuilt frameworks lack an Apple SDK signature that (as far as we can tell) only Ionic's own build pipeline can produce. So: official release → current-SDK check fails. Self-rebuilt release → signature check fails. We verified this isn't a fluke with an isolated throwaway-archive test swapping only the framework source. Questions for anyone who's solved this: Is ITMS-91065's "Apple SDK signature" requirement satisfiable by re-signing a self-built .framework with our own Distribution certificate during export, or does it specifically require Apple's own build-time signature that third parties can't reproduce? Has anyone shipped a Capacitor/Cordova app successfully against a new major Xcode/SDK before Ionic cut a matching signed release? If so, how? Also filed with Ionic: ionic-team/capacitor#8537 (https://github.com/ionic-team/capacitor/issues/8537) — no response yet as of 2026-07-23.
0
0
410
Jul ’26
App Update "Waiting for Review" Since July 16 — Is This Normal?
Hi everyone, I submitted an app update for review on July 16, and the status has been stuck at "Waiting for Review" for a full week now (7 days and counting). The app is not in a sensitive category (not health, finance, VPN, or gambling related), and there are no legal or export compliance issues that I'm aware of. A bit of background: App type: update (not a new app) Submission date: July 16, 2026 Apple Developer Program membership: active and in good standing No messages in Resolution Center or App Store Connect inbox No changes made to the submission during this period (no metadata edits, no new builds uploaded) I understand review times can fluctuate, but 7+ days in "Waiting for Review" — not even "In Review" — without any communication seems unusually long, especially for a routine update. Has anyone else experienced similar delays recently? Is there anything suggested beyond withdrawing and resubmitting (which I'd like to avoid)? Thanks in advance!
0
1
298
Jul ’26
Stuck in "Waiting for Review" for 10 days — 5 expedite requests ignored, critical crash-fix release
Our app has been stuck in "Waiting for Review" with no movement for 10 days. Timeline: July 13: Submitted version 2.0.1 (App ID 6584518186, a stability release) July 18: Resubmitted as 2.0.2 (build 133) with additional crash fixes — same app, same metadata Since then: no review start, no rejection, no metadata request, nothing. What we have already tried: Five (5) expedited review requests — all with concrete justification, zero response A status inquiry through Contact Us (App Review) — no response Review notes and a working demo account are fully provided and verified end-to-end Why this is urgent: this is a critical stability release. Firebase Crashlytics shows our crash-free user rate on the live version dropped to 55% — nearly half of our daily active users experience crashes (1,400+ crash events per 24 hours). The fixes are all in the waiting build. Every day of delay directly harms real users. Questions: Is there any way to find out whether a submission is simply queued vs. placed on an internal hold? App Store Connect shows only "Waiting for Review" either way. Is anyone else currently seeing 7+ day waits? (I've found several similar threads from February and May 2026 with no resolution posted.) Is there any escalation path left when expedite requests and Contact Us both go unanswered? App ID: 6584518186 Any guidance would be greatly appreciated.
0
0
151
Jul ’26
subscriptions remain Waiting for Review
Hello! My app beFamily (version 1.0.0) is already live on the App Store and has active users. I have developed and completed the subscription functionality, but I have been unable to release it because my auto-renewable subscriptions have been stuck in review for more than a month. The current state is inconsistent: The subscription group "beFamily Plans" is marked as In Review. Both subscriptions remain Waiting for Review. There is no active App Review submission containing these subscriptions. My app version 1.0.1 is in Prepare for Submission, but the "In-App Purchases and Subscriptions" section is missing, preventing me from attaching the subscriptions to the app version. If I submit the app without them, it is rejected under Guideline 2.1(b) because the reviewer cannot locate the subscriptions. This issue has now been blocking my subscription launch for over a month, preventing my users from purchasing subscriptions and preventing my business from generating subscription revenue. I have already: Opened a Developer Support case. Submitted Feedback Assistant report FB23817386. Posted the issue on the Apple Developer Forums. Performed all recommended troubleshooting steps without success.
0
0
219
Jul ’26
App Review Pending Since July 3 – Request for Assistance
Hello Apple Developer Support, My app has been in the "Waiting for Review" status since July 3, and I am concerned because the update has not yet been reviewed. App Name: Trading Insights - AI Charts This update is important, and I would like to make it available to my users as soon as possible. So far, I have: Submitted an Expedited App Review request. Contacted Apple Developer Support regarding the delay. Unfortunately, the app is still waiting for review, and I have not received any indication of whether there is an issue with my submission. Could you please check if there is any problem with my app or my submission that is preventing the review from starting? If there is anything I need to fix or provide, I would be happy to do so immediately. I would greatly appreciate any assistance or guidance. Thank you for your time and support. Kind regards, Jawad
0
0
231
Jul ’26
In-App Purchases and Subscriptions section missing from version page — cannot attach subscriptions to submission
I have been rejected twice under Guideline 2.1(b) because my In-App Purchase subscriptions are not submitted for review. I cannot figure out how to attach them to my submission. Here is my situation: I have 6 auto-renewable subscriptions fully configured in App Store Connect under "Barrel Pro Subscriptions" — all have screenshots, pricing, descriptions, and review notes My app is iOS only, built with React Native/Expo My current version is 1.1, Build 10 (1.1.0) The problem: The "In-App Purchases and Subscriptions" section does not appear anywhere on my version page. I have scrolled to the very bottom and it is not there. I cannot find any way to attach my subscriptions to my submission before clicking "Submit for Review." The blue info box on the Subscriptions page says: "Your first subscription must be submitted with a new app version. Select it from the app's In-App Purchases and Subscriptions section on the version page." But that section does not exist on my version page. What I have tried: Cancelling the rejected submission and starting fresh Creating a new version (1.1) manually Uploading a new build (Build 10) Checking both "In-App Purchases" and "Subscriptions" sections in the sidebar Has Apple removed this section from the version page? How do I attach my subscriptions to my submission in 2026? Any help is greatly appreciated. Thank you.
5
1
869
Jul ’26
iOS App Review is absurdly slow, and rejections come with no real justification
I need to vent some real frustration with App Review. Our app "AlphaOmega" has been live on the App Store since July 6, 2026. We submitted a routine update (version 1.0.4, not a new app) on July 11. It sat untouched in the review queue for 10 full days before anyone even looked at it. For an update to an already-approved, already-live app, that's not acceptable. And when it finally got reviewed on July 21, we got rejected under Guideline 4.1(a) "Copycats," with this justification: "Specifically, the app's icons include references to Omegle." That's it. No screenshot comparison, no explanation of what "reference" means. I put our icon next to Omegle's actual icon myself (attached below): Ours: white Greek letters Α/Ω overlapped, purple gradient background Omegle's: a blue background with a white comma-shaped swirl They share nothing — not color, not shape, not any design element. Our app name comes from the Christian phrase "Alpha and Omega," has nothing to do with "Omegle" beyond a partial spelling overlap. This isn't a borderline case that needs interpretation — it's just wrong. We've already replied to the review message with this clarification and separately submitted a formal appeal to the App Review Board. We also requested an expedited review — it made no difference. What makes this especially hard is that we built this app so our church community could finally have it. People have been anxiously checking in day after day, hoping to be able to use it together. This is how the cycle usually goes for us: submit, sit in the queue for days waiting for a reviewer to even look at it, sit in "In Review" for days more, then get rejected for a reason that doesn't hold up to two minutes of scrutiny — fix it, resubmit, and start the whole cycle again, with no guarantee the next rejection will even make sense. We've stayed up late more than once just to catch a review update, only for it to end exactly like this. Is this really how Apple treats developers? At this point I'm seriously reconsidering whether I want to keep building for iOS at all. So right now: 10 days to get a wrong answer, a canned one-line rejection with zero evidence, and I have to spend more time writing replies and appeals just to get a human to actually look at two icons side by side. Meanwhile the update sits blocked with no ETA. Is this the normal experience now? Anyone else dealing with 10+ day waits for simple updates, followed by rejections that don't hold up under two minutes of scrutiny? App Information: App Name: AlphaOmega Apple ID: 6783182206 Bundle ID: com.zoven.omega Platform: iOS Version rejected: 1.0.4 (build 26)
1
0
219
Jul ’26
App rejected, but no rejection reason shown anywhere (submission stuck on "In Review")
Hi all, I'm hoping someone has seen this before. My app's first submission was rejected, but I cannot find the rejection reason anywhere. What I see: The app-level status shows "Rejected". Under App Review, the submission itself still shows "In Review". There is no reviewer message / no Resolution Center message anywhere, and the in-app purchases are all marked as rejected too. The rejection email only says to visit the App Review page, but the link just opens the App Store Connect root (appstoreconnect.apple.com) with no details. What I already tried: App Store Connect on web (Safari/macOS and Firefox/Windows) and the App Store Connect iOS app — all three show the exact same state. Hard reload, private window, sign out / sign back in. Opened an App Review contact request asking for the specific reasons — no response until now. So the app is clearly rejected, but the submission status and the reviewer feedback never propagated on my end. It looks like a backend status/desync issue. Questions: Has anyone experienced this "rejected but stuck on In Review with no message" state? Where else can the rejection details appear, or is it purely a matter of waiting for the backend to sync? Roughly how long did it take to resolve for you? App: CountTally Submission ID: e9bf771c-a5a2-471f-9db4-7b7038d4ebf9 Thanks a lot for any pointers!
0
0
253
Jul ’26
Multiple apps stuck in App Review for months
Hello, I'm looking for advice from other developers who may have experienced unusually long App Review times. Here is my situation: • I submitted five apps on March 2, 2026. • They remained in Waiting for Review until the end of April. • They have now been In Review for several months. • I also submitted CampusGo Connect on May 14, 2026, and it is still Waiting for Review. I have contacted Apple Developer Support several times. They confirmed that my apps are still in the review process, but there have been no updates or requests for additional information. I have also verified that my Apple Developer Program membership is active, all agreements are accepted, and my App Store Connect account is functioning normally. Has anyone experienced review times this long? If so: • How long did your review eventually take? • Was there anything you did that helped? • Is there anything else I should try besides continuing to work with Developer Support? Thank you for any advice.
2
1
367
Jul ’26
App stuck in "Waiting for Review" for 9+ days - expedited review accepted, no response to support ticket
Hello, My first App Store submission (Apple ID 6769883617) has been stuck in "Waiting for Review" since July 12. Timeline: July 12: Submitted for review. July 18: Expedited review requested and approved. July 19: Contacted App Review through Contact Us / App Review Status. July 21: Still no status change and no response. I understand that review times can vary, but over 9 days in "Waiting for Review", an approved expedited request, and no reply from App Review no longer seems like a normal review timeline. Has anyone experienced this recently? Is there another way to reach the App Review team or verify that my submission isn't stuck? Any guidance would be appreciated. Thank you.
1
0
207
Jul ’26
App stuck in “Waiting for Review” since 7/14— support case unanswered
Hello, Our app submission has remained in “Waiting for Review” since 7/14. App: Skald: Odyssey Apple ID: 6790579937 Version: iOS 0.1.0 Support case: 102944762837 We contacted Developer Support on 7/17 and submitted the App Review status/contact form on 7/21, but have not received a response. App Store Connect does not show any action required from us. The submission metadata, review notes, contact information, demo credentials, and backend access are complete and available. Could an Apple representative please confirm that the submission is correctly queued and escalate the case if necessary? This delay is now significantly longer than our usual review times, and we have been unable to get a status update through the normal support channels. We would appreciate confirmation that the submission is not stuck and that no action is required from us. Thank you.
1
0
162
Jul ’26
App stuck in Waiting for Review - Over a Week
Hi, I just wanted to post to see if anyone else is experiencing extremely poor customer support from Apple. I have sent emails regarding the delay for the app review and heard nothing back, I have tried to call the worldwide support but get stuck in queues for over 3 hours before being disconnected. Has it always been this poor? My app has been stuck in review now for over a week despite it saying 48 hours, and whenever I try to reach out for help I receive no response. Could anyone please advise. Thank you!
1
0
200
Jul ’26
“waiting for review” status over 7 days
Hi. This is my first time submitting for app review. my app been stuck in “waiting for review” status for over 7 days. Any idea? Any help is appreciated.
Replies
0
Boosts
0
Views
106
Activity
4w
Developer account terminated under ADP 3.2(f) — Kalvero, App ID 6789877937
Hello, Fibo Business Limited’s Apple Developer Program membership was terminated under Section 3.2(f), citing unspecified indications of fraudulent conduct. App name: Kalvero App ID: 6789877937 Bundle ID: com.fibobusiness.kalvero Support case: 20000117968758 Kalvero is an original physical-goods shopping app developed and operated by our company. We have not manipulated ratings or rankings, hidden features, switched the app’s concept after review, offered fraudulent subscriptions, or attempted to evade App Review. The app uses Shopify checkout for physical goods and does not sell digital subscriptions. The dedicated review credentials only facilitate authentication; reviewers and ordinary users receive the same features, catalog, prices, and production backend. We have submitted a formal reinstatement request, but the termination notice did not identify a specific action, build, date, or account association. We understand that account-specific decisions cannot be resolved publicly. Could Apple Staff please confirm that our app submission and support case can be located, and advise whether any additional information is required through the official support channel? Thank you.
Replies
0
Boosts
0
Views
198
Activity
4w
Supported architecture and organization requirement for an on-device iOS domain blocker
I am planning an iOS security and content-blocking app for unmanaged consumer iPhones. The app would not provide a traditional VPN service. It would not offer: Remote VPN servers Geographic location switching Access to a private corporate network IP-address masking as a service Anonymous browsing Instead, the app would allow the user to: View destination domains contacted by the device Classify destinations such as trackers, advertising, analytics, or potentially malicious domains Manually block selected domains Keep connection history and filtering decisions on the device I understand that NEFilterDataProvider and NEFilterControlProvider are the APIs intended for network content filtering. However, according to TN3134, these providers are not generally deployable for an unmanaged adult consumer iPhone. I also understand that TN3120 says NEPacketTunnelProvider should not be used as a general-purpose local content filter. This appears to leave a gap for an unmanaged consumer security app whose core feature is user-controlled, system-wide domain blocking. I am considering whether NETunnelProviderManager with an NEPacketTunnelProvider could support the feature, but I do not want to use the packet-tunnel API outside its supported purpose. My questions are: Is there currently a supported Network Extension architecture for system-wide, user-controlled domain blocking on an unmanaged adult consumer iPhone? Can an app with this purpose use NEPacketTunnelProvider, or would that necessarily be considered the unsupported general-purpose filtering use described in TN3120? If such an architecture is supported, could an app with this purpose be treated as an approved security or content-blocking provider under Guideline 5.4 rather than as an app offering a traditional VPN service? App Review Guideline 5.4 states that apps offering VPN services must be submitted by developers enrolled as organizations. It also states that parental-control, content-blocking, and security apps from approved providers may use NEVPNManager. For an app that does not provide a remote VPN service but uses Apple’s VPN configuration infrastructure only for local security and user-controlled blocking, must the developer still enroll as an organization, or may an individual Apple Developer Program member submit it?
Replies
1
Boosts
0
Views
535
Activity
4w
Guideline 4.3(a) - Design - Spam
Dear Apple Review Team & Develpers! Could anyone clarify why Apple Reviewers, when rejecting the app under Guideline 4.3(a) - Design - Spam, do not provide any specific details? Each time my app is rejected, I receive a generic, automated response. In contrast, I provide detailed information and request clarification on the exact reasons for the rejection- specifically, what aspects of the app do not meet Apple's requirements. However, the responses I receive are always the same standard message without any useful details. Am I correct in understanding that the review process is entirely automated, with no human evaluation, resulting in repetitive, unhelpful replies? I would appreciate a more detailed response that can genuinely help me address the issue and ensure my app complies with Apple's guidelines. Here is their standard generic response to any my reply where I provide details and ask questions, but Apple Reviewer answer alsway with the same text: Guideline 4.3(a) - Design - Spam This app duplicates the content and functionality of other apps on the App Store, which is considered a form of spam. Specifically, this app appears to be identical to apps already on the App Store from other developers. Apps that duplicate content or functionality create clutter, diminish the overall experience for the end user, and reduce the ability of developers to market their apps. Next Steps It would be appropriate to revise your app to provide a unique experience or submit a new app that does not duplicate the content and functionality of other apps on the App Store. Resources Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third party Submitting several similar apps across multiple accounts Learn more about our requirements to prevent spam in App Review Guideline 4.3(a). Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Provide feedback on this message and your review experience by completing a short survey. Review Environment Submission ID: c4a62f43-b02a-40f0-b763-e00fcc996512 Review date: March 04, 2025 Version reviewed: 11.4.1202
Replies
1
Boosts
0
Views
1k
Activity
4w
Does expedited review carry over to a build resubmitted after rejection?
Does expedited review status carry over to a build resubmitted after a rejection? As I understood the expedited terms it does, but my resubmission has now been in Waiting for Review for three days. App: Hibi Calendar: Daily Journal Apple ID: 6762520622 Submission ID: ab5ae098-30c3-4185-a723-5f7901980dfa Timeline: Mid-July: submitted v3.0, a major update (first iPad build, Apple Pencil, a day-page customization layer). Sat in Waiting for Review over a week. Jul 20: requested expedited review, citing a live marketing campaign. Granted. Jul 21, 1:47 PM: rejected on one issue, Guideline 5.1.1. A pre-permission priming screen used the button label "Grant"; the reviewer asked for neutral wording like "Continue." Build 3.0 (35). Jul 21, 2:54 PM: uploaded build 3.0 (36) with the wording fixed, about an hour later. Today, Jul 24: still Waiting for Review. Roughly three days on the new build, two weeks since the original submission. Two things I got wrong(?), up front: The rejection included the Bug Fix Submissions offer (reply to the thread, keep the current submission). I declined it and uploaded a new binary instead. Believing I was still in the expedited queue, I filed a second expedited request two days after resubmitting. It shows as granted, but nothing moved. I know repeat requests are discouraged. I've also emailed App Review with no reply for over a week, and I haven't cancelled the submission - I don't want to reset the clock over a one-word fix that's already in the binary. My questions: did uploading a new binary rather than replying to the rejection thread drop me out of the expedited queue? Anything actionable on my end, or is the only thing I can do is wait?
Replies
0
Boosts
0
Views
137
Activity
Jul ’26
Title: Build stuck in "Waiting for Review" after resubmit — usually under 24h
Hello App Review team, My app (App ID: 6745896828) was rejected on Friday, July 17. I addressed the points raised and resubmitted the same day. Since then, the build has stayed in "Waiting for Review" with no update or response. This is highly unusual for our account: I have shipped regular updates for over a year, and every single review has been completed within 24 hours. Something appears to be stuck on this specific submission. This is a major version that our partner venues are actively waiting on for a business-critical feature (in-app reservations), so the delay has a direct impact on us. Could the App Review team please look into why this submission is stalled? Case ID: [102945425814] Thank you.
Replies
3
Boosts
0
Views
397
Activity
Jul ’26
Extended App Review Delay After Resolving Guideline 2.1 Issue – Looking for Guidance
Hi everyone, I'm looking for advice regarding an unusually long App Review process. Our app was initially submitted on July 7, 2026. During the review, Apple rejected the app under Guideline 2.1 – Information Needed because the demo account was not available due to a backend deployment ("User not found"). We immediately resolved the issue by creating and verifying the demo account, replied to the App Review team with the working credentials, and requested an expedited review. However, after providing the updated credentials, our app has remained in the review queue for several days without any further updates. We have also contacted Apple Developer Support and followed up multiple times through the App Review thread, but we have not yet received any information about the current status or whether there are any remaining blockers. This is our first App Store release, and the continued delay is affecting our planned public launch, business commitments, and customer onboarding. Has anyone experienced a similar situation after resolving a Guideline 2.1 issue? Is there any additional action we can take to help move the review forward, or is waiting the only option at this stage? Any guidance or suggestions from the community or Apple engineers would be greatly appreciated. Thank you!
Replies
0
Boosts
0
Views
118
Activity
Jul ’26
Explanation of App Review Following Successful Appeal under Clause 5.6
Dear App Review Team, First, I must admit my mistake and sincerely apologize for wasting your time. After my app was previously rejected under Guideline 5.6, I filed an appeal, which was subsequently approved. You instructed me to submit a new binary for review. Due to an error on my part, I submitted a new version and removed the previous submission record; consequently, the new submission was not linked to the ID associated with the approved appeal. I am writing today to provide the ID for my new submission: 0760b84f-00b6-4c77-a1a3-ab9040143c06 The submission ID associated with the approved appeal was: fb5b0474-3ed0-4a38-82c8-3e7553743d1f My App Apple ID : 6764726742
Replies
0
Boosts
0
Views
271
Activity
Jul ’26
ITMS-90111 vs ITMS-91065 catch-22: current-SDK third-party framework rebuild loses Apple SDK signature
We're hitting a submission deadlock with a Capacitor-based iOS app that I suspect will affect any app using Capacitor/Cordova (or similar frameworks distributed as prebuilt binaries) once Xcode 27 ships. Setup: App built with the current Xcode, targeting the current SDK. Embeds Capacitor.framework and Cordova.framework (via ionic-team/capacitor-swift-pm). The loop: Using Ionic's latest official release: these prebuilt frameworks are still built against an older Xcode/iOS SDK. App Store Connect rejects the upload with ITMS-90111 (stale SDK), even though the app's own target and every other embedded framework are current. To fix that, we rebuilt Capacitor.framework/Cordova.framework from Capacitor's open-source iOS source (MIT-licensed, same version as the official release) using the current Xcode — confirmed via archive that every framework now reports the current SDK. That upload is then rejected with ITMS-91065 (missing signature) — the rebuilt frameworks lack an Apple SDK signature that (as far as we can tell) only Ionic's own build pipeline can produce. So: official release → current-SDK check fails. Self-rebuilt release → signature check fails. We verified this isn't a fluke with an isolated throwaway-archive test swapping only the framework source. Questions for anyone who's solved this: Is ITMS-91065's "Apple SDK signature" requirement satisfiable by re-signing a self-built .framework with our own Distribution certificate during export, or does it specifically require Apple's own build-time signature that third parties can't reproduce? Has anyone shipped a Capacitor/Cordova app successfully against a new major Xcode/SDK before Ionic cut a matching signed release? If so, how? Also filed with Ionic: ionic-team/capacitor#8537 (https://github.com/ionic-team/capacitor/issues/8537) — no response yet as of 2026-07-23.
Replies
0
Boosts
0
Views
410
Activity
Jul ’26
App Update "Waiting for Review" Since July 16 — Is This Normal?
Hi everyone, I submitted an app update for review on July 16, and the status has been stuck at "Waiting for Review" for a full week now (7 days and counting). The app is not in a sensitive category (not health, finance, VPN, or gambling related), and there are no legal or export compliance issues that I'm aware of. A bit of background: App type: update (not a new app) Submission date: July 16, 2026 Apple Developer Program membership: active and in good standing No messages in Resolution Center or App Store Connect inbox No changes made to the submission during this period (no metadata edits, no new builds uploaded) I understand review times can fluctuate, but 7+ days in "Waiting for Review" — not even "In Review" — without any communication seems unusually long, especially for a routine update. Has anyone else experienced similar delays recently? Is there anything suggested beyond withdrawing and resubmitting (which I'd like to avoid)? Thanks in advance!
Replies
0
Boosts
1
Views
298
Activity
Jul ’26
Stuck in "Waiting for Review" for 10 days — 5 expedite requests ignored, critical crash-fix release
Our app has been stuck in "Waiting for Review" with no movement for 10 days. Timeline: July 13: Submitted version 2.0.1 (App ID 6584518186, a stability release) July 18: Resubmitted as 2.0.2 (build 133) with additional crash fixes — same app, same metadata Since then: no review start, no rejection, no metadata request, nothing. What we have already tried: Five (5) expedited review requests — all with concrete justification, zero response A status inquiry through Contact Us (App Review) — no response Review notes and a working demo account are fully provided and verified end-to-end Why this is urgent: this is a critical stability release. Firebase Crashlytics shows our crash-free user rate on the live version dropped to 55% — nearly half of our daily active users experience crashes (1,400+ crash events per 24 hours). The fixes are all in the waiting build. Every day of delay directly harms real users. Questions: Is there any way to find out whether a submission is simply queued vs. placed on an internal hold? App Store Connect shows only "Waiting for Review" either way. Is anyone else currently seeing 7+ day waits? (I've found several similar threads from February and May 2026 with no resolution posted.) Is there any escalation path left when expedite requests and Contact Us both go unanswered? App ID: 6584518186 Any guidance would be greatly appreciated.
Replies
0
Boosts
0
Views
151
Activity
Jul ’26
subscriptions remain Waiting for Review
Hello! My app beFamily (version 1.0.0) is already live on the App Store and has active users. I have developed and completed the subscription functionality, but I have been unable to release it because my auto-renewable subscriptions have been stuck in review for more than a month. The current state is inconsistent: The subscription group "beFamily Plans" is marked as In Review. Both subscriptions remain Waiting for Review. There is no active App Review submission containing these subscriptions. My app version 1.0.1 is in Prepare for Submission, but the "In-App Purchases and Subscriptions" section is missing, preventing me from attaching the subscriptions to the app version. If I submit the app without them, it is rejected under Guideline 2.1(b) because the reviewer cannot locate the subscriptions. This issue has now been blocking my subscription launch for over a month, preventing my users from purchasing subscriptions and preventing my business from generating subscription revenue. I have already: Opened a Developer Support case. Submitted Feedback Assistant report FB23817386. Posted the issue on the Apple Developer Forums. Performed all recommended troubleshooting steps without success.
Replies
0
Boosts
0
Views
219
Activity
Jul ’26
App Review Pending Since July 3 – Request for Assistance
Hello Apple Developer Support, My app has been in the "Waiting for Review" status since July 3, and I am concerned because the update has not yet been reviewed. App Name: Trading Insights - AI Charts This update is important, and I would like to make it available to my users as soon as possible. So far, I have: Submitted an Expedited App Review request. Contacted Apple Developer Support regarding the delay. Unfortunately, the app is still waiting for review, and I have not received any indication of whether there is an issue with my submission. Could you please check if there is any problem with my app or my submission that is preventing the review from starting? If there is anything I need to fix or provide, I would be happy to do so immediately. I would greatly appreciate any assistance or guidance. Thank you for your time and support. Kind regards, Jawad
Replies
0
Boosts
0
Views
231
Activity
Jul ’26
In-App Purchases and Subscriptions section missing from version page — cannot attach subscriptions to submission
I have been rejected twice under Guideline 2.1(b) because my In-App Purchase subscriptions are not submitted for review. I cannot figure out how to attach them to my submission. Here is my situation: I have 6 auto-renewable subscriptions fully configured in App Store Connect under "Barrel Pro Subscriptions" — all have screenshots, pricing, descriptions, and review notes My app is iOS only, built with React Native/Expo My current version is 1.1, Build 10 (1.1.0) The problem: The "In-App Purchases and Subscriptions" section does not appear anywhere on my version page. I have scrolled to the very bottom and it is not there. I cannot find any way to attach my subscriptions to my submission before clicking "Submit for Review." The blue info box on the Subscriptions page says: "Your first subscription must be submitted with a new app version. Select it from the app's In-App Purchases and Subscriptions section on the version page." But that section does not exist on my version page. What I have tried: Cancelling the rejected submission and starting fresh Creating a new version (1.1) manually Uploading a new build (Build 10) Checking both "In-App Purchases" and "Subscriptions" sections in the sidebar Has Apple removed this section from the version page? How do I attach my subscriptions to my submission in 2026? Any help is greatly appreciated. Thank you.
Replies
5
Boosts
1
Views
869
Activity
Jul ’26
iOS App Review is absurdly slow, and rejections come with no real justification
I need to vent some real frustration with App Review. Our app "AlphaOmega" has been live on the App Store since July 6, 2026. We submitted a routine update (version 1.0.4, not a new app) on July 11. It sat untouched in the review queue for 10 full days before anyone even looked at it. For an update to an already-approved, already-live app, that's not acceptable. And when it finally got reviewed on July 21, we got rejected under Guideline 4.1(a) "Copycats," with this justification: "Specifically, the app's icons include references to Omegle." That's it. No screenshot comparison, no explanation of what "reference" means. I put our icon next to Omegle's actual icon myself (attached below): Ours: white Greek letters Α/Ω overlapped, purple gradient background Omegle's: a blue background with a white comma-shaped swirl They share nothing — not color, not shape, not any design element. Our app name comes from the Christian phrase "Alpha and Omega," has nothing to do with "Omegle" beyond a partial spelling overlap. This isn't a borderline case that needs interpretation — it's just wrong. We've already replied to the review message with this clarification and separately submitted a formal appeal to the App Review Board. We also requested an expedited review — it made no difference. What makes this especially hard is that we built this app so our church community could finally have it. People have been anxiously checking in day after day, hoping to be able to use it together. This is how the cycle usually goes for us: submit, sit in the queue for days waiting for a reviewer to even look at it, sit in "In Review" for days more, then get rejected for a reason that doesn't hold up to two minutes of scrutiny — fix it, resubmit, and start the whole cycle again, with no guarantee the next rejection will even make sense. We've stayed up late more than once just to catch a review update, only for it to end exactly like this. Is this really how Apple treats developers? At this point I'm seriously reconsidering whether I want to keep building for iOS at all. So right now: 10 days to get a wrong answer, a canned one-line rejection with zero evidence, and I have to spend more time writing replies and appeals just to get a human to actually look at two icons side by side. Meanwhile the update sits blocked with no ETA. Is this the normal experience now? Anyone else dealing with 10+ day waits for simple updates, followed by rejections that don't hold up under two minutes of scrutiny? App Information: App Name: AlphaOmega Apple ID: 6783182206 Bundle ID: com.zoven.omega Platform: iOS Version rejected: 1.0.4 (build 26)
Replies
1
Boosts
0
Views
219
Activity
Jul ’26
App rejected, but no rejection reason shown anywhere (submission stuck on "In Review")
Hi all, I'm hoping someone has seen this before. My app's first submission was rejected, but I cannot find the rejection reason anywhere. What I see: The app-level status shows "Rejected". Under App Review, the submission itself still shows "In Review". There is no reviewer message / no Resolution Center message anywhere, and the in-app purchases are all marked as rejected too. The rejection email only says to visit the App Review page, but the link just opens the App Store Connect root (appstoreconnect.apple.com) with no details. What I already tried: App Store Connect on web (Safari/macOS and Firefox/Windows) and the App Store Connect iOS app — all three show the exact same state. Hard reload, private window, sign out / sign back in. Opened an App Review contact request asking for the specific reasons — no response until now. So the app is clearly rejected, but the submission status and the reviewer feedback never propagated on my end. It looks like a backend status/desync issue. Questions: Has anyone experienced this "rejected but stuck on In Review with no message" state? Where else can the rejection details appear, or is it purely a matter of waiting for the backend to sync? Roughly how long did it take to resolve for you? App: CountTally Submission ID: e9bf771c-a5a2-471f-9db4-7b7038d4ebf9 Thanks a lot for any pointers!
Replies
0
Boosts
0
Views
253
Activity
Jul ’26
Multiple apps stuck in App Review for months
Hello, I'm looking for advice from other developers who may have experienced unusually long App Review times. Here is my situation: • I submitted five apps on March 2, 2026. • They remained in Waiting for Review until the end of April. • They have now been In Review for several months. • I also submitted CampusGo Connect on May 14, 2026, and it is still Waiting for Review. I have contacted Apple Developer Support several times. They confirmed that my apps are still in the review process, but there have been no updates or requests for additional information. I have also verified that my Apple Developer Program membership is active, all agreements are accepted, and my App Store Connect account is functioning normally. Has anyone experienced review times this long? If so: • How long did your review eventually take? • Was there anything you did that helped? • Is there anything else I should try besides continuing to work with Developer Support? Thank you for any advice.
Replies
2
Boosts
1
Views
367
Activity
Jul ’26
App stuck in "Waiting for Review" for 9+ days - expedited review accepted, no response to support ticket
Hello, My first App Store submission (Apple ID 6769883617) has been stuck in "Waiting for Review" since July 12. Timeline: July 12: Submitted for review. July 18: Expedited review requested and approved. July 19: Contacted App Review through Contact Us / App Review Status. July 21: Still no status change and no response. I understand that review times can vary, but over 9 days in "Waiting for Review", an approved expedited request, and no reply from App Review no longer seems like a normal review timeline. Has anyone experienced this recently? Is there another way to reach the App Review team or verify that my submission isn't stuck? Any guidance would be appreciated. Thank you.
Replies
1
Boosts
0
Views
207
Activity
Jul ’26
App stuck in “Waiting for Review” since 7/14— support case unanswered
Hello, Our app submission has remained in “Waiting for Review” since 7/14. App: Skald: Odyssey Apple ID: 6790579937 Version: iOS 0.1.0 Support case: 102944762837 We contacted Developer Support on 7/17 and submitted the App Review status/contact form on 7/21, but have not received a response. App Store Connect does not show any action required from us. The submission metadata, review notes, contact information, demo credentials, and backend access are complete and available. Could an Apple representative please confirm that the submission is correctly queued and escalate the case if necessary? This delay is now significantly longer than our usual review times, and we have been unable to get a status update through the normal support channels. We would appreciate confirmation that the submission is not stuck and that no action is required from us. Thank you.
Replies
1
Boosts
0
Views
162
Activity
Jul ’26
App stuck in Waiting for Review - Over a Week
Hi, I just wanted to post to see if anyone else is experiencing extremely poor customer support from Apple. I have sent emails regarding the delay for the app review and heard nothing back, I have tried to call the worldwide support but get stuck in queues for over 3 hours before being disconnected. Has it always been this poor? My app has been stuck in review now for over a week despite it saying 48 hours, and whenever I try to reach out for help I receive no response. Could anyone please advise. Thank you!
Replies
1
Boosts
0
Views
200
Activity
Jul ’26