An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Hello Apple Developer Community, I’m posting here because I have exhausted the available channels to resolve an issue concerning the termination of my Apple Developer Program membership, and I’m struggling to obtain a meaningful response or clarification. After receiving the termination notice, I submitted an appeal and attempted to contact the Apple Developer Support team by phone to understand the decision and explore whether there was any possibility of resolving the issue. Unfortunately, I was told that the matter was not within the team's control. This was extremely disappointing because I was seeking a clear explanation and guidance on what I could do next. Since then, I have been unable to establish meaningful further communication through phone support. I submitted another appeal through the available channel, provided identity verification documents, and explained my application's functionality and disclosures. However, I have still not received a meaningful response addressing the specific concerns I raised. My application is a simulation-based mining app, not an actual cryptocurrency mining service. I have made efforts to disclose its simulation-based nature transparently throughout the app's presentation, including: App metadata and description Promotional text In-app disclosures Supporting documentation submitted during the appeal Despite these efforts, my Developer Program membership was terminated, and I have not received sufficient clarification about the specific issue that remains unresolved or whether the information and documentation I submitted were properly considered. I fully understand that Apple has developer policies and that developers are expected to comply with them. I am not asking Apple to ignore its guidelines. I am asking for a fair opportunity to understand the decision, clarify any remaining concerns, and determine whether any further action is possible. What makes this situation particularly frustrating is that I have invested considerable time, effort, and money into developing and maintaining my applications and participating in the Apple Developer Program. Paying the membership fee while being unable to obtain meaningful clarification or a substantive response to my appeals leaves me feeling that my investment and efforts have not been adequately acknowledged. I am not expecting a guaranteed reinstatement. I am requesting transparency, a meaningful explanation, and clarity on whether my case has received a proper review. I would appreciate guidance on the following questions: Is there any official escalation channel available when a developer has exhausted the usual appeal and support channels? Can Apple clarify whether the simulation-based nature of an app, when disclosed in its metadata, promotional text, in-app content, and supporting documentation, is sufficient to address the relevant policy concerns? I understand that compliance depends on the complete app and applicable guidelines. Is there any further review process available after an appeal has been rejected or has gone unanswered? If a membership termination decision is final, is there a way to obtain a clear explanation of the specific policy concerns that led to it? I am sharing this experience publicly because I genuinely want to understand what happened and whether any legitimate path forward remains. I have tried to resolve this through the official channels before bringing the matter to the community. I may also share my experience on Reddit so that other developers facing similar situations can learn from it. My intention is to raise awareness about the difficulty of obtaining meaningful communication during a serious account-related dispute, not to attack individual support representatives. If anyone from Apple or anyone who has experienced a similar situation can offer factual guidance about the available options, I would sincerely appreciate it. Thank you for taking the time to read my post.

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!

Hello Apple App Review Team, I'm seeking urgent assistance with Carrying The Fire (Apple ID: 6820179361), submitted on 9 October 2026, which has now remained in "Waiting for Review" for over eight days, without progressing to active review. An expedited app review request was also submitted. The app is an essential component of a major government-funded public arts event on 7 November 2026 in Albany, Western Australia, involving approximately 2,000 community participants. The event is presented by FORM as part of Albany 2026, with support from the Australian Government's Festivals Australia program and Lotterywest. The performance depends on participants downloading and preparing the app well in advance. Our planned distribution period is already underway, and the continued delay is directly affecting participant preparations and putting the event at risk. The Android version has already been approved and published on Google Play, but iOS participants are currently unable to download or prepare the app, creating an increasingly concerning issue as the event approaches. We have submitted a formal expedited-review request and contacted Apple Developer Support twice (Case ID: 102994798591), but have received no response. Given the fixed event deadline and the significant number of participants affected, could an Apple App Review representative please urgently investigate our submission and escalate it to the appropriate team? Official event information: https://www.albany2026.com.au/events/carrying-the-fire Any help here would be truly appreciated. Thank you for your assistance.

