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’m looking for some guidance on my first public iOS submission, which is currently in Waiting for Review. I submitted the app two weeks ago, and this is now my fifth round of back and forth with the App Review team solving one concern at a time. The previous reviews were responded to in a couple days, but this one has already taken about twice as long. What’s confusing is that I expected this review to be fairly straightforward. The previous issue was a 5.6 guideline related to a feature of the paywall, and rather than modify it and potentially going through another round of review, I decided to remove that paywall feature entirely. I also included a video with the submission showing that the feature is removed. Submission ID: 20261ce3-65a0-41c8-8e2f-db622795a475 Apple ID: 6762278821 I also submitted an expedited review request about two days ago using Apple’s official form. The timing is important because I planned the app’s launch with the start of the school year, and each additional day in review pushes it further past that window. Is there a way to confirm whether the expedited review request is actually on file? I was under the impression that expedited reviews normally required some kind of justification, so I’m not sure if my request went through correctly. I’ve also tried reaching out to Apple by both phone and email regarding the submission, but so far I haven’t been able to get any assistance. If someone from the App Review team is able to take a look at the submission, I’d really appreciate it. Thank you.

App: AI RunCoach — App ID 6782097197, bundle ID com.airuncoach.app, Team ID 4N3X74Y2LF When adding a new build to our External Testing group, TestFlight shows: "Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership." Our membership is not expired: the Membership Details page shows renewal date 20 June 2027, auto-renew ON, and the €99 fee already paid. We've also checked Agreements, Tax, and Banking — nothing shows as pending or requiring action anywhere. In the meantime, our app has been stuck in "In Review" status since August 3, and TestFlight installations also seem to be blocked. A request for an expedited review produced no result, and a request for a phone consultation did not lead to any contact either. Did anyone else experience this, and could someone advise on how to contact Apple about this? Thanks in advance for any pointers.

Hello, I apologise for posting here. I know this forum is not a support channel, and I would not have posted if I had another way to reach App Review. Apple ID: 6759336435 Submission ID: 59a73f4a-e83b-4fa4-96dc-4c4b6a0ebcc4 Version reviewed: 1.0 (3) In review since: August 10, 2026 Rejection received: August 20, 2026 Our first submission was rejected under Guideline 4.3(a), on the basis that the app shares a similar binary, metadata or concept with apps previously submitted by a terminated Apple Developer Program account. We have no connection to any terminated developer account. RocketIO is not related to any other app, including the other apps on our own account. It is a separate product that we have been designing and writing for several years, on a different technical foundation: 114,817 lines of Dart across 139 files in Flutter, plus the Swift we wrote for the iOS tunnel host and the Network Extension, 187 tests, and 32 fully translated languages. We believe the binary match is a false positive. RocketIO statically links a publicly available open-source proxy core, as every app in this category does. That core is the largest part of the compiled binary, so any two apps linking the same open-source library will share a large amount of identical compiled code no matter how different their own source is — exactly as apps linking OpenVPN or WireGuard do. We cannot remove it, because it is the reason the app exists. RocketIO is also a bring-your-own-configuration client rather than a VPN service. It ships with an empty server list and does nothing until the user supplies a configuration for infrastructure they already own. We operate no servers, sell no subscriptions and carry no traffic. Among the protocols we have implemented are several that very few clients support on any platform, including DNSTT (DNS tunnelling), AnyTLS, ShadowQUIC, Mieru and Juicity, some of them added only recently. We replied in Resolution Center with all of this in detail, and asked which app or account the similarity was matched against, so that we could respond to the specific finding rather than guess. We are still waiting for a response. We have deliberately not resubmitted. We did not want to place another submission in the queue while this conversation is open, and we did not want to send back something that could reasonably be read as unchanged. We have been waiting since August 10, and we will be honest that it has been a difficult wait. We put years of work into this app and we have users who are looking forward to it, and at the moment we cannot tell them anything, because we do not know what specifically we are being asked to change. Could someone from App Review please reply to us there? We are glad to provide our source repository and its full commit history, to take a call at any time convenient to you in English, and to demonstrate the app live. Thank you for your time.

