Hello, We are preparing to submit our banking application to the App Store and would appreciate some guidance regarding our review and release process. Due to our organization's deployment process, we plan to submit a production build that is configured to connect to our UAT backend during App Review. This will allow the App Review team to test all functionality using dedicated test credentials. After the app is approved, we intend to submit another build that is identical in functionality but configured to connect to our production backend before releasing the app to customers. A few questions: Is this approach acceptable under the App Store Review Guidelines? Has anyone successfully followed a similar workflow for enterprise or banking applications? Since the second submission would primarily change the backend environment (UAT → Production), is it generally reviewed as a normal update, or is there anything we should be aware of? Our planned public launch is 7 September 2026. Is there any recommended approach to help ensure the production update is reviewed before the launch date? We understand review times cannot be guaranteed. Due to our bank's security policy, our UAT environment is available only from 10:00 AM to 10:00 PM IST (Indian Standard Time). Is mentioning this in the App Review Notes sufficient, or is there a better way to communicate these testing hours to the App Review team? The app will be fully functional during review, and we will provide complete test credentials and any other information required by the App Review team. We appreciate any guidance or best practices from Apple or developers who have gone through a similar review process. Thank you!

Hello Apple Developer Community, I'm reaching out regarding an urgent matter that requires immediate attention from the App Review team. SITUATION: Our production mutual TLS (mTLS) security certificate expires on August 15, 2026 — only 11 days away. We have submitted version 4.3.1 of our iOS app (Mibanco) which includes the mandatory certificate renewal implementation. WHAT WE'VE DONE: ✅ Implemented dual-certificate coexistence for safe rotation ✅ Tested v4.3.0 thoroughly in TestFlight production ✅ Validated mTLS authentication without errors ✅ Confirmed backward compatibility with legacy systems ✅ Zero user-facing impact OUR REQUEST: We need HIGH PRIORITY review and approval of v4.3.1 before August 15, 2026. This is a critical security infrastructure renewal, not a feature release. Submission ID: b148b754-1abe-451e-b4ac-ad285abbc6da Thank you for your urgent attention to this time-sensitive security matter. Best regards, Alberto Adrian Quineche Poma Engineer Mibanco

Hi everyone, I'm wondering if anyone from Apple or other developers has seen a similar situation. My app is currently in Waiting for Review, and there has been no movement for several days. A bit of context: This is the first release of my app. My initial submission was rejected due to a design-related issue, which I addressed. I submitted a new build on August 1 (IST), and it has remained in Waiting for Review ever since. I have already submitted an Expedited Review Request, but I haven't received a response yet. I understand review times can vary, but I'm concerned because I've seen many other apps submitted around the same time already move into review or get approved. Is there currently a backlog in App Review, or is there anything else I should do besides continuing to wait? Any guidance from Apple or developers who have experienced something similar would be greatly appreciated. Thank you!

It has been a week since we submitted our app update, and the app is still in Pending Review. We previously contacted Apple Support regarding this issue and received a case ID via email. However, we have not received any response or update on the status of our case. We also could not find any place to track the case using the case ID that was provided.

We build and operate a management platform for fitness studios — bookings, memberships, payments, class schedules. We're planning the mobile side now and want to get the App Store model right before we build the release pipeline rather than after. What we have One codebase, which we write and maintain. It ships in two configurations from the same source: A marketplace app — every studio on the platform, searchable, with a picker. One binary, one listing, our brand. A per-studio configuration of that same app — identical functionality, with that studio's name, logo and colour palette, pointed at that studio's data. Studios ask for the second because they want their own presence in the store. Each one is a real business: real class schedules, real bookings, real payments taken by that studio, real members using it weekly. What I'm unsure about 4.2.6 Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content. I can read that two ways and I'd rather ask than guess: (a) It targets app-builder products, where the customer assembles an app themselves from a toolkit and the vendor's product is app generation. We aren't that — customers never touch a build tool, and the app is our own software that we develop, update and support. (b) It applies to any per-client build regardless, in which case each studio needs its own Apple Developer account and submits with us added to their team. Questions Which reading is right for a SaaS product where the vendor writes and operates the app, and the client supplies business data rather than an app? If per-studio builds can be published under our own developer account, is there anything specific you'd want to see in the submission or the App Review notes to make that clear? Separately from 4.2.6 — what makes per-client apps sufficiently distinct under 4.3? This is the part I'm least sure about, because it reads as a judgement about the pattern across many apps rather than about any one of them, and I'd rather design real differentiation in now than discover the line at app number fifty. Is "same functionality, different business, own branding, own data" enough, or is more expected? Does the aggregated / picker option in 4.2.6 change the answer if we ship it alongside? We're building the marketplace app regardless, so both would exist. Happy to give more detail on the product. I'd rather build the right pipeline once than appeal a rejection later.