Hello everyone, I am an independent developer of Bolzplatz – Soccer GM (App ID: 6747684577), and I am hoping someone from Apple's App Review team might be able to help me. Unfortunately, I have been experiencing recurring and unusually long App Review delays over the past several weeks. During a previous submission, I had to wait more than three weeks for a review, despite receiving confirmation that my expedited review request had been approved. Multiple attempts to contact Developer Support did not resolve the situation. Now I am facing similar difficulties again. Since October 16, 2026, I have been trying to get another update reviewed. Concerned about another prolonged delay, I submitted two replacement builds, hoping to avoid a possible issue with the review process. I understand that replacing a build may reset the review queue. However, my previous experience has left me genuinely concerned that something might not be working correctly. What makes the situation especially frustrating is the lack of communication. I have contacted Apple Developer Support several times, including messages on October 19 and 20, and submitted another support request on October 22. Unfortunately, I have not received a substantive response. I also submitted formal complaints on September 29 and October 21 regarding these recurring issues. As an independent developer, I continuously invest considerable time and resources into improving my game, fixing bugs, and providing new features for my players. I fully respect Apple's review process and understand the importance of thorough app reviews. However, repeated delays without meaningful communication make it extremely difficult to plan updates and support my players. My main concern is whether there might be an underlying technical or administrative issue affecting my application's review process. Could someone from the Apple App Review team please help investigate this situation or advise me on how to get it properly escalated? I would sincerely appreciate any assistance or guidance. Thank you very much for your time! Kind regards,Felix DämmrichDeveloper – Bolzplatz – Soccer GM

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

The Screenshot specifications page lists iPhone Duo as an iPhone screenshot size: Outer display: 1398 × 2034 and 2034 × 1398 Inner display: 2007 × 2853 and 2853 × 2007 https://developer.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications I cannot find a way to upload them. In App Store Connect, the App Previews and Screenshots device selector on my app's version page does not list iPhone Duo. The only iPhone options are the existing display sizes. In the App Store Connect API, ScreenshotDisplayType has no Duo case. The largest iPhone case is still APP_IPHONE_67. I checked the current reference: https://developer.apple.com/documentation/appstoreconnectapi/screenshotdisplaytype My questions: Where in App Store Connect do I upload iPhone Duo screenshots? If the option is not open yet, is there a ScreenshotDisplayType case for Duo that I should use through the API instead? Thanks.

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.

My App Preview videos display correctly, but none of the existing screenshots are visible in Preview. Both the released version and new created version. However, in the Asset Library (one of the newly introduced tabs in App Store Connect), those screenshots are marked as used in all versions. I tried to re-upload the screenshots or browse from assets, but the system returned an error. I suspect this happens because the screenshots are already attached to the version but fail to display, which prevents any new screenshots from being added. Another similar issue is that previews for newly added assets disappear as soon as the web page is switched. I uploaded a video/screenshot for the Header and Search Results. Although it processed successfully, the preview does not display unless I manually click the Preview button. Furthermore, if I navigate to a different page in App Store Connect (such as switching to another localized language to add a new asset) and then return to the original language, the preview is completely gone. However, according to the Asset Library, the header asset has already been successfully added. It appears that the Preview function in the newly updated App Store Connect is experiencing bugs. Currently, this issue is blocking me from submitting new versions. Filed FB25118327

Hi everyone, We submitted Yutori Kids for review on October 10, and it has been in “Waiting for Review” for 12 days. We also requested an expedited review three days ago but haven’t received an update. Has anyone experienced a similar delay recently? Is there a recommended way to follow up with App Review? Thank you!

Hello Apple App Review Team and Community, We would like to request an expedited review of a critical bug fix update for HungryAliens (App ID: 6449141384), which is currently live on the App Store. Our large-scale competitive multiplayer feature, Guild Conquest, launched on September 15, is experiencing critical issues, including a bug that prevents players from defeating a boss. These issues are directly affecting active players and disrupting normal gameplay progression. On October 13, our update was rejected due to an issue with an App Store screenshot. We corrected the screenshot and requested a re-review within approximately two hours. However, the review did not resume, so we withdrew the original submission and submitted a new build on October 19. The latest submission remains in "Waiting for Review" status, preventing us from delivering the necessary critical fixes to our players. App Information App Name: HungryAliens App ID: 6449141384 App Bundle ID: com.DetailGames.HungryAliens Timeline September 15: Launched Guild Conquest, a major competitive multiplayer feature. October 13: The update containing critical bug fixes for Guild Conquest was undergoing App Review. October 13: Received a rejection under Guideline 1.1 (Safety – Objectionable Content) related to an App Store screenshot → Corrected the screenshot and submitted the revised material through App Store Connect within approximately two hours, requesting the review to resume. October 13–19: Despite our prompt response, the review did not resume, delaying approval of the critical bug fix update. October 19: Withdrew the previous submission and resubmitted a build containing the necessary fixes. October 20: The latest submission remains in "Waiting for Review" status. Why This Is Urgent Guild Conquest is a large-scale competitive multiplayer feature involving many players, where accurate information display is essential. However, issues affecting this functionality are currently occurring. A critical bug is preventing players from defeating a specific boss in Guild Conquest, disrupting normal gameplay progression. These issues directly affect the gameplay experience and competitive fairness of players currently participating in the content. Although we promptly addressed the review feedback on October 13, the update has still not been approved, preventing us from delivering the necessary bug fixes. What We Are Requesting Expedited review of our October 19 submission, considering the critical gameplay issues affecting our live service. Confirmation of the current review status. Guidance on any additional information or actions required from our side. We understand and respect Apple's App Review Guidelines and review process, and we have made every effort to respond promptly to the feedback provided. We apologize for the urgent request and would sincerely appreciate your assistance in reviewing this critical bug fix update as soon as possible. Thank you for your time. We look forward to your response.

