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

App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.

I submitted my app update(A Slight Chance of Sawblades - 6444032878) for approval for beta testing on the 29th and it was rejected yesterday with just one sentence describing the issue: "Specifically, the app automatically closes after launch." Details about the device type and OS version were left blank. Interestingly, through testing with an internal group via TestFlight, I was unable to reproduce the stated issue, and was able to run the app across a variety of devices, OS versions and accounts without problems. I am writing this post in the hopes to expedite the review and get to the bottom of this problem, because my users are expecting a patch soon to address a specific bug (and I also need the app to match the Apple Arcade version). I'm also recompiling and submitting a fresh build, just in case. Thank you very much.

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.

Hello everyone, I'm an independent developer trying to release my first iOS app, Somnolia. I've already gone through three previous App Review rejections, each concerning a different issue. I carefully addressed the feedback provided by Apple and submitted an updated build on October 14, 2026. Unfortunately, my fourth submission has now been stuck in "Waiting for Review" for 17 days, without any progress or additional communication. Submission details: App: Somnolia Apple App ID: 6794948071 Version: 1.0 (Build 6) Submission date: October 14, 2026 Current status: Waiting for Review I've already contacted Apple Developer Support by phone and opened another support case today, October 31, but I still don't know why the review hasn't started. I completely understand that Apple needs time to review applications, especially after previous rejections. However, I've addressed three separate issues, and I'm concerned that my submission might be stuck in the review queue. Has anyone experienced a similar situation recently? If someone from Apple sees this post, I would really appreciate any guidance on whether my submission is correctly queued or if any further action is needed on my side. I've spent months developing this application independently, and I would simply like to understand what's happening. Thank you for your help!

Hi everyone, I'm looking for some guidance from anyone who has dealt with a similar tax-form issue in App Store Connect. I am a non-US individual and the sole owner of a US single-member LLC. The LLC is treated as a disregarded entity for US federal tax purposes. In App Store Connect, under Tax Forms, I am only presented with the U.S. Form W-9. I am not presented with the questionnaire or any option to complete a W-8BEN. This is particularly confusing because Apple's documentation says that developers based outside the United States may be required to complete a W-8BEN, W-8BEN-E or W-8ECI, and that the appropriate form should be determined through the tax questions in App Store Connect. I contacted Apple Finance Support about this issue and received confirmation that my request had been received: I have an open case with Apple Finance Support since August 26, 2026. I followed up on August 31 and again on September 14, but I have not received any substantive response or update from the Finance/Tax team. I have also found other recent Apple Developer Forum posts describing essentially the same situation: a foreign-owned US single-member LLC where App Store Connect only presents the W-9 workflow and the issue has to be escalated to Apple's tax team. Has anyone here with a similar setup actually managed to get the W-8BEN workflow enabled in App Store Connect? If so: What did Apple ask you to provide? Which Apple team eventually resolved it? Was there a specific escalation path that worked? I am not looking for tax advice — I am mainly trying to understand how others got the App Store Connect tax-form workflow corrected. Thanks in advance.

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

Hi, I am a solo developer with an individual account since 2024. I would appreciate guidance from App Review, because I do not know what else I can do from my side. On October 13 at 00:06 all five apps I had in review were rejected within the same minute under 4.3 and 4.2.6, each with the same nine questions about the app, its audience, beta testing, shared code and templates. The apps are not related: a voice recorder with on-device transcription, a dice roguelike, a tile based dungeon game, a studio simulation game and a Safari extension for cookie banners. I built them myself in Xcode over several weeks and submitted each one when it was finished, which is why they arrived in the same week. No template, no generation service, no client, no third party SDKs, no other accounts. The same day I answered all nine questions in full for four of the apps and withdrew the fifth, the cookie banner extension, to rebuild it. Nine days later there is no response on any of the four threads. On October 21 I submitted the rebuilt extension as version 2.0. It now has consent receipts decoded from each site's TCF record, a public page listing the 100 sites tested before every release with the result for each, a separate mode for subscribe-or-consent walls, Global Privacy Control, Shortcuts and a Mac app. A review video and a public test page were attached. It was rejected within a day under 4.3(a) as sharing "a similar binary, metadata and/or concept" with apps submitted by me or others, with an Extended Review note. The only earlier app with this name is my own withdrawn 1.0. I have stopped submitting anything. My questions: Is there anything more I can provide for the four open threads so a reviewer can look at the apps themselves? I can send screen recordings, source code or demo builds the same day. For the 4.3(a) rejection: what was the app matched against, and what counts as a sufficient difference in this category, given that several cookie banner blockers for Safari were approved in 2026? App IDs: 6821429432 (Voice Notes: Local Transcribe), 6821423492 (Lampfall), 6821275353 (Bone Caster), 6819040142 (Vibe Coder), 6818993189 (Cookie Hide, version 2.0). Thank you for your time. Armen Ter-Oganezov