Hello Apple Developer Community, I'm reaching out regarding an urgent matter that requires immediate attention from the App Review team. SITUATION: Our production mutual TLS (mTLS) security certificate expires on August 15, 2026 — only 11 days away. We have submitted version 4.3.1 of our iOS app (Mibanco) which includes the mandatory certificate renewal implementation. WHAT WE'VE DONE: ✅ Implemented dual-certificate coexistence for safe rotation ✅ Tested v4.3.1 thoroughly in TestFlight production ✅ Validated mTLS authentication without errors ✅ Confirmed backward compatibility with legacy systems ✅ Zero user-facing impact OUR REQUEST: We need HIGH PRIORITY review and approval of v4.3.1 before August 15, 2026. This is a critical security infrastructure renewal, not a feature release. Submission ID: b148b754-1abe-451e-b4ac-ad285abbc6da Thank you for your urgent attention to this time-sensitive security matter. Best regards, Alberto Adrian Quineche Poma Engineer Mibanco

Hi, Our macOS app has been in Waiting for Review since Jul 24, 2026 with no status change. Platform: macOS Version: 1.0 (1) App Apple ID: 6794145764 Submission ID: 5d04a433-b67d-4801-8578-b1ccc3f22d34 Support case: 20000126982226 We also requested an expedited review and contacted support more than once; no reply so far. Our earlier iOS submission was reviewed within a few days. This macOS one hasn’t moved at all. Is anyone else seeing long macOS “Waiting for Review” times right now? Any advice on getting this unstuck, or can someone from App Review take a look? Thanks.

App name: Bromure Client App id: 6793724385 Submission id: 33c98717-eb8d-4b2d-867e-0cc0bf2ef89d My app has been suck in the state of "in review" since 7/31. The credentials provided to test the app have never been used by the Apple team. I emailed support -- never received any answer. Does anyone have any idea on what could be happening? I initially submitted the app on 7/27. How much longer should I expect to wait?

Hello, My app Air Finder - My Device Tracker (Apple ID: 1490211589) seems to be stuck in the App Review process and I'd like to check if something might be wrong with my submission. Timeline: Submission for review: Jul 30, 2026 Current status: Waiting for Review Waiting time: 7 days as of Aug 6, 2026 My app reviews are typically approved within 1-2 business days, so I suppose this delay seems to be unusual. Please help review this submission as soon as possible! I have a timeline for publishing app version that cannot be delayed for this long. Any guidance would be very appreciated. Thank you in advance!

Hi, I submitted Mendo (iOS, version 0.1.0) for App Review on Thursday at 12:39 AM. It’s still Waiting for Review. I had earlier submissions of the same version that I removed myself because I needed to make updates. The current submission is the one I want reviewed. I understood App Review usually takes around 48 hours, but it’s been longer than that for me. Is this delay normal right now, or is there something I should check on my end? Otherwise can I at least get some sort of acknowledgement of some sort to the tickets I've created: - case ID is 20000125052237 case ID is 20000126237735 Thanks.

I am reaching out because my app has been stuck in “Waiting for Review” since July 27, and despite every effort to obtain an update, I have received no response. Over the past several days, I have: Contacted Apple Developer Support by phone multiple times and no response Sent multiple follow-up emails requesting a status update. Unfortunately, I still have not received any update. This delay is causing significant disruption to our launch. We have already committed resources to marketing campaigns, promotional materials, social media announcements, and launch planning based on the expectation that the app would be reviewed within a reasonable timeframe. If there is anything preventing the review from moving forward, or if additional information is needed from my side, I am ready to respond immediately. Developer: thespinu@hotmail

