Hello, Our app, InReality (iOS version 0.1.4, build 20), has been in “Waiting for Review” since October 26, 2026. This is a new version of an existing app, using the same bundle ID, io.inreality.app. The previous version has been off the App Store for an extended period, and we are now preparing to bring InReality back. Timeline: October 26: Submitted version 0.1.4 for App Review. October 29: Requested expedited review and received confirmation: “We’ll expedite review for InReality.” October 30: Contacted App Review Support (Case #103013501314). November 1: Still “Waiting for Review,” with no visible review activity or requests for additional information. We understand that review times vary, but we are concerned that the submission has not entered review despite the accepted expedited request. Could an Apple representative help verify whether our submission is correctly queued for expedited review, check for any administrative or technical blocker, and escalate our existing support case if appropriate? If this cannot be checked through the forums, guidance on the appropriate escalation route would be appreciated. Our team is available to respond immediately to any requests for additional information. Thank you for your assistance.

Apple, Please Investigate: Two Apps Rejected for Information Already Provided in the Original Submissions Dear Apple Developer Community and App Review Team, I am writing to report a serious and extremely frustrating problem I have experienced with two different applications submitted to the App Store. Both applications were rejected under App Review Guideline 1.3, requesting answers to four questions that I had already answered completely in the App Review Notes during the ORIGINAL submissions. The information was not added after rejection. It was already provided before either application entered review. I fully support Apple’s strict requirements for children’s applications. However, these repeated incidents raise serious concerns about how App Review Notes and supporting documents are handled. **1. Kalimati - كلماتي Apple App ID: 6812125263** Kalimati is an educational application that helps children learn Arabic words and action verbs through interactive activities and animations. When submitting Kalimati for the first time, I explicitly answered all four required questions in the App Review Notes: Third-party analytics. Third-party advertising. Sharing user or device data with third parties. Other collection or processing of user or device information. Despite providing complete answers, Kalimati was rejected on October 11, 2026, requesting answers to those exact same questions. These answers were already included in the original submission! I responded again and resubmitted the application on October 11. As of October 22, Kalimati remains in “Waiting for Review” status, 11 days after resubmission. I contacted Apple Developer Support multiple times. Although I was informed that steps would be taken to expedite the review, the application remains in the queue. This delay followed a request for information that had already been provided. **2. HeroHop: Sky Adventure Apple App ID: 6823625184** After my experience with Kalimati, I took additional precautions before submitting HeroHop on October 20, 2026. I provided the answers in TWO separate places: First: Complete answers to all four questions in the App Review Notes. Second: A detailed two-page PDF attachment titled “HeroHop-App-Review-Notes-Build-8.pdf”, addressing each question individually and explaining privacy practices, data handling, parental controls, and in-app purchases. Nevertheless, HeroHop was rejected the following day with an automated message requesting answers to the exact same four questions! I had answered every question in the designated field AND attached detailed supporting documentation. Yet the application was rejected as though none of this information had been provided. I repeated the answers and resubmitted HeroHop on October 21. The Real Problem The issue is not Apple’s requirement to answer privacy-related questions. Those questions are reasonable and important. The issue is that Apple repeatedly requests information that developers have ALREADY provided in the designated submission fields. With Kalimati, the answers were included in App Review Notes. With HeroHop, the answers were included in App Review Notes AND a separate PDF. Both applications received requests for the same information again. This raises important questions: Are App Review Notes displayed correctly to reviewers? Are supporting documents properly accessible? Are automated requests generated without checking existing answers? Is there a procedural problem in reviewing Kids Category submissions? I cannot determine the cause from outside Apple’s systems. However, experiencing the same issue twice, despite taking additional precautions, strongly suggests that the submission or review workflow requires investigation. The Consequences for Developers Every unnecessary rejection can delay an application for days or weeks. Kalimati has remained in “Waiting for Review” since October 11. Developers spend considerable time preparing applications, testing them, documenting compliance, and answering Apple’s questions. It is extremely frustrating to complete these requirements correctly, only to receive a rejection requesting information that was already provided. This wastes developers’ time, disrupts release schedules, and undermines confidence in Apple’s review process. What Apple Should Investigate and Improve I respectfully urge Apple’s App Review management and App Store Connect teams to investigate and improve the following: 1. Verify App Review Notes: Ensure submitted information is correctly stored, displayed, and examined before requesting additional answers. 2. Verify attachments: Ensure supporting PDFs and documents are clearly visible and accessible to reviewers. 3. Prevent repeated requests: Before issuing a rejection, verify whether the requested information already exists in the original submission. 4. Provide specific explanations: If an answer is insufficient, explain precisely what is missing instead of repeating the same questionnaire. 5. Investigate the Kids Category workflow: Examine why the same four Guideline 1.3 questions are repeatedly requested despite documented answers. 6. Establish an escalation channel: Allow developers to report recurring procedural problems beyond individual rejection decisions. Concern About My Upcoming macOS Application I am currently developing another application for macOS. After these experiences, I am genuinely concerned that I may encounter another unnecessary rejection because information I carefully provide is overlooked. Developers should not have to worry whether their App Review Notes will actually be considered. A Direct Appeal to Apple I am not requesting special treatment, exceptions to Apple’s guidelines, or approval without proper review. I fully respect Apple’s responsibility to protect users, particularly children. I am simply asking Apple to ensure that information developers provide is actually read and considered before applications are rejected for supposedly missing information. Apple, please investigate this issue at both the management and technical levels. If there is a technical problem, fix it. If there is a procedural problem, improve the procedure. If answers are insufficient, explain exactly what is missing. This is a real and recurring problem that deserves serious attention. I also invite fellow developers to share their experiences: Have you received a Guideline 1.3 rejection requesting the four Kids Category answers even though you had already provided them in your original App Review Notes? I sincerely hope Apple takes this issue seriously and investigates its underlying cause. A Final Request to the Community Please help bring this issue to Apple’s attention. Salman Farhat

Hello, I’m an independent developer and founder of a startup preparing for its first App Store launch. Our application was rejected under Guideline 4.3(a) for alleged similarity to other applications. We believe the rejection may be related to an earlier version of our own application that existed exclusively for internal TestFlight testing under a different developer account. That version was never submitted for public App Store review. We provided a detailed explanation to App Review and resubmitted the application without code changes, as we dispute the original finding. Our current submission has now remained in “Waiting for Review” for over 60 hours. We have already requested expedited review and opened a Developer Support case, but have received no substantive response. Our business launch is time-sensitive, and the continued uncertainty is causing significant financial and operational difficulties. Could an Apple App Review representative please advise whether there is a way to escalate this matter or arrange private communication with the appropriate team? I would be happy to provide our App ID, Submission ID, support case number and supporting documentation privately through an official Apple channel. Thank you.

Hi Apple Developer Community, I'm reaching out to share my situation and seek advice from developers who may have experienced something similar. Recently, my Apple Developer account received a Pending Termination Notice, and my app, FastWise: IF Fasting Timer (App ID: 6798288587), was removed from the App Store. Apple stated that the account had been flagged for alleged dishonest or fraudulent activity related to developer identity or account information, citing Section 3.2(f) of the Apple Developer Program License Agreement and App Review Guideline 5.6.2. I submitted an official appeal to the App Review Board on October 8, 2026, explaining my situation and requesting a review of the decision. I also contacted Apple Developer Support by phone. However, as of October 16, I have not received any updates or response regarding my appeal. I'm concerned because the notice states that my developer membership may be terminated, earnings payments are paused, and app transfers are disabled. I fully respect Apple's policies and understand the importance of maintaining a trustworthy App Store ecosystem. I am willing to provide any additional information or documentation required to resolve this matter. I would appreciate guidance from the community on a few questions: Has anyone experienced a similar Pending Termination Notice and successfully appealed it? How long does Apple typically take to respond to a developer account termination appeal? Is there an official way to request a status update or escalation when an appeal has already been submitted? Are there any additional steps I should take while waiting for the App Review Board's response? App: FastWise: IF Fasting Timer App ID: 6798288587 Appeal submitted: October 8, 2026 Any insights or experiences would be greatly appreciated. I hope to resolve this situation fairly and continue developing apps for the Apple ecosystem. Thank you for your support!

Hello App Review, I’m looking for guidance on an update that has been through two review rounds and is now waiting on a Bug Fix Submission approval with no reply. App: Know Your Dosh: Money Tracker (iOS) Apple ID: 6739780269 Version: 2.0.10 (build 336) Submission ID: c728875d-ad9b-4eef-9bee-ec91522f5960 Timeline: 12 Oct: Submitted 2.0.10 (build 318). 15 Oct: Rejected under Guideline 2.1, Information Needed (ATT prompt not located on iPadOS 27.0.1). 16 Oct: Replied in App Store Connect with a screen recording from a physical device showing the ATT prompt, and added it to the Notes field. 19 Oct: Rejected under Guideline 5.1.1(ii), ATT purpose string not sufficiently specific. 19 Oct: Replied asking for clarification on what the string should say for our use case (attribution via an MMP, no advertising in the app). 21 Oct: Submitted build 336 with bug fixes, including a fix for universal links that are broken for users on the current live version. 27 Oct: Build 336 reviewed. App Review offered the Bug Fix Submission option, stating the 5.1.1(ii) issue is eligible to be resolved in the next update and that we did not need to resubmit. 27 Oct, 3:12 PM: Replied in App Store Connect accepting the Bug Fix Submission, confirmed the build includes bug fixes, and provided the updated purpose string that will ship in the next update. Current status in App Store Connect: Waiting for Review We have not resubmitted or cancelled anything since 21 Oct, and the updated ATT purpose string is already in our next build. The live version has a universal links bug that this update fixes, so we’d like to understand whether anything further is needed from us for build 336 to proceed under the Bug Fix Submission process. Thank you, Varun Aggarwal

Hello, Our first app submission has been in "Waiting for Review" since October 18, 2026, with no status change. Submitted: October 18, 2026 Developer Support case: 103009496109 (October 26 and 28, no reply yet) Current status: Waiting for Review There is no message in App Review, and the agreements are up to date. The demo account details are in the App Review Information. Could someone confirm whether this submission is progressing normally? If anything further is needed, I'll provide it right away. Thank you.

Hello, Our submission has been in "Waiting for Review" since 15 October 2026 with no status change. App name: Healy 3 Apple ID: 6776578116 Submitted for review: 15 October 2026 Scheduled pre-order release: 18 October 2026 (already passed) Expedited review requested: 21 October 2026 Developer Support case: 103005950459 (23 October 2026) Current status: Waiting for Review There is nothing in Resolution Center, and we have received no requests for further information or documentation. The App Review Information section includes a demo account and video walkthroughs, as the app requires a paired Bluetooth device to complete onboarding. This is a business app, so approval is time-critical for us — and we have a further submission to follow. Could someone confirm whether this submission is progressing normally or whether it is held in an error state? If anything further is needed from us, we will provide it immediately. Thank you.

I'm trying to prepare my app for the iPhone Duo release. I'm now producing the screenshots for the Duo. Apple's guidance gives dimensions for folded and unfolded, but these dimensions are both different in height, so they would make them visually uneven on the App Store, which would undoubtedly be refused. My screenshots show the device on a coloured background. I have shots for both open landscape and closed portrait, but I'm unsure how to properly format them. Are there any examples that Apple have released for me to review?

A couple months ago, I got an error when attempting to deploy our app to App Store Connect (see error further below). I used the CLI command xcrun altool --upload-app, and I was trying to upload a new version 1.0.26 build 0, when the previous uploaded version was 1.0.25 build 2 (so the new version is definitely a higher number). I later tried to upload a version 1.0.27 build 1, and that still failed. Note that I have an identical staging app, and I was able to go from 1.0.25 build 2 to 1.0.26 build 0 just fine there. And I have never had issues with version incrementation in the past for either our production or staging app. What could be going wrong here? Here are the error logs: 2026-04-30 23:18:19.430 ERROR: [ContentDelivery.Uploader.6000012404C0] The provided entity includes an attribute with a value that has already been used (-19232) The bundle version must be higher than the previously uploaded version: ‘0’. (ID: 71a9077b-807a-476c-b8a2-04cb8357bc32) NSUnderlyingError : The provided entity includes an attribute with a value that has already been used (-19241) The bundle version must be higher than the previously uploaded version. status : 409 detail : The bundle version must be higher than the previously uploaded version. Failed to upload archive at '[MyApp].ipa'. source : pointer : /data/attributes/cfBundleVersion id : 71a9077b-807a-476c-b8a2-04cb8357bc32 code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE title : The provided entity includes an attribute with a value that has already been used meta : previousBundleVersion : 0 previousBundleVersion : 0 iris-code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE 2026-04-30 23:18:19.431 ERROR: [altool.6000012404C0] Failed to upload package. 2026-04-30 23:18:19.431 ERROR: [altool.6000012404C0] The provided entity includes an attribute with a value that has already been used (-19232) The bundle version must be higher than the previously uploaded version: ‘0’. (ID: 71a9077b-807a-476c-b8a2-04cb8357bc32) NSUnderlyingError : The provided entity includes an attribute with a value that has already been used (-19241) The bundle version must be higher than the previously uploaded version. status : 409 detail : The bundle version must be higher than the previously uploaded version. source : pointer : /data/attributes/cfBundleVersion id : 71a9077b-807a-476c-b8a2-04cb8357bc32 code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE title : The provided entity includes an attribute with a value that has already been used meta : previousBundleVersion : 0 previousBundleVersion : 0 iris-code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE

Our iOS app has been sitting in "In Review" for four weeks and we have not been able to get a status update through any channel, so I'm posting here in case someone from App Review can take a look. App: Epocra, iOS, version 1.0, build 268 Apple ID: 6813697639 Status: In Review since September 24, as Developer Support confirmed on October 1 Timeline Sept 22: build 267 rejected under 2.1(a), a launch crash on iPad Air running iPadOS 27. Fixed the same day and resubmitted as build 268. Sept 22: a reviewer signed in to the demo account that evening. No activity since. Sept 28: opened a status request through Contact Us, case 102979044954. On Oct 1 Developer Support replied that the review was "outside of our normal timeframe" and that the review team had been notified. Nothing since. Oct 5: second status request, case 102986888342. Acknowledgement only. Oct 9: replied in the App Review message thread for the submission citing both cases. No response. We have not changed anything on the submission while it is in review so we don't reset the queue. The app is a business phone app (CallKit and PushKit VoIP with server-side call recording and a consent screen on first launch). The review notes include a demo account, a walkthrough video, and a phone number the reviewer can call to test inbound calls. Is there anything else we should be doing to get this looked at, or can someone from App Review check on it? Happy to provide anything that would help.

Hello App Review team, Our minorly revised app submission has been stalled for >5 days and like others is stuck on Waiting for Review. One thing that may be related: since the submission, App Store Connect has shown a banner asking the Account Holder to accept the updated Paid Applications Schedule, but in the Business module the Paid Apps row offers only "View Terms" with no Agree button, and there is nothing to accept on developer.apple.com either. I am the Account Holder. If that pending schedule is what is holding the review, we need Apple's help to clear it today, because it cannot be accepted from our side. App name: Girl JuJu Apple ID: 6816548377 Version: 1.0.0 (build 6) Submitted: October 23, 2026 Current status: Waiting for Review This is extremely urgent. Girl JuJu is being showcased at an event on October 30, and we need the app approved and ready to release by end of day October 29. The event was planned around a normal review turnaround from the October 23 submission, and 5 days at Waiting for Review has left us 1 day. The previous build of this version (build 4) was already approved by App Review and is at Pending Developer Release; build 6 is the same app with updated question content and a fix to how the app loads on first open, so nothing about the app's scope or purchases has changed. Google Play has approved the same release. We're ready to provide anything the review team needs right away, including a demo account or additional info, which we can share privately. Could someone confirm whether anything is blocking the submission or needed from our side, and whether an expedited review is possible given the October 30 date? Thank you, Christine Clancy, Girl Juju, Inc. (Team ID HLF8K8QY79)

Hello Apple App Review Team and fellow developers, I'm an independent developer preparing to launch my first iOS application, Workout Alarm: Wakeletics, and I'm experiencing an unusually long wait for App Review. App Details: App Name: Workout Alarm: Wakeletics Apple App ID: 6812064201 Platform: iOS Version: 1.0.0 Submitted: October 22, 2026, at approximately 5:00 PM CDT Current Status: Waiting for Review As of October 28, my app has been waiting for almost six days without moving to "In Review". I have not received any feedback or requests for additional information in App Store Connect. I've verified that the App Review Information is complete, including detailed testing instructions, contact information, explanations of the app's functionality, and an attached demonstration video. I also contacted Apple Developer Support on October 27 to check whether anything might be blocking the review, but I have not received a response yet. I understand that first-time submissions may require additional verification. However, given Apple's published review-time estimates and the similar delays reported by other developers this month, I wanted to ask: Is there currently a broader backlog affecting first-time iOS app submissions? Could someone from the App Review team confirm whether my submission is correctly queued? Is there anything else I should check or provide without withdrawing and resubmitting the app? I would greatly appreciate any guidance or clarification. Thank you for your time and assistance. Best regards, Sam Developer of Wakeletics

Hi, Our app peeka (App ID 6819420154), version 1.0.47 build 19, has been in "Waiting for Review" since 22 October 2026, 20:00 UTC. It has not moved to "In Review" once. Timeline: 5 Oct: version 1.0.47 created, first submissions on 9 Oct 14 Oct: rejected under Guideline 1.2 (user-generated content) 17 Oct: we addressed every 1.2 point and replied in App Store Connect 22 Oct: resubmitted with build 19, which contains those fixes. It has been waiting ever since. So far we have: requested an expedited review three times (no reply) confirmed that our Free Apps Agreement is active (since 19 Oct) confirmed that the demo account in the review notes still signs in Is there anything on our side blocking the submission, such as missing metadata or a flag on the account? If the submission is stuck in the queue, could someone please look at it? Thank you.

My first app submission has been in Waiting for Review since 16 October 2026 with no change of state — twelve days. App: Parozo: Restaurant POS & KOT Apple ID: 6817765731 Version: 1.0.0 (iOS) Submitted: 16 Oct 2026, 9:10 AM Case ID: 103011293263 Version 1.0.0 was reviewed and rejected on 14 October. I addressed the feedback and resubmitted on 16 October. Since then the submission has not entered review. I understand this is a first app with no prior review history, and that review times are longer than usual at the moment, so I am not looking to jump the queue. I have already contacted App Review through the App Review Status form and have the case ID above. If anyone from Apple is able to confirm the submission is queued normally, or point out anything outstanding at my end, I would be grateful. Happy to provide demo credentials or a walkthrough video.

Hello, My first iOS app, Textout (version 1.0.0, build 46), has been in "Waiting for Review" since October 14, 2026, and has never moved to "In Review". There are no messages from Apple in App Store Connect, and no requests for additional information. Details App ID: 6793842235 Version / build: 1.0.0 (46) Submitted: Oct 14, 2026 at 2:37 AM (IST) Submission ID: 4b32b67c-ee72-4d8d-9351-3d09e284e9b1 Support case ID (App Review Status): 103005845026, opened Oct 23 What I've already done Requested expedited review twice Opened a support case with App Review, with no reply so far Not edited, withdrawn or resubmitted the build, so I don't lose my place in the queue I've seen other developers report long "Waiting for Review" times this month. Is anyone else still seeing this, and did your app move without any further action? Any guidance from App Review would be appreciated. Thank you.

Hello Apple Developer Community, Our app, ALANN, has been going through the App Store review process since September 21, 2026, and we are still unable to complete the review. As of October 27, our latest submission remains in “Waiting for Review,” unchanged since October 16. Despite our continued efforts, the prolonged delay is having a significant impact on our business: Business launch delayed: We are unable to proceed with our planned iOS launch. Ongoing financial losses: The delay is affecting our planned operations and causing financial losses while we wait for the app to become available. Previous feedback addressed: We have implemented the requested changes and provided dedicated Individual Seller and Dealer test accounts, pre-populated data, payment testing details, and detailed review instructions. Multiple escalation attempts: We have contacted Apple Developer Support several times and submitted an expedited review request. No clear update: Despite these efforts, the submission remains in “Waiting for Review,” and we have not received a clear explanation for why the review has not started. We understand that App Review timelines can vary, but the continued uncertainty is making it increasingly difficult to manage our launch plans and business commitments. Has anyone experienced a similar delay despite providing all requested information and following up through official support channels? Is there an appropriate way to request clarification on the review queue status? We would genuinely appreciate any practical guidance or relevant experiences from the developer community. Regards,Team ALANN

Hello Apple Developer Forums community, I would like to ask whether anyone has experienced a similar App Review delay and whether there is anything I can do to move the review process forward. Here is the submission timeline for my app: July 26, 2026: Submitted an app update for review. July 28, 2026: The submission was rejected due to Guideline 2.3.6, Guideline 3.2.1(viii), and Guideline 3.2.2(ix). August 19, 2026: After addressing the issues raised in the rejection, I replied and resubmitted the app for review. October 1, 2026: Since the status had remained under review for an extended period, I canceled the existing submission and submitted it again. October 27, 2026: The app is still showing “In Review” in App Store Connect, with no apparent progress. It has now been more than two months since I first submitted the update, and the current review has been pending for a considerable amount of time. I understand that review times can vary depending on the app and the issues involved. However, I am concerned that something may be holding up the review process. I would appreciate any advice on the following questions: Has anyone experienced a similar delay recently, particularly after addressing previous App Review guideline violations? Is there anything I can do to determine whether the submission is progressing normally or requires additional action from my side? Would it be advisable to contact App Review or Apple Developer Support directly at this point? Based on your experience, is there any way to estimate when the review might be completed? I am not looking to bypass the App Review process. I would simply like to understand whether this extended delay is normal and what steps I should take next. Thank you for your time and any advice you can share. Submission ID: 59357cf3-2efd-4795-88ce-e761cb79e171

Hello Apple Developer Community, I submitted my iOS app, Backed: Warranty & Claim Kit, for App Review and received Apple's confirmation email stating that the app had been received for review. The email mentions that over 90% of apps are reviewed within 48 hours. However, it has now been more than 48 hours, and my app's status is still showing “Waiting for Review” in App Store Connect. I understand that review times can vary depending on several factors, but I would appreciate some guidance from developers who have experienced a similar delay. Has anyone recently experienced a review delay beyond 48 hours? Is it normal for an app to remain in “Waiting for Review” status for several days? At what point should I contact Apple Developer Support? App details: App name: Backed: Warranty & Claim Kit Platform: iOS Current status: Waiting for Review Time elapsed: More than 48 hours I would appreciate any advice or insights from developers who have experienced this situation. Thank you!

App: Sudoku: Cosmos (iOS 1.0.1, build 5) Submission ID: 010c7c7d-6a2d-4a66-b16b-003aa5f2eefe Timeline: Oct 11: reviewed; Oct 14: metadata rejected under Guideline 2.3.3 (screenshots). Oct 14: replaced all screenshots with captures of the actual app UI and resubmitted the same submission. Since then: "Waiting for Review" with no change (13 days). Expedited review was requested; no response. I cannot reply in the submission message thread: every attempt fails with a validation error, even a one-line message. Could App Review confirm the resubmission is in the queue? Thank you.

App: Sudoku: Cosmos (iOS 1.0.1, build 5) Submission ID: 010c7c7d-6a2d-4a66-b16b-003aa5f2eefe Timeline: Oct 11: reviewed; Oct 14: metadata rejected under Guideline 2.3.3 (screenshots). Oct 14: replaced all screenshots with captures of the actual app UI and resubmitted the same submission. Since then: "Waiting for Review" with no change (13 days). Expedited review was requested; no response. I cannot reply in the submission message thread: every attempt fails with a validation error, even a one-line message. Could App Review confirm the resubmission is in the queue? Thank you.