Hello, I apologise for posting here. I know this forum is not a support channel, and I would not have posted if I had another way to reach App Review. Apple ID: 6799505220 Submission ID: 0a07b03d-56c9-45b4-b9b2-7ecbeb9ada0e Our submission was rejected under Guideline 4.3(a). We investigated and found the cause on our side: a server-side configuration fault meant the reviewed build was served the shared server pool used by our other apps, so it displayed a worldwide server list it was never designed to show. The finding was correct for that build. It was a defect, not the product. We have corrected it and verified the correction, and the corrected build is uploaded and attached to the version in App Store Connect. We have deliberately not pressed Submit for Review. We did not want to place another submission in the queue and take review time from other developers while this conversation is still open, and we did not want to send back something that could reasonably be read as unchanged. We would rather agree the right next step with App Review first. We replied in Resolution Center with all of this and are still waiting for a response. Could someone from App Review please reply to us there? Thank you for your time.

Hi everyone, I submitted my new dating app and requested an expedited review because we have a launch event planned in a couple of days. Apple accepted the expedited review request, but the app is still “Waiting for Review.” If it isn't reviewed in time, we'll unfortunately have to cancel or postpone the event. Does anyone know if there is a way to contact the App Review team or a reviewer directly, or an email/support channel I can reach out to about the status of an already-approved expedited review?£ Thanks!

Hello Apple Review Team, I am trying to submit an urgent app update to fix a critical issue, but I am blocked by the following error message: You’ve reached the maximum number of submissions allowed in review for this platform. To submit another, wait until one of your existing submissions has been reviewed or remove one from review. This is happening because I submitted two Custom Product Pages a few days ago, which are currently pending approval. Unfortunately, there is no option for me to cancel these submissions on my end. Here are the Submission IDs for the pending pages: Submission ID: 81a13cdc-1ea9-4fd1-a40f-31f3ae88f2bd Submission ID: 82732b38-ad4f-4e70-aeee-de7aef9459da Could someone please help clear, cancel, or expedite the review for these two Custom Product Pages? I need to submit my urgent app binary release as soon as possible to resolve the issue for my users. Thank you for your time and assistance.

I'm trying to submit my app's first-ever subscriptions for review, and I'm stuck in a loop between two different App Store Connect submission flows that seem to conflict with each other. Setup: App: HeyFlat (bundle au.com.heyflat) Subscription group "HeyFlat Casa" with 3 auto-renewable subscriptions (monthly/semiannual/annual), all status "Ready to Submit" App version 1.0 has been rejected multiple times (most recently for Guideline 2.1(b) — "In-App Purchase products have not been submitted for review") What I've tried: On the Subscriptions page, I click "Add for Review" on the subscription group → it opens a "Draft Submission" panel (breadcrumb "Submissions") listing the group as an item ready to submit. That panel shows: "Unable to submit for review — Add an app version for the selected platform." I uploaded a brand-new, never-before-submitted build (build 31, version 1.0) via CI and manually attached it to the App Store version page (Distribution → App Store Version 1.0 → Build). Went back to the Draft Submission — same error persists, plus a new one: "New subscription groups must be submitted with an auto-renewing subscription from that group." The item listed is just the subscription group itself, not the individual subscriptions. Separately, the legacy per-version thread (App Review → iOS Submission) now shows build 31 as "Ready for Review" — but that thread only lists 1 item (the app version itself), no subscriptions attached, even though they're marked "Added for Review." So I have: a subscription group with 3 ready subscriptions, and a fresh unreleased build attached to the app version — but no path in the UI actually lets me submit them together. This exact same "In-App Purchases not submitted" rejection has now happened twice, with the subscriptions in this same "ready" state both times. Has anyone run into this specific mismatch between the "Submissions" draft flow and the legacy per-version "App Review" thread? What's the correct way to get a first-time subscription group submitted alongside an app version right now?

