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

Hi all, Long wait times. No responses from Apple Developer Program. Maybe we can find support in the broader professional community instead of trying to get in touch with Apple Developer customer service via these forums? Should we take our thoughts to X or LinkedIn? Emails to Apple Developer Support go seemingly unnoticed, I am not sure if they actually even monitor the inbox. I think it would be better to have a voice outside of these forum walls so that they may have potential to actually be heard. Respond here if you want to connect on LinkedIn or X (twitter) and see if we're able to get ANY SORT OF RESPONSE AT ALL from anyone at Apple Developer which we paid money to be able to access.

Hi, Quizadero 1.1.0 went to App Review on October 27, 2026, and eight days later it still shows "Waiting for Review". In the meantime we asked for an Expedited Review twice, on separate days. Neither request produced a confirmation email or any reply, so we can't tell whether they were received. The wait is holding up our release plans. Submission: App: Quizadero (Apple ID 6813638656) iOS, version 1.1.0, build 9 Submission ID: cfc0cff6-d34c-4298-a879-d03bc1cc1685 Submitted: Oct 27, 2026, 11:34 PM The submission contains one item, the iOS app version 1.1.0 (build 9), currently in Waiting for Review. If someone at App Review can check whether our expedited requests arrived, or pass this submission along internally, we'd be grateful. Thanks, Quizadero Team

Hello, My first app, "Terca MIDI" (iOS, version 1.0), together with its first non-consumable in-app purchase "Terca zauvek", has been in "Waiting for Review" since October 22, 2026 – 13 days now. Individual developer account, first app submission Paid Apps Agreement, banking and tax info are all Active No messages in App Review / Resolution Center I requested an expedited review on October 31 but have not received any response Is there anything blocking the review that I should fix on my side, or is this just a longer queue at the moment? Any help from the App Review team would be greatly appreciated. Thank you!

Hello, My app, Fanverse, and its associated In-App Purchases/Subscriptions have been stuck in the "Waiting for Review" status since October 27, 2026. Our team previously received confirmation that Fanverse would receive an Expedited Review. However, this submission has now been waiting for 8 days without any progress. We have already opened support tickets (Case ID: 103014800220) and sent follow-up emails, but we haven't received a human response yet. Our marketing timeline and business operations are heavily impacted by this delay. Could anyone from the App Review or App Store Connect team please look into this case and help us escalate it? Here are the specific details of the submission: • App Name: Fanverse • Apple ID (App ID): dillerlara@hotmail.com • Platform: iOS • Version: 1.0.1 (Build 8) • Submission ID: fde8f13d-4dba-4ed3-9dce-5cf65187ad3a • Submission Date: Oct 27, 2026, 8:00 AM • Support Case ID: 103014800220 Items currently pending review in this submission: iOS App 1.0 (1.0.1 Build 8) - Waiting for Review In-App Purchase (Dorameira Fundadora) - Waiting for Review Subscription Group (Dorameira Apoiadora) - Waiting for Review Subscription (Dorameira apoiadora) - Waiting for Review We would greatly appreciate any guidance or internal escalation to help resolve this limbo. Best regards, Fanverse Team

Hello App Review team, Our app, Detox: Digital Detox, has been live on the App Store for over three years. Until August, our updates usually cleared review within a day or two. Since August, every update has waited about 3 weeks in “Waiting for Review” before being reviewed, even with full review notes and demo access. Current submission App ID: 6450723324 Version: 5.0.0 Submitted: Saturday, 31 October 2026 Status: Waiting for Review Support case: 30000004708883 This submission has been waiting for 4 days so far. That is not unusual on its own, but it matches the start of the pattern we’ve seen on every update since August, so we wanted to raise it now rather than wait another three weeks. We met with App Review last week and were told there are long wait times right now. However, Apple has said that updates to existing apps are being reviewed first and average about 14 hours, so our pattern looks like more than the general queue. Could you check whether anything on our account or app is affecting review timing, and let us know if there’s anything we need to do on our side? More details are in the support case above. Thank you for your help.