Hello, our first app, CardQuest: Trading Card Binder (iOS 1.0), was submitted on October 14, 2026 together with one subscription group and two auto-renewable subscriptions, and has been in "Waiting for Review" since. An expedited review request on October 19 received no reply, phone support is unavailable, and there are no messages in App Store Connect or email. All agreements are active. Could someone from App Review please confirm the submission is queued correctly or let us know if anything is needed from us? Thank you!

Adding my post to the pile in hopes someone at Apple is looking here. My app, which is set to release a week from now has been waiting in review for about 8 days. I submitted a support ticket and holding off on an expedited request (for whatever good that would do) for my final release. My app is just a simple paid game. No in app purchases, logins, or data. I am as frustrated as everyone else here on Apple's miscommunication on how long a review is supposed to take. Their documentation states 90% of reviews complete within 48 hours. If we are the lucky 10% woohoo lets all go buy a lottery ticket, but with that estimate they give us, I would assume, and I believe others do to, that you should be in a review queue no longer than a week at most. I understand if they are overwhelmed with submissions, but they need to give us developers an accurate time estimate so we can plan accordingly. From reading what other people have posted here experiencing this issue, I have a theory that apple has a triage system that prioritizes apps from developers in good standing that have released an app before, or apps that have had no previous rejections. The common thread I seem to see here is that people who are waiting a long time are first time app store devs and/or are resubmitting after a rejection. This also my situation. I now at the end of the day all we can do is wait and I am just posting this to vent, hope the volume of complaints eventually causes apple to change something, and see if making a post helps push my review foward in any way. I'm probably already going to miss my deadline because even though i fixed the issue in my resubmit, I already have another update with a lot more change I will need to submit again right after. it has been cathartic reading everyone else post knowing I am not alone in this, good luck to everyone and i hope you all get approved eventually!!

Is anyone else facing this problem? For the last hour or so, I've been unable to submit new screenshots. We have an iPhone app update with Duo support ready to submit, but can't get the screenshots to upload. Every attempt results in "Your file couldn't be saved. Try again. If the issue persists, contact us." I've even tried uploading my known, good screenshots from an already updated / approved Duo app with the same error, so it's not an issue with my specific screenshots. I've tried private browsing, Chrome, Safari, logging out, etc. No luck. Anyone else seeing this?

Hi everyone, I submitted my app for App Review on August 14, 2026, at 2:39 PM. I later submitted an updated version again on September 9, 2026. The latest submission has been showing “In Review” for the past 5 days, but I still haven’t received any review decision or additional information from the App Review team. As I understand it, once an app enters the “In Review” status, a review decision is generally provided after the review is completed. However, in my case, the status has remained unchanged for several days. Has anyone experienced a similar situation recently? Is it normal for an app to remain in “In Review” for this long, or is there anything I should do from my side? Any advice or guidance would be appreciated. Thank you!

Hi, I'm sure people see this all the time, but it's been approx 3 weeks (23 days) since I submitted my second app for review on App Store Connect. My first one got accepted with no issues after a couple changes. For this app, I first made a review request on Sep 25 and resubmitted after 3 days on Sep 28 as I saw some posts on the forums recommending this. However, Apple recommends the opposite, so I've left my Sep 28 submission untouched and [contacted Apple Support](https://developer.apple.com/contact/) over the past month (email on Oct 10 then another on Oct 19) with zero response or help. I also previously tried to contact Apple in order to change my account from individual -> organization, but got ghosted after I asked a question on the website I needed to submit to begin migrating the account. Is there anything I can do? I'm saving my expedited app review request as I already have some new features and updates my clients want after this initial submission, but it's taking such a long time that it's almost guaranteed my business reputation will be affected. I did warn my clients about this beforehand in person (and in contract) so thankfully they're quite understanding — still crazy though and not sure what to do at this point.