Hello, My app, Pulse Blocks: Block Puzzle, iOS version 1.0, was submitted on August 14, 2026 at 12:52 PM and has remained in Waiting for Review for more than 6 days. It has never moved to “In Review”. I have not received any rejection, request for additional information, or indication that action is required from my side in App Store Connect. I have also contacted Apple Developer Support, but I have not received a response yet. Could someone from App Review please confirm whether this delay is expected or whether the submission may be stuck in the review queue? I’m happy to provide any additional information privately if required. Thank you.

I was encountered this issue when i want to change the app screen shot in the appstore connect. The screenshot image files were uploaded to appstore connect successfully and display properly. But after a while, all that images turn into error and display the message 'One or more screenshots are in the wrong format'. Checked in the developer help, the resolution was correct. I have no idea, what is the issue i encountered.

Hello everyone, I submitted an app to App Store Connect on August 18th, and it has been stuck in the "Waiting for Review" status ever since. Normally, my submissions are reviewed and resolved within about 2 days, but this time it is approaching the 3-day mark without any status change. Is it normal to wait this long in the current queue? Has anyone else noticed a recent slowdown in review times, or should I consider rejecting and resubmitting the binary? Thanks in advance for sharing your experiences!

We are experiencing an issue when inviting a user to join our Apple Developer Program team through App Store Connect Users and Access. The purpose of adding this user is to include them as an internal TestFlight tester after the invitation is accepted. The invited user received the Apple Developer invitation email and clicked the "Accept invitation" link. The invitation link opens the following page: https://appstoreconnect.apple.com/activation_ds?key=... The page displays "Sign in to accept your invitation" and asks the user to sign in with an Apple Account. After the user signs in successfully, the page redirects back to the same sign-in page and asks the user to sign in again. The invitation cannot be accepted, and the user cannot join the Apple Developer Program team. Steps to reproduce: Go to Users and Access in App Store Connect. Add a new user and send an invitation to join the Apple Developer Program team. The invited user receives the Apple Developer invitation email. The invited user clicks the "Accept invitation" link. The page opens appstoreconnect.apple.com/activation_ds. The user signs in with an Apple Account. After signing in, the page redirects back to the same sign-in page. Repeating the sign-in process results in the same redirect loop. Expected result: The invitation should be accepted after the user signs in, and the user should be added to the Apple Developer Program team. Actual result: The page keeps redirecting back to the sign-in page, and the user cannot accept the invitation. Troubleshooting already tried: Safari and Chrome Private browsing mode Clearing browser cookies Signing out of Apple ID before opening the invitation link again Opening the link directly in the browser instead of an email app embedded browser The issue still occurs.

I paid the $99 annual Apple Developer Program membership fee and submitted my first iOS game, Pippin Plaza, for App Store review on July 21, 2026 at 9:54 PM. Apple publicly states that most app submissions are reviewed within approximately 24 to 48 hours. It has now been nearly 12 days, and my submission is still sitting in “Waiting for Review.” It has never entered “In Review.” There has been no request for additional information, no message from App Review, no explanation for the delay, and no indication that anyone has looked at the submission. I understand that review times can vary and that a first release may sometimes require additional time. However, nearly 12 days without even entering review is far beyond Apple’s publicly stated review timeframe and does not appear to be a normal delay. I contacted Apple Developer Support on July 29, 2026 through the App Review Status support category. Case ID: 20000122288868 Despite contacting support, I have still received no reply, no explanation, and no update regarding the submission. Developers are required to pay Apple $99 annually before they are allowed to distribute apps through the App Store. It is therefore reasonable to expect that a completed submission will at least enter the review process within a reasonable period, or that Apple will communicate when there is a significant delay. Is this currently considered normal for first-time app submissions? At what point should a developer conclude that a submission is stuck rather than merely delayed? Why has there been no response from Apple Developer Support since July 29, despite the submission already being delayed far beyond the stated review timeframe? I am not asking for special treatment, guaranteed approval, or an expedited review. I am asking for my completed submission to enter the review process, or for Apple to explain why it has remained untouched for nearly 12 days.