Hello everyone, I'm building a cloud-based AI mobile app development platform called TryAppnetic (https://tryappnetic.com), where users can generate React Native/Expo applications and publish them under their own Apple Developer accounts. I'm currently researching how to implement automated iOS app publishing and have some questions regarding the Apple Developer Program License Agreement. Specifically, Section 2.9 appears to restrict third-party service providers from submitting applications to the App Store or using TestFlight on behalf of developers. Section 5.1 also introduces restrictions around certificates and private keys. I'd like to understand what is technically and legally permitted for a platform like ours. Our intended workflow: A user generates an iOS application using our platform. We build the application in our cloud infrastructure. The user authorizes access to their Apple Developer account. We use authorized credentials or App Store Connect API keys to manage the build and upload process. The application is published under the user's own Apple Developer account. My questions: Is it permitted for a cloud-based platform to build and compile iOS applications on behalf of users? Can we automate code signing using certificates and provisioning profiles belonging to the user, provided they explicitly authorize their use? Can we use customer-generated App Store Connect API keys to automate uploading builds to App Store Connect? Does Section 2.9 prohibit automated build uploads as well, or does it specifically prohibit the actual submission of an app for App Store review and TestFlight distribution? Would it be compliant to automate the entire build and upload process but leave the final App Store submission and TestFlight distribution actions to the account owner? I'm particularly interested in hearing from developers who have built cloud-based development platforms, CI/CD services, or automated iOS publishing workflows. I'd also appreciate clarification from anyone familiar with Apple's interpretation of Sections 2.9 and 5.1. Thanks!