Hello to all1 I have an app currently published on Android and immediately pivoted to publishing the app on Apple, and was pretty excited about the response time from support when signing up for an account. I build the app using RN, so the move to Apple was fairly simple. Works great on my phone. That said, I'm still waiting for Apple to review my app. It's only been 3 days, but Apple says 90% of apps take 48 hours. Is that accurate? I submitted a ticket as well and never received a response.

Hi, Is there a reason why app reviews are taking longer than usual to be completed it has been over a week now since I submitted my app for review.

Our app sells two auto-renewable subscriptions. Product loading succeeds and returns both products with correct localized prices, but every purchase attempt fails roughly one second later with "Item Unavailable". No purchase sheet is ever presented to the user. The app has not yet passed its first App Review. It was rejected under Guideline 2.1(b) because the reviewer encountered this same error on their device. MY QUESTION Under what conditions does StoreKit reject a purchase with "Item Unavailable" for a product that has just been returned successfully, with a valid localized price, by a product request? Is an auto-renewable subscription transactable in the sandbox environment for an app that has never had a binary approved by App Review? Question 2 is the one I most need answered. App Review's rejection states that In-App Purchase products "do not need prior approval to function in review", but neither we nor the reviewer can transact them. DIAGNOSTIC LOG Captured on-device during a failing session: 01:08:56 fetchProducts [com.aurascanner.app.pro.weekly, com.aurascanner.app.pro.annual] 01:08:56 fetchProducts -> 2 product(s): com.aurascanner.app.pro.annual=$39.99; com.aurascanner.app.pro.weekly=$6.99 01:08:56 requestPurchase sku=com.aurascanner.app.pro.weekly 01:08:57 purchaseError: code=purchase-error msg=Item Unavailable 01:08:57 error code=purchase-error, storefront=USA 01:09:05 fetchProducts -> 2 product(s), same prices returned again 01:09:05 requestPurchase sku=com.aurascanner.app.pro.annual 01:09:06 requestPurchase threw: Item Unavailable 01:09:06 error code=purchase-error, storefront=USA An introductory-offer eligibility check earlier in the session also succeeded, using the subscription group ID read from the loaded product. So product metadata, including the subscription group, resolves correctly. CONDITIONS Fails identically for both products, on every attempt. Reproduces in TestFlight on our own devices and Apple IDs. Also failed during App Review on iPad Air 11-inch (M3), iPadOS 26.5.2. Storefront reports as USA in every case. Real devices only. Not reproduced on Simulator. ALREADY VERIFIED Paid Applications Agreement: Active, banking and tax information complete. In-App Purchase capability: enabled on the App ID at Certificates, Identifiers & Profiles. Bundle identifier com.aurascanner.app matches the App Store Connect record. Both subscriptions: complete metadata, review screenshots uploaded, USD pricing set, United States availability. Both subscriptions and the subscription group are attached to the current submission, status "Ready for Review". Subscription group has a localized display name. Build distributed via TestFlight, which routes purchases to sandbox automatically. IMPLEMENTATION The app is React Native and uses a wrapper library over StoreKit 2, but the error text originates from StoreKit rather than the wrapper, and the call order follows the documented pattern: Initialize the StoreKit connection. Load products. This succeeds and returns both products. Register transaction update and error listeners. Request the purchase. This is where it fails. Purchases are verified server-side using Apple's App Store Server Library, and the transaction is finished only after verification succeeds. I am not asking anyone to debug the wrapper. My question is about StoreKit and App Store behaviour: what causes the store to quote a product and then decline to sell it? Any pointers appreciated. I can supply screenshots or the full log.