Hi all, Hoping someone has run into this or has advice. My App Store Connect account is registered as an Individual, with the legal entity/account holder under my name. I added a bank account, but the Account Holder Name on that bank account belongs to a different person than the name on my developer agreement. That other person and I are both Admins on the same App Store Connect team. It's now been well past the standard 24-hour processing window, and the bank account is still showing "Processing," with the usual banner: "Your banking updates are processing, and you should see the changes in 24 hours. You won't be able to make any additional updates until then." Separately, my Canadian GST/HST Form 506 also shows "Missing Tax Info," and my Paid Apps Agreement is "Pending User Info," so I suspect these two issues may be related/compounding. Questions: Has anyone successfully gotten Apple to approve a bank account where the Account Holder Name doesn't match the developer account's legal entity name, when both people are Admins on the same team? If not, has anyone been able to get Apple to cancel/reset a stuck bank account submission so they could resubmit under the correct account holder name? I can't edit it myself while it shows "Processing." Any luck getting a timely response from the Financial Information contact form specifically, versus general Developer Support (which just redirected me to documentation)? Appreciate any insight trying to avoid this dragging on for weeks like I've seen in a few other threads here. Thanks!

There were no problems with our bank account until 01.01.2020, all payments were received. Since 01.01.2020 itunesconnect rejected payment claiming that "The IBAN number does not match the account number." Can't find any similar cases here, Mike

Hi everyone! I'm back again! 😄 A few months ago I posted here after submitting my first iOS app, after previously publishing it on Google Play. That experience was really helpful, so I'm hoping to get some advice from the community again. I've just submitted my new app, Vaqui, and it's currently Waiting for Review. Vaqui is an expense-sharing app for groups, mainly designed for trips. For example, three friends travel together and pay for different things: Pepe pays for the hotel. Sandra pays for groceries. Marcos pays for dinner. Everyone participates in different expenses. Vaqui calculates the resulting balances and suggests who should transfer money to whom. The app supports multiple currencies and stores the exchange rate used when an expense is recorded. The important part is that Vaqui does not process or hold money. It doesn't provide a wallet, banking account, payment processing, cards, or financial transactions. If someone owes another person money, Vaqui simply tells them something like: "Marcos owes Sandra $15,000." They make the actual transfer themselves using their bank or payment provider, outside Vaqui. The users can then mark the payment as made/received inside the app so the group knows what has already been settled. This made me wonder about something before the review starts: Would an app like Vaqui normally be considered a financial-services app by App Review, simply because it calculates debts/balances between users? Or is it generally treated as an expense-management / expense-sharing utility as long as it doesn't actually process, hold, or transfer money? I'm asking because I want to make sure I've understood the relevant App Review guidelines correctly rather than discovering during review that I've misunderstood something obvious. 😅 The current App Store Connect information is: App: Vaqui Bundle ID: mobi.todoapp.vaqui Apple ID: 6802352647 Status: Waiting for Review Platform: iOS / Flutter If anyone has submitted an app with similar functionality, I'd really appreciate hearing about your experience. Thanks! Greetings from Córdoba, Argentina 🇦🇷 And yes... once again I'm waiting for that little "In Review" notification. 🤞😂

Hello, My iOS app, Vagus Fit, has been stuck in “Waiting for Review” since August 12, 2026 at approximately 3:46 PM. It has now been about 9 days and the submission has still never entered “In Review.” App: Vagus Fit Version: 1.3.0 Platform: iOS Submitted: August 12, 2026 at approximately 3:46 PM Current status: Waiting for Review Developer Support Case ID: 20000142078727 I already contacted Apple Developer Support through the App Review Status contact form several days ago, but I have not received a response or any update. I have also checked App Store Connect and I do not see any messages, missing information, rejection, or action required from my side. I understand that review times can vary, but this delay is significantly longer than the normal review timeframe. Could someone from Apple please check whether my submission and existing Developer Support case are progressing normally, or escalate the case if necessary? Thank you.