Hello App Review team, Our game Istanbul Taxi: City Driver has been in "Waiting for Review" since October 7, 2026 and has not moved to "In Review" yet. App Apple ID: 6819802943 Version: [1.0] Submission ID: 78962f48-9200-418d-acd6-7d104761acaa Submitted: October 7, 2026 Platform: iOS Agreements, tax and banking are all active, and there are no messages or pending items in App Store Connect. I've been an Apple developer for over 11 years and have never seen a submission wait this long before review. I understand there may be a backlog right now, and I'm not asking for special treatment. I'd just like to confirm that the submission is queued correctly and that nothing is needed from my side. If anything is required, I can respond right away. Thank you.

Hello Apple Developer Support Team, I would appreciate your assistance regarding a prolonged review delay for my app. App Name: Chat Mate for Messenger App ID: 6762255821 My app was previously rejected, and after addressing the review feedback, I resubmitted the update. However, it has now been 14 days and the app remains in "Waiting for Review" status without any further communication or review activity. This project is extremely important to me and my team. We have worked diligently to resolve all issues raised during the previous review and are very eager to launch the app. The extended delay is significantly impacting our planned release schedule and ongoing work. Could you please investigate the status of this submission and help move the review process forward if possible? We would greatly appreciate any update or assistance in getting the app reviewed and, if approved, made live as soon as possible. Thank you for your time and support. Best regards, Muhammad Ahmed

Hello Apple Developer Community, My first iOS app, PitCaptain, has been stuck in “Waiting for Review” since October 7, 2026. App: PitCaptain Version: iOS 1.0.0 (build 10) Submission date: October 7, 2026 Current status: Waiting for Review Expedited review: Requested Contacted Apple Support: Yes The app has not moved to “In Review”, and I have not received any feedback or requests for additional information. PitCaptain helps endurance racing teams plan driver changes, driving stints, refuelling windows and driver-change alarms. I understand that review times can vary, but nine days without any status change is concerning, especially after requesting an expedited review. Could someone from App Review please check whether the submission is progressing normally or whether it may be stuck in the review queue? Any advice or assistance would be greatly appreciated. Thank you!

Hello Apple Developer Community, I am seeking advice regarding the review timeline for our initial iOS application, GoldEngine AI. Our app was submitted on 4 October 2026 at 11:12 AM and has remained in "Waiting for Review" for seven consecutive days. Application details: App: GoldEngine AI Apple App ID: 6818722861 App Store version: 1.0 Current status: Waiting for Review Submission date: 4 October 2026 We contacted Apple Developer Support on 8, 9 and 11 October. We have not yet received clarification on why the submission remains pending. Meanwhile, subsequent builds have been successfully processed and made available through TestFlight. However, the outstanding initial submission prevents us from progressing with the standard App Store release and update process. I have noticed several recent discussions describing similar delays, ranging from approximately 4 to 16 days. I understand that review times vary and that Apple may require additional time for individual submissions. I also recognise that Apple Developer Forums are not an official channel for investigating individual App Review cases. I would appreciate guidance from developers who have experienced this situation: Have you encountered comparable review delays during October 2026? Did your application eventually enter review without further intervention? Did requesting an expedited review help, or did you simply continue waiting? Is there a recommended way to verify that a submission remains correctly queued without withdrawing and resubmitting it? We are keen to avoid unnecessarily resetting the review process. Thank you for sharing any relevant experiences or practical guidance. GoldEngine AI HealthyHedgehogs Ltd

Hi App Review team, Our app has been in "Waiting for Review" since October 4, 2026, with no status change and no message in the Resolution Center. App name: Hangpost Apple ID: 6784063100 Version: 1.0.0 (build 49) Submitted: October 4, 2026, 5:51 PM ET Submission ID: 82c9fd8e-b56e-4491-afbd-f4295573edae Release option: Manual release What we've done so far: Checked the Resolution Center and our developer account email regularly Submitted an expedited review request through Contact Us Kept the build and metadata unchanged so as not to reset our place in the queue Two demo accounts with fixed sign-in codes are in the Sign-In Information, and the review notes explain the sample content and how to test account deletion. If anything about the submission needs to change, we're happy to fix it right away. We'd appreciate any update on its status. Thank you!