Hello App Review team and fellow developers, Our Padel Tempo: Padel Score iOS 1.0 submission has been in Waiting for Review for nearly five days after a metadata-only resubmission, and I would like to make sure that nothing else is required from our side. App: Padel Tempo: Padel ScoreVersion: iOS 1.0Submission ID: cbc83032-2f7a-4f80-bc2c-e54a5c9f68b3Resubmitted: October 26, 2026 at 5:04 PMCurrent status: Waiting for Review What happened Our initial submission was reviewed on October 26. We received an automated App Review message regarding the auto-renewable subscriptions Premium Monthly and Premium Yearly. The only issue identified was a missing functional link to the standard Apple Terms of Use (EULA) in the App Store metadata. We corrected the issue immediately: added the standard Apple Terms of Use (EULA) link to the App Description; made sure the required metadata was complete; no binary changes were necessary; resubmitted the same app version approximately 12 minutes after receiving the review message. Since then, the submission has remained in Waiting for Review. Why I am posting I understand that review times can vary, and I am not asking to skip the queue. I would simply like to confirm that: the resubmission is correctly queued for App Review; the previous metadata issue is considered resolved; no additional action or information is currently required from us. Since this was a metadata-only correction following an already completed first review, I wanted to make sure the resubmission did not end up waiting because of something we may have missed. If App Review needs any additional information, screenshots, test instructions, or clarification, I can provide it immediately. Thank you for your time, and I would also appreciate hearing from other developers who have recently experienced longer-than-usual Waiting for Review times. Best regards,MykolaPadel Tempo

I'm genuinely at a loss with Apple's App Review process. Our backend records show that across BOTH reviews, Apple's reviewers did not complete a SINGLE use of our app's core functionality. Not once. ZERO completed generations. For the latest review, our logs confirm Apple successfully logged in, but recorded ZERO generation requests and ZERO credits consumed. This isn't some minor feature. It's the entire foundation of our app. Our app fundamentally changes and becomes personalised as it's used. Without completing that process, you're essentially judging an incomplete product. Submission ID: 6a126514-9bb6-4d91-923c-bf29aacb1b68 Here's why this is so frustrating. We spent months deliberately building an app that offers functionality and a user experience fundamentally different from existing competitors. This wasn't another copycat app - avoiding that was central to its design from day one. We explained these differences extensively in our App Review notes. Yet Apple has rejected us TWICE under Guideline 4.3(b) — Design Spam. We even provided a narrated walkthrough demonstrating exactly what makes our app unique. Our video analytics show ZERO views. So we're being rejected for supposedly lacking originality, despite neither review producing a completed use of our main feature and no recorded views of our demonstration. After both rejections, we've received nothing but generic responses telling us to improve the app, without identifying a single specific problem. How are independent developers supposed to fix something when Apple won't explain what's wrong? We've now filed a formal appeal, which could take a month, with no visible queue position, progress updates or estimated timeframe. Meanwhile, we've already missed multiple planned marketing opportunities, and waiting could mean missing even more. We're not asking for guaranteed approval. We're asking for a fair review of what we've actually built. Has anyone else experienced this? What would you do? Wait for the appeal, hoping the App Review Board properly evaluates the app, even if it takes another month and we miss more deadlines? Withdraw the appeal and resubmit, hoping for a different reviewer, but risking another rejection without proper testing and further warnings against our developer account? I'd genuinely appreciate advice from anyone who's experienced something similar, especially those who've successfully appealed a 4.3(b) rejection. At this point, I genuinely don't know whether this is a reviewer misunderstanding, an automated rejection process, or something else entirely. But how can Apple determine that an app lacks originality when its defining functionality hasn't even been tested?