Hello Apple Developer Support, Our first App Store submission has been in "Waiting for Review" since July 30, 2026, and it has not yet entered the review process. App information App: PigHub Marketplace Apple ID: 6791982179 Version: 1.0.8 (Build 5) We have also opened a Developer Support case regarding this issue, but we have not yet received a response after several days. Support Case ID: 20000126933752 This delay has unfortunately caused us to miss our planned public launch, so we would greatly appreciate your assistance in verifying that our submission is progressing normally. We understand that review times can vary. However, after several days, our submission remains in Waiting for Review without moving to In Review. We have also noticed that several other developers are currently reporting similar delays on the Apple Developer Forums. Could you please confirm that our submission is correctly queued and not affected by any App Store Connect or App Review issue? If there is any additional information or action required from our side, we would be happy to provide it immediately. Thank you very much for your time and assistance.

apple claimed that the game will be after review in 48 hours, i'm waiting for 2 weeks and i feel like i got scammed by apple. this is crazy! no response to emails and opening tickets. no one to talk to! Date Submitted Jul 25, 2026 at 1:17 AM Submission ID a5bd957b-7cd8-409f-a9d1-e3c5652952be

Our game Sand Sort 3D was rejected under Guideline 4.3(a) for binary similarity with our other titles. Three problems: False rejection: it's an original game: its simulation code, shaders and levels exist in no other app. The flagged overlap is shared infrastructure, not content: Unity engine resources, brand fonts, licensed Asset Store packs, and our own internal SDK (sign-in, IAP, ads, cloud save, analytics, consent) that we reuse across our catalogue. On our own audit, engine and font data are the bulk of the overlap; content we designed is ~4%, limited to a coin icon and a settings toggle. No gameplay code, levels, art or design is shared with anything we publish. Insufficient directions: the notice cited 4.3(a) without naming a single element of the app, so we have no actionable way to comply. If it's rejected again, please identify the specific content at issue. Long review times: this rejection has held the release 15 days, and review on this app and our other titles is averaging 10+ days — unusually long. A component-by-component breakdown is attached as appeal; the game is already live on Google Play.

Hello Apple Support Team, I'd like to kindly request an update regarding our latest app submission, which has remained in Waiting for Review since July 30, 2026. As of today (August 5), it has been 6 days without entering the review process. App Information App Name: Dora - AI Video Generator 2 Apple ID: 1604739131 Item for Review: App Version This submission is a major UI/UX revamp that significantly improves the overall user experience. After a long period of maintaining and iterating on the product, we redesigned many core user flows to provide a much more seamless and intuitive experience for our users. Our app continues to receive a large number of daily active users, so having this build remain in Waiting for Review is preventing them from accessing these important improvements and new experiences. The prolonged delay is having a meaningful impact on our users as well as our product rollout. We completely understand that review times can vary, but given the circumstances, we would greatly appreciate it if the review could be prioritized or expedited whenever possible. Thank you very much for your time and support. We truly appreciate the work of the App Review team and look forward to your response. Kind regards,

[Foxify] Version 1.1.1 (13) Review Hello Apple Support Team, My app's new app version and In-App Purchase appear to be stuck in the review process, and I'd like to check whether there might be an issue with the submission. App Information App Name: Foxify AI - Make Your Own Song. Apple ID: 6761515837. Items for Review: New App Version and New Consumable In-App Purchase. Timeline Submitted: July 21, 2026, at 10:57 AM. As of today (July 27), both the app version and the In-App Purchase have remained in "Waiting for Review" for 7 days. Context We submitted a new app version after addressing the issues raised during the previous review. At the same time, we submitted our first new consumable In-App Purchase, which requires the binary build to test the purchase flow, which has also been stuck for a while and has been rejected a few times due to build rejections and the item itself without a clear reason, so the Apple Review team could test the updated purchase flow together with the new IAP. Normally, both our app updates and In-App Purchases are reviewed within 1–2 days, so this delay seems unusual. Please kindly review the submission. Any guidance or assistance would be greatly appreciated. Thank you for your time and support.

Hi, Ive added a new version of my app for review a week ago. Jul 29, 2026 at 10:02 PM. Can someone explain what is taking so long? My new versions before this only took 24-48 hours. Its really difficult to fix and update bug fixes when it takes to long to get approved. Hoping this issue will be resolved quickly