Hi Apple Developer Community, I’m having a serious problem with the Digital Services Act (DSA) trader verification in App Store Connect and I’m hoping someone can clarify what document Apple actually expects. I’m enrolled in the Apple Developer Program as an individual developer and I’m a registered self-employed person (OSVČ) in the Czech Republic. I declared myself as a trader under the DSA. My contact information was successfully provided and verified. Apple’s documentation says: “You’ll need to provide a current document that verifies your business name and address. Acceptable documents include business or legal records.” I provided an official extract from the Czech Trade Register. It is a government-issued document and contains: my full legal name; my registered business address; my IČO (business identification number); my active trade authorization; my registered business activities. The document was issued very recently and clearly contains both the business name and address requested by Apple. However, the DSA verification was rejected again, without any clear explanation of what exactly was wrong with the document. During the verification process Apple also showed “Document Language: English (US)”, although the official Czech Trade Register document is issued in Czech. I have contacted Apple Developer Support multiple times regarding this issue. I have also had a Developer Support case open for this DSA verification, but I still have not received a clear explanation of which requirement my document fails to meet. I was previously told by Developer Support that I could provide an English translation, and that if I did not provide a certified translation, I could allow Apple or a third-party provider to translate the document and accept responsibility for translation errors. My questions are: Has anyone successfully completed DSA trader verification in App Store Connect as a Czech OSVČ / self-employed individual? What exact document did you upload? Does Apple require a certified English translation of a Czech Trade Register extract? If so, what type of certification is accepted? If an official Czech Trade Register extract is sufficient, why would it be rejected when it clearly verifies both the business name and address? I would really appreciate any experience from developers who have successfully completed this verification, especially developers registered as Czech OSVČ. Thank you.

I first submitted my app for App Review on 16 July 2026 and the review process has now been ongoing for more than 5 weeks. During that time, the submission has gone through multiple review cycles. I have made every requested change and answered every question from App Review immediately. The problem is that after waiting several days, I am repeatedly asked a very basic question about how the app works. I answer immediately, but then it takes several more days for the review process to move forward again. I have also: Contacted Developer Support multiple times Opened support case 20000135457439 Had the submission added to the expedited review queue Been told by Developer Support that review times are currently “extremely extended” At this point the submission does not appear to be progressing toward a final decision. Each basic information request seems to result in another lengthy delay before anything happens. Submission ID: 27e289bf-307a-44e9-a285-d8ad94f82be1 Could an Apple App Review staff member please check whether this submission is stuck and escalate it if necessary?