Hi all, I'm looking for guidance on getting my app back on sale. I've done everything I know to do and I'm not sure what step I'm missing. Details below. Timeline: Aug 16: The app was removed from sale through App Store Notices (ref APP265997). Sept: I renamed the app with a new name, icon, and listing, which was the agreed resolution. Oct 2: Apple lifted the submission hold. Oct 5: The other party confirmed to App Store Notices that the matter is closed and the app can be restored. Oct 7: Version 1.0.4 was approved. App Store Connect shows it as "Ready for Distribution," but the version page also shows a banner: "This app was removed from sale from the App Store." The product page returns "can't be found." I've accepted all current agreements. Oct 20: I submitted 1.0.5 (Manual release). It has been in "Waiting for Review" for 8 days and hasn't moved to In Review. Oct 23: I followed up with App Store Notices and have not heard back yet. My questions: Once an App Store Notices matter is closed, is there a separate step to restore the app to sale, or does App Store Notices lift the removal on their end? Could the removal be why 1.0.5 hasn't entered review after 8 days? Is there a better contact or channel for this than the App Store Notices thread? Any guidance from Apple staff or anyone who has been through this would be a huge help. Existing users can't get the latest fixes, and new users can't find the app at all. Thank you.

Hello, My Digital Services Act trader verification has been "In Review" since 29 September 2026, now 24 business days, well past the 14 business days mentioned in App Store Connect Help. Business > Compliance > Digital Services Act: In Review, last updated 29 Sep 2026 (27 countries or regions) DAC7 compliance: Active since 20 October 2026 Paid Apps agreement, bank account, tax forms: all Active Individual account, based in France No request for additional documents received at any point Support case 103002121516: emails sent on 20 and 28 October, no reply My app [Coucou — Notch Companion] (Apple ID [6817120203]) cannot be distributed in any EU storefront, including France, my home market. Could someone from Apple please check the status of this verification, and whether it may already be approved but not reflected in App Store Connect? 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 Apple Developer Team and Community, I am posting here publicly because I have used every official channel available, and after a month my enrollment issue is still unresolved. My emails have gone unanswered for weeks. What happened On 28 August 2026, I tried to enroll in the Apple Developer Program and got this error: “Your enrollment in the Apple Developer Program could not be completed at this time.” I contacted Developer Support the same day (Ticket: 20000149763302). On 31 August, Apple told me my trusted device or phone number was associated with an existing Developer or Enterprise account. I followed every step they gave me and removed my device and number from all developer accounts. After getting no reply to my follow-up on 19 September, I opened a new case on 23 September (Case ID: 102973162608). On 25 September, Apple sent the same response again and asked for my ID. I submitted my ID the same day and confirmed that my iPhone is not linked to any developer account. On 29 September, Apple confirmed they had “made the necessary changes” to my account and asked me to continue with enrollment. The new problem On 30 September, I tried to enroll again. My national ID (CNIC) does not include a street number, so the system could not accept the address on it. I entered my postal address instead. After two or three attempts, my ID verification was rejected. I reported this to Apple right away. On 3 October, Apple replied with the same trusted-device message as before, even though that issue had already been resolved on 29 September. I replied the same day and explained that this is a completely different problem. Since then: no response at all I followed up on 1, 2, 5, 7, 8, 12 and 28 October and got no reply. On 30 October, I submitted another ticket (Ticket: 103011417221). I have also called Apple Support about six times and used chat support three or four times. Every time I am told the same thing: “We have no direct link to the Developer team. You must contact them by email.” But the Developer team does not reply to email. I have no way forward. This is very shameful behavior from the Apple Developer team. A company of Apple’s size and reputation should not leave a developer completely ignored for over a month, with no reply, no explanation and no way to reach anyone who can help. Why this matters My app is fully developed and ready to launch. I have already invested in marketing, and I am now more than a month past my planned release date. Every extra day of delay adds to my financial loss and puts all of that work and money at risk. My request I am ready to provide any verification Apple needs, including identity documents, proof of address or anything else. And if there is a reason my account cannot be enrolled, I simply ask to be told. Leaving a developer with no reply for more than a month is not acceptable for a company of Apple’s standing. I respectfully but urgently ask Apple Developer Support to: Review Case ID 102973162608 and Ticket 103011417221 Resolve my ID and address verification issue Reply to me with a clear status or the next steps If anyone in the community has faced and solved a similar problem please help me to responsed back how can i get this issue to be solved, I would really appreciate your advice. Thank you, Shaher Yar

