Hello! After uploading a promotional image for an IAP, it appears broken in App Store Connect. We tested it with another app and encountered the same issue immediately after uploading. Could you please advise what might be causing this and how to fix it?

Hello, I am trying to submit my In-App Purchase subscriptions for review, but App Store Connect is preventing the submission. I have already created: A subscription group ("Piscineiros Pro") Two auto-renewable subscriptions All required metadata and review screenshots When I open the draft submission, I receive the following message: "Unable to Submit for Review. To submit your items for review, add an app version for the selected platform." However, my app version (iOS 4.8.3) already exists in App Store Connect and was previously submitted for review. I would like to understand: Do I need to create a new app version and upload a new binary before I can submit these subscriptions for review? Is it possible to associate the existing subscriptions with the currently rejected app version? What specific steps are required to submit these In-App Purchase products together with my app review? Thank you for your assistance. Best regards, Luiz Maueski

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

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, I renewed my Apple Developer Program membership on July 29, 2026. The payment was successfully processed, I received the invoice and renewal confirmation, and the Apple Developer website shows that my membership is active. For approximately one week, App Store Connect has continued to display this error: Developer Program Membership Expired Your membership has expired, and your apps have been removed from the App Store until you renew your membership. To renew, a user with the Account Holder role must sign in and renew the membership on the Apple Developer website. Because of this incorrect status, I cannot submit apps, and App Store Connect states that my existing apps have been removed from the App Store. I have contacted Apple Developer Support multiple times. I received two responses, but neither addressed the App Store Connect membership-status issue. The renewal itself is already complete; the problem appears to be a synchronization issue between the Apple Developer portal and App Store Connect. Has anyone experienced this situation? How long did synchronization take, and was there a specific support team or escalation path that resolved it? Any advice would be appreciated.

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.

Hello all! Have open source iOS application. Is it possible to use In-App purchasing (subscription or any other) for donations? Will it be against any kind of Apple rules? The application have no paid content. Just only donations needed. Will it be passing publications checking? This question isn't about using crowd funding or any other kind of platforms. This question about Apple rules exactly.

Hello, our team is currently in the process of adapting our app for UIScene lifecycle and Liquid Glass. When building with Xcode 26 and iOS 27 Simulator, we see the following message in the console: "UIScene life cycle is now required when building with the latest SDKs. Apps that don't adopt will fail to launch." If we build the app with Xcode 27 without scenes implemented, it crashes on launch as expected. To plan our development roadmap, we would like to clarify the following: 1. Behavior of Xcode 26 builds: Can builds created with Xcode 26 (without UIScene support) still be submitted to the App Store, and will they continue to launch without crashing for users updating to future iOS versions? 2. Xcode 26 submission deadline: Until what exact date will Apple continue accepting App Store submissions built with Xcode 26? Thank you for your guidance!

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.

Hello everyone. I’m trying to submit my first auto-renewable subscription with my iOS app, but can’t associate the subscription with my app version in App Store Connect. Setup: app version 1.0.7 with build attached, subscription group “Premium” with weekly, monthly, yearly. All metadata complete; paid apps agreement active, bank details set, admin access confirmed. Problem: “In-App Purchases and Subscriptions” section is missing on my app version page, so I can’t attach my subscription. Draft error says, “Unable to submit for review. Add an app version for the selected platform.” The draft only lists my weekly plan, not the app version. Questions: why might that section be missing? Are there prerequisites? Has anyone seen this? Any guidance or suggestions would be greatly appreciated.

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.

Hello Apple, Our app "HealiFii Wellness" (Bundle ID: com.healifi.app) was submitted for review on July 29, 2026, and it has remained in "Waiting for Review" status for over one week. We have verified the following: No pending agreements or business requirements. No messages in the Resolution Center. The required DSA declaration has been completed. The app is available for distribution. The build has been successfully validated. Could someone please check if there is any issue with our submission or confirm whether it is still in the review queue? Please let us know if any additional information is required from our side. Thank you.

App: Halo Safe Apple ID: 6756702314 Platform: iOS (update to an existing live app) Submitted: July 27, 2026 Status: Waiting for Review (8 days as of August 4) My update has been sitting in "Waiting for Review" since July 27, 8 full days now, well past the typical turnaround and past every previous review of this app (usually within a day or two). I've checked App Store Connect and can't find anything on my end holding it up: no Developer Action Needed items, no pending agreements, no metadata or export compliance flags that I can see. Meanwhile it's got more complicated: while this has been waiting, I've prepared another build with crash fixes some users are hitting on their devices in the current live version. So the stuck submission is now also blocking crash fixes. I'm worried that If I resubmit it's going to take even longer to get the first batch of updates through. Anyone have any thoughts? How I can get some information?