I’m trying to determine the supported submission path for the first non-consumable IAP in a watchOS-only app. Configuration The app uses a standard watch-only container: Container: com.seanfu.safe Watch app: com.seanfu.safe.watchkitapp ITSWatchOnlyContainer = true WKWatchOnly = true WKApplication = true It offers one non-consumable “Full Version” unlock and uses StoreKit 2: Product.products(for:) Product.purchase(options:) Transaction.currentEntitlements Transaction.updates The product ID in the Release binary exactly matches App Store Connect. Paid Apps agreements, banking, tax, pricing, and territory availability are active. The Release archive contains no local .storekit configuration or test bundle. TestFlight works, but App Review receives no product In TestFlight, using the real App Store sandbox and App Store Connect product configuration, Product.products(for:) returns the correct product, localized price, and title. The purchase sheet can be presented. During App Review, the same request repeatedly returns an empty array without throwing an error. The reviewer sees this application-defined diagnostic: IAP-L-01(empty x5) This is not an Apple or StoreKit error code. It means: Five separate Product.products(for:) calls completed without throwing. Every call returned an empty product array. The diagnostic appears only after the initial request and limited retries are exhausted. Thrown StoreKit errors use different diagnostics. The app does not locally filter a successfully returned product. Therefore, the screenshot means StoreKit returned no matching product in five consecutive requests. This has happened in multiple review attempts, while the same Release code path works in TestFlight. An App Review representative contacted us and explicitly stated that a watchOS-only app can be reviewed and tested with IAP. They suggested investigating our StoreKit integration, but our audit found no code path that could transform a non-empty response into this diagnostic. Submission behavior changed Earlier watchOS-only builds could be submitted with both: The app version The “Full Version” IAP Those submissions reached App Review, where the product was empty: Submission accepted → Review starts → Product array is empty For build 23, we explicitly added the In-App Purchase capability to the Watch target in Xcode. The project now records the IAP capability and explicitly links StoreKit.framework. This did not add an IAP entitlement to the signed app. The bundle IDs, watch-only packaging, product ID, StoreKit code, pricing, availability, agreements, banking, and tax status remained unchanged. After uploading build 23, App Store Connect no longer allows the app version and IAP to be submitted together. The draft contains: iOS App 1.0, build 23 The “Full Version” non-consumable IAP App Store Connect blocks the submission and says IAPs and subscriptions are not supported on Apple Watch and must be removed from the submission. The behavior is now: App version + IAP selected → Submission blocked before review This timing does not prove that adding the Xcode capability caused the change. App Store Connect may have changed its validation, or the new build may have caused its watch-only classification to be reevaluated. However, the transition is notable: earlier submissions were accepted but the product was unavailable during review; the current submission is blocked entirely. Contradictory documentation StoreKit documentation says the Swift IAP API is available on watchOS 8+: https://developer.apple.com/documentation/storekit/choosing-a-storekit-api-for-in-app-purchases The documentation for purchase(options:) specifically says to use it for apps running on watchOS: https://developer.apple.com/documentation/storekit/product/purchase(options:) However, App Store Connect documentation says IAPs are not supported on Apple Watch and must be removed before submitting an Apple Watch app version: https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase/ The same page says the first non-consumable IAP must be submitted with a new app version. This creates a circular requirement: The first non-consumable IAP must accompany an app version. An Apple Watch app version cannot include an IAP. A watchOS-only app therefore appears unable to submit its first IAP. Questions What is the supported path for submitting the first non-consumable IAP of a watchOS-only app? Can Apple review the first IAP separately, or apply a backend override, despite the requirement to include it with an app version? Is an iPhone companion app required, with watchOS IAP support intended only for Watch apps associated with a regular iOS app? Could the unsupported submission association explain why TestFlight sandbox returns the product while App Review receives an empty array? Why were earlier watchOS-only submissions accepted with the IAP attached, while build 23 is blocked despite unchanged bundle IDs and watch-only packaging? Does App Store Connect use the Xcode IAP capability or explicit StoreKit linkage when validating the submission? Clarification from a StoreKit or App Store Connect engineer would be greatly appreciated. The StoreKit documentation, App Store Connect validation, and guidance from App Review currently describe different behaviors.

Hello App Review team, I am requesting urgent assistance with my app review. Our previous build was approved around 5 weeks after our expected launch date, and last week we had to resubmit with a couple bugs that were fixed during the last review process. It has been 6 days since that submission, with an expedited review, and we are now 6 weeks past our launch date which has resulted in financial losses and dozens of media outlets notified weekly of delays. We would really appreciate if our latest build can be approved, as there are only minor bug fixes since the last one. Apple ID: 6748958042 Original Submission Date: 06/30/2026 Latest Submission Date: 08/14/2026 Current Status: Waiting for Review Support Case #: 20000141845140 Given the previous approval and minor changes since that build, we would greatly appreciate any escalation or update on the status of this review as we are incurring daily losses due to the review delay. Thank you!