Uploading an iOS app built with the public release of Xcode 27.2 (27B52) fails with this error (code 90534 / ITMS-90534 in the upload logs): Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn't supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases. The upload itself completes; the error is returned afterward by App Store Connect when Xcode checks the upload's status, so this looks like server-side validation not yet recognizing the final 27B52 build. As of today, developer.apple.com/news/releases lists Xcode 27.2 RC (27B48) but not Xcode 27.2 (27B52). Archive metadata (app and all extensions match): DTXcode: 2720 DTXcodeBuild: 27B52 DTSDKName: iphoneos27.2 DTSDKBuild: 24B8118 Deployment target: iOS 26.0 No embedded third-party frameworks Uploaded via Xcode Organizer (ContentDelivery 27.10.4-2.2), macOS 27.2 (26B123) Local setup checked: Only one Xcode installed (27.2, 27B52); xcode-select points to it; no DEVELOPER_DIR or SDKROOT overrides Reproduced after a clean build and a fresh archive Upload error IDs: JITIPJCXJDJFKY7RQZS6GAWAGM (Oct 30, 2026) 2D3BNQAYTYPEPADRSCS4XCHZME (Oct 30, 2026, after a clean rebuild) Can Apple confirm whether Xcode 27.2 (27B52) is accepted for App Store submission, or whether builds should use 27.2 RC (27B48) until it is?

Hi all, I submitted an individual Apple Developer Program enrollment several weeks ago, and it’s still pending. I opened a support case (Case ID: 103004160661) and sent a follow-up, but haven’t heard back. What I’ve tried: Replied to the existing case through the Contact page Checked all email folders for document requests (nothing) Tried enrolling through the Apple Developer app on iPhone. “Enroll Now” is grayed out with: “Enrollment through the Apple Developer app is not available for this Apple Account.” Phone support routes back to the web form Is there anything else I can do to get set up? I’m an independent developer ready to ship multiple apps and would appreciate any guidance from Apple staff or anyone who’s been through this. Thanks, Topher Farrell

App Name: Barbro Studio Apple ID / App ID: 6816361007 Platform: iOS Associated Support Case IDs: 102993165132, 103010022185 We are submitting this formal appeal to the App Review Board regarding an abnormal 12-day review delay, persistent queue stall, and the complete absence of developer support communication. Summary of Timeline & Critical Issue: 1. Guideline 4.8 Resolution: In our previous review cycle, feedback was received regarding Guideline 4.8 (Login Services). We made all necessary code and UI adjustments, fully satisfied the guideline requirements, and submitted a freshly updated build on October 18, 2026. 2. 12-Day Unattended Queue: As of today, October 30, 2026, the updated build has remained untouched in "Waiting for Review" for 12 straight days without a reviewer assigned. 3. Prior Delays: Our first submission sat in "Waiting for Review" for 8 days before any reviewer looked at it. In total, our initial launch has now been delayed by over 20 days solely waiting in queues. 4. Unresponsive Support: We have raised and followed up on two official support tickets (Case IDs: 102993165132 and 103010022185) with documented inquiries on Oct 11, Oct 19, Oct 25, and Oct 27. Despite paying the annual Apple Developer Program fee, we have received zero human responses from Apple. Business Impact: This indefinite queue stall has paralyzed our commercial launch, merchant salon onboarding, and public marketing campaign. Request to the Board: We request the App Review Board to: 1. Intervene and investigate why our build is trapped indefinitely in the "Waiting for Review" queue. 2. Directly assign a reviewer to Barbro Studio (App ID: 6816361007) so the review can proceed without further delay. We are ready to provide any additional testing credentials or technical clarifications immediately upon request. Thank you, Kevinkumar Dobariya Founder / Lead Developer, Barbro Studio Team Email: dobariya007kevin@gmail.com