App update stuck in “Waiting for Review” after replacing an approved build (possible queue issue?) Hello, I would like to know whether other developers are experiencing a similar issue with App Review this weeks. App: Spherag IOT Platform: iOS Current build: 1.2.34 (234) Status: Waiting for Review Timeline Friday, July 24: build 1.2.30 was reviewed and approved successfully. We decided not to release that approved build. Monday, July 27: we removed it from release and submitted 1.2.31 (231). Build 1.2.31 remained in Waiting for Review for about 3 days and never moved to In Review. We then submitted 1.2.34 (234), Today, August 04: after waiting several days with no progress, we removed the submission and re-submitted the same build, 1.2.34 (234), which is currently still in Waiting for Review. I have already opened two Developer Support cases regarding this issue, but I have not yet received a resolution. What concerns me most is that, after submitting build 1.2.34, the version history in App Store Connect appears inconsistent and previous entries are displayed as 1.2.34 (234). This makes me wonder whether there could be a display issue or a problem with the review queue state. All Agreements, Tax and Banking information are active, and all required metadata, privacy details, export compliance and age rating information are complete. This delay is becoming difficult to manage operationally: one release is already blocked, a second release is now waiting, and a third release will likely be ready before the current submission is reviewed. Has anyone experienced a new submission remaining in “Waiting for Review” for several days after withdrawing a previously approved build and submitting a newer build? If so, did it eventually move to review automatically, or was any action from Apple required? Thank you.

App: Halo Safe Apple ID: 6756702314 Platform: iOS Submitted: July 27, 2026 Status: Waiting for Review (8 full days) My update has been sitting in "Waiting for Review" since July 27, 8 days now, well past the typical turnaround and past every previous review of this app (usually within a day or two). I've checked App Store Connect and can't find anything on my end holding it up: no Developer Action Needed items, no pending agreements, no metadata or export compliance flags, and no leftover open submission blocking the queue. Meanwhile, it's got more complicated: while this has been waiting, I've prepared another build with bug fixes for crashes some users are hitting on their devices in the current live version. So the stuck submission is now also blocking crash fixes. Any thoughts?

Hello, We are reaching out because I haven't received any response from App Review for about 220hours, The date We had planned to make my proposal has already passed. App: Apple ID 6782845619, version 1.2 Submission ID: 2722eda8-9429-44d2-9971-092f4ed28ffb Rejection: Guideline 4.3(a) — Design (Spam) I have already taken the corrective steps suggested in the rejection message (I withdrew the duplicate prototype app from review and removed it from all 175 storefronts, so there is no overlap anymore), and I replied to App Review in App Store Connect with this information. However, it has now been about 220 hours with no reply. I understand the review team is very busy, and I truly appreciate their time. I'm not trying to dispute the review process itself — I would simply be grateful if someone could check whether my reply has been received and is being looked at, or advise me on the best way to get a status update. Thank you very much for your help.

Hello App Review Team, I'm reaching out because our submission has been stuck in "Waiting for Review" for over 90 hours with no visible movement, and this is time-sensitive on our side. App Name: Mibanco Platform: iOS Version: 4.3.0 (Build 10000528) Submission ID: 32cbac81-e5f8-43d4-b09f-363d33aba256 Apple ID: [add your numeric Apple ID here] Timeline: Jul 30, 2026, 12:33 PM: In preparation for submission Jul 30, 2026, 12:39 PM: Submitted / Waiting for Review Aug 3, 2026 (today): Still "Waiting for Review" — no rejection, no messages, and no information requests in the Resolution Center Context: this version slot was previously used for a build tied to a certificate-related change. We had to developer-reject that earlier build, which is why the version number jumped from 4.2.x straight to 4.3.0 rather than a normal increment. What we've already tried: Contacted Apple through the general Contact Us form with our Apple ID and submission ID — no response so far. Submitting an Expedited App Review request through the official form alongside this post. Why this is urgent: This release needs to go live before a scheduled backend certificate rotation on our side. Once that rotation completes, the app versions currently live on the App Store will stop being able to authenticate with our backend — so every day this stays in review increases the number of users who will lose access. We understand App Review is handling a high volume of submissions right now and we're not trying to jump the line — we just want to confirm this hasn't fallen into a technical gap, since there's been zero communication in either direction. Any update, or confirmation that it's actively being looked at, would be greatly appreciated. Thank you for your time.

Hi everyone, I'm wondering if anyone else is experiencing unusually long App Review delays. My app has been in "Waiting for Review" since July 22 at 11:04 PM, and it still hasn't entered the review process. As of today, it's been nearly two weeks with no review activity. I understand that review times can vary depending on workload, app category, and other factors, but this is significantly longer than what I've experienced before. Has anyone else recently faced similar delays? How long did your app remain in "Waiting for Review"? Did it eventually get reviewed without taking any action? Did contacting Apple Developer Support help in your case? I'm mainly trying to understand whether this is a broader issue affecting other developers or if I should reach out to Apple Support. Thanks in advance for sharing your experience.

Hello Apple Developer Forum, We have implemented the Declared Age Range API exactly as described in Apple's documentation. Our implementation checks isEligibleForAgeFeatures before calling requestAgeRange, as recommended. We have been testing with different users located in Texas (US) and Brazil. However, for all users, isEligibleForAgeFeatures consistently returns false, so the Declared Age Range prompt is never displayed. We would appreciate some clarification on the following: Under what conditions does isEligibleForAgeFeatures return true? When is the Declared Age Range prompt expected to be shown? Besides the user's region, are there any additional eligibility requirements, such as whether the Apple ID has a verified payment method (credit/debit card), verified identity or address, account age or a phased rollout? Since all of our test users are in supported regions (Texas and Brazil), we expected at least some users to be eligible. However, all four test accounts consistently return false. Could you please clarify how Apple determines eligibility for the Declared Age Range feature and when developers should expect the prompt to appear? Thank you for your guidance.