Hello Apple Developer Community and App Review Team, I’m seeking assistance regarding an unusual review delay for my iOS application, DoseDue (Version 1.0.1, Build 7). The application was submitted for review on October 30, 2026, and has remained in “Waiting for Review” status without any visible progress. To resolve this situation, I have already taken the following steps: Step 1: Submitted two expedited review requests, with approval confirmed for at least one of them. Step 2: Contacted Apple Developer Support regarding the delay (Case #103015637385). Step 3: Submitted an additional escalation through the official App Review Status contact form on November 3, 2026 (Case #103017881214). Step 4: Sent follow-up emails requesting confirmation that the approved expedited review priority had been applied. Despite these efforts, I have only received automated acknowledgements for the support cases, without any substantive update regarding the application’s review status. Our originally planned launch date is November 6, 2026, and the ongoing delay is affecting our release planning. I would appreciate clarification on the following: Question 1: Can an application remain in “Waiting for Review” even after an expedited review request has been approved? Question 2: Is there a way to verify that expedited review priority has actually been applied to the submission? Question 3: Could someone from the App Review team investigate whether the submission is experiencing an unusual delay or requires any action from the developer? Application Details: App Name: DoseDue Platform: iOS Version: 1.0.1 (Build 7) Apple ID: 6818982362 Submission Date: October 30, 2026 Support Cases: 103015637385 and 103017881214 I understand that review timelines can vary and that expedited review does not guarantee an immediate decision. However, given the approved expedited request and the lack of progress, I would greatly appreciate any guidance or assistance. Thank you for your time and support. Best regards, Aiman Alnajmi

Hello, Our iOS app update has been "Waiting for Review" since October 9, 2026, with no status change or message from App Review. App: LoveYug: Couple Games for Two Apple ID: 6764535507 App Store: https://apps.apple.com/app/id6764535507 Version: iOS 2.0.1 (Build 61) Submission ID: ee368da7-67ea-47b4-af79-6a0b301f3896 Timeline: October 2: Version 2.0.1 was rejected under Guideline 1.1 for a keyword in our App Store metadata. October 3: We removed it from the metadata in every localization, replied in App Review, and resubmitted. October 9: We withdrew the submission to include a new build (61) and resubmitted the same day. November 2: Still "Waiting for Review", with no further questions or issues reported. What we have tried: Requested an expedited review twice Contacted App Review through the Contact Us form Opened two Developer Support cases: 102988518785, 103012593576 None of these has received a substantive response. Our app is already live on the App Store (version 2.0.0), and this update is already live on Google Play. iOS users are stuck on the older version, without the new features and fixes. We fixed the earlier issue the same day and have not changed the binary or metadata since October 9. We are not asking for approval without review. We only want to confirm the submission is correctly queued and not stuck on a hold, or to learn whether we need to do anything else. Could someone from App Review look at this submission or escalate it? Thank you.

Has anyone else run into this? Our app has been in review since late September. The last review on Oct 31 asked for a few changes which we fixed everything, replied in the App Review thread, and resubmitted. Then I realized I wanted to make one more small change and to add the new build, I had to remove that submission and submit again with the updated build. The new submission didn't go into the same review thread. It shows up as a completely separate submission. Our first review took about 3.5 weeks, and I'm worried this one will be treated as a brand new submission and wait just as long. Has this happened to anyone? Did your resubmission keep its place or did the wait start over? Also, is there anything I can do so the reviewer still sees our earlier replies? Thanks so much and I really appreciate it!

Hello, Our first iOS submission has been in "Waiting for Review" since October 6, 2026. The status has not changed, and App Review has not sent us any message. App: Wardify: AI Closet & Stylist Apple ID: 6803264113 Version: iOS 1.1.0 (Build 47) Submission ID: 3ef61ac0-72f7-43c2-817c-0fe01a88c88f Submitted: October 6, 2026, 18:15 UTC This is the app's first version. The same submission includes its first in-app purchases: two auto-renewable subscriptions in one group and three consumable credit packs. All agreements, tax and banking are active, and there are no open messages in App Store Connect. What we have tried: Requested an expedited review Opened a Developer Support case (App Review Status): 103011140929 We have not withdrawn or resubmitted, so that we do not lose our place in the queue. Could someone from App Review look at this submission or escalate it? Thank you.

Hello, Our first app submission has been in "Waiting for Review" since 17 October 2026 with no status change. App name: Gather Expense Apple ID: 6820869711 Version: 1.0 (build 12) Resubmitted for review: 17 October 2026, after answering a Guideline 2.1 Information Needed request with a screen recording and full details (also added to App Review Notes) TestFlight external beta: approved 20 October 2026 (same build) Developer Support case: 103007371511 (24 October 2026) Current status: Waiting for Review There is nothing new in App Review messages, and agreements, tax and banking are all active. Could someone confirm whether this submission is progressing normally or whether it is held? If anything further is needed, I'll provide it immediately. Thank you.

Hi, I submitted my app for review on October 4th, but I haven't received any updates from Apple, and the status is still showing as "In Review." I've tried reaching out to Apple via email but haven't received a response. Does anyone know if there is a phone number I can call to speak with Apple Support or the App Review team directly? I would really appreciate any guidance or suggestions. Thanks!

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?

I have been fighting to get a small app through App Review since October 23 and I am honestly running out of patience. Let me lay out the facts, because at this point the delays have nothing to do with our app. App: Sensoludek (Apple ID 6823115588), a companion app for a small Polish brand of handmade children's educational books. Submission ID: 5fd41009-f25a-413e-a0ba-03dc693afa3b, version 1.0 (23). Oct 23: first submission. Rejected under 3.1.1 because our subscription was sold on our website. We tried the reader app route (3.1.3(a)) with no prices and no links in the app. Rejected twice more under 3.1.1. Fine. We implemented In-App Purchase with StoreKit 2, four auto-renewable subscriptions, restore purchases, terms and privacy links, everything by the book. Submitted on Oct 29. Expedited review requested and granted. Oct 30: rejected under 2.1(b), "cannot locate the In-App Purchases". The reviewer had signed in with the demo account from Sign-In Information, which already had the subscription content unlocked. The Review Notes clearly described a second demo account without the subscription, with its e-mail and password, and explained exactly where the purchase screen is. That paragraph was not read. Oct 30, 22:16 UTC, minutes after the rejection: we moved the second account into the Sign-In Information fields, replied with step-by-step instructions and resubmitted. This was not a code change. It was a form field. Our server logs show the purchase screen being opened on that account four minutes later, so the reviewer could see the subscriptions immediately. Since then: nothing. No message, no status change, "Waiting for Review" for more than 48 hours. An appeal filed with the App Review Board on Oct 28 also has no answer. The "Reply to App Review" window is locked while the status is "Waiting for Review", so I cannot even ask the reviewer what is going on. Meet with Apple has no appointments available until mid-November. Developer Support cannot touch the review queue. There is no official channel left, which is why I am writing here. For comparison: the same app has been live on Google Play since October 26 with zero issues. Every day without the iOS version is a day the brand cannot sell to its customers, and most of them are on iPhones. I would understand a delay if we had ignored the guidelines, shipped something broken, or missed a legal requirement. None of that happened. We are stuck on a demo account field, which was fixed within minutes, and the submission has been sitting untouched for two days. Could someone from App Review please look at submission 5fd41009 and either finish the review or tell us what else is needed? We will answer within minutes. Szymon Miks

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.