Hi everyone, I submitted my iOS app (Hatırlatıcım) for review on October 13, and it's still showing "Waiting for Review" today, October 26. It's been almost two weeks now, and the status hasn't changed at all. I haven't received any emails or requests for additional information from Apple either. I contacted Developer Support on October 19, but haven't heard back from them yet. I've seen a few other developers mentioning similar delays recently, so I'm wondering if this is a general issue with App Store reviews right now. Has anyone who submitted an app around October 13–14 had theirs reviewed yet? I'm also not sure if I should just keep waiting or if there's anything else I can do at this point. Thanks!

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, We submitted an Unlisted App Distribution request on September 29, 2026 and still haven't received a decision. We seem to be stuck in a loop between App Review and Developer Support. App: Vardım (App Apple ID 6816233538) Unlisted request case: 102979701136 App Review submission: da98301b-fdc5-4d28-a09d-0abe0b1daab2 Timeline Sep 26: App submitted to App Review (version 1.0). Sep 29: Unlisted App Distribution request submitted. Oct 3: Rejected under Guideline 3.2. App Review told us not to resubmit until we receive the unlisted decision by email. Oct 6 and Oct 9: App Review asked us to contact Developer Support via Distribution > Other Distribution Questions. Oct 15: Developer Support said they cannot help with App Review matters, referred us back to App Review, and closed case 102992104513. Oct 21: We asked App Review again in App Store Connect. No reply yet. Oct 22: We opened follow-up case 103004741994 and replied to the Developer Support email. No reply yet. The distribution method still shows Public in Pricing and Availability. We have not resubmitted, as instructed. The app is a workforce attendance app used by employees of several independent organizations on their personal devices. Accounts are created by each organization's administrator. Apple Business Manager distribution isn't practical for us, which is why we requested unlisted distribution. Could someone from App Review or Developer Support please confirm whether our unlisted request is still under review, or tell us if anything is needed from us? Thank you.

Hello App Review team, Our app Bedlo (App ID 6818974374), iOS 1.0.53 (3), has been in “Waiting for Review” since 20 October 2026, 11:05 PM IST. Submission ID: 2b14964f-25bb-401b-880b-b548c474ed33 20 Oct: rejected under Guideline 5.1.1(iv) (camera permission screen). We fixed it and resubmitted the same day, and replied in App Store Connect. Expedited review approved on 15 Oct and again on 27 Oct Support case: 103000787721 (18 Oct) We haven’t removed or changed the build. Could someone check whether anything is blocking this submission or needed from us? Thank you.

Hello, Our app Touki English (Apple ID 6809937929, version 1.3.1, build 14) was submitted on October 16, 2026 and has been in "Waiting for Review" for two weeks, with no message in App Review. The submission contains 7 items: the app, one subscription group with two subscriptions, and three in-app purchases. We requested an expedited review on October 20 and received the confirmation "We'll expedite review for Touki English", but the status has not changed. We contacted App Review through the contact form (case 103004096698) on October 21 and 23, and Developer Support by phone today. Support told us they have no visibility on the review queue. Agreements, banking, tax and DSA trader status are all active, and we have just accepted the updated Program License Agreement. The Android version is already live, and we are running a launch campaign, so this delay is really hurting us. We would be very grateful if someone from App Review could check whether something is blocking this submission, or tell us if we should remove it from review and resubmit. Thank you very much for your help.