Navigate the App Store landscape. Share strategies for app submission, distribution, marketing, and user acquisition. Discuss best practices for getting your app discovered and downloaded.

All subtopics
Posts under App Store Distribution & Marketing topic

Post

Replies

Boosts

Views

Activity

Locate the In-App Purchases and Subscriptions Section in App Store Connect
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.
0
0
2.2k
Jun ’26
First-time subscription submission stuck — "add an app version" error even with a fresh, unreleased build attached
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?
0
0
2
24m
Waiting for Review for over 2 weeks
Hi. I submitted my very first app for review on July 22. After waiting nearly two weeks, I received the 4.3a Spam rejection notice on Aug 4. I cleaned up some of my shared framework code, changed some of my images and explained that no app in the marketplace currently does what I'm trying to do. I submitted my appeal via reply on the review on August 5 and I'm still waiting for review. It's been over two weeks and I don't have any indication that anyone is actually looking at this. Most comments talk about the long wait times but it's been over 2 weeks and I don't know what to do next. Any help would be awesome. Thanks.
2
0
72
42m
App Review Delayed for Over a Month Despite Multiple Submissions and Support Requests
Hello, I’m looking for guidance regarding an unusually long App Review process for my app, Auto Deal. The app was originally submitted on July 2, 2026. It eventually entered “In Review,” but remained there for an unusually long period without any update or decision. After waiting for a long time with no progress, I deleted the submission and uploaded it again. On the second submission, we again experienced a long delay. The app was eventually reviewed and rejected because of an issue that occurred when tapping the “Confirm” button inside the app. I immediately fixed the exact issue identified by App Review and submitted the corrected build. The corrected submission then entered “In Review,” but once again remained there for a long period without any further feedback or decision. After waiting again with no progress, I deleted the submission and uploaded a new build. When the same prolonged delay continued, I deleted that submission and submitted another fresh build. I understand that deleting and resubmitting can restart the review process. However, I only took these steps after repeatedly experiencing unusually long periods in review without any decision or explanation. Throughout this entire process, I have contacted Apple Developer Support multiple times and submitted three expedited review requests, but the issue remains unresolved. The app is complete and already available on Google Play. We have customers waiting for the iOS version, and this prolonged review process has significantly delayed our business launch. I am not requesting another expedited review through this post. I am trying to understand why this keeps happening and whether there is an issue with the app submission, my developer account, or the review process that requires action from my side. If an Apple engineer or App Review representative can look into this situation or advise me on the appropriate next step, I would greatly appreciate it. Thank you.
15
0
1.1k
1h
TestFlight builds expired across multiple apps; new builds cannot be installed (“Requested app is not available or doesn’t exist”)
Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds
25
3
2.3k
2h
Stuck At Waiting For Review
Hello! I am very upset to write this down, but apple keep ignoring the reply i gave them for something they wanted from me on my first app submission. I understand they got some important work to do, but it says that 90% of the people get response in 48 hours. I am waiting for 72 currently and not happy with this. Please do something apple...
0
0
28
3h
First iOS submission stuck in “Waiting for Review” for 6+ days
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.
1
0
128
3h
Guideline 4.3(a): 5 rejections despite major code and content changes
Hi everyone. I’m looking for some advice regarding repeated rejections under Guideline 4.3(a) - Design - Spam. I’m a solo developer and have been making car simulator sandbox games since 2020. I already have an older game in the same genre on the App Store, and I’ve spent around 2 years developing its sequel. The new game is also available on Google Play, where it has passed 1M installs in its first month and currently has a 4.9 rating. The iOS version has now been rejected 5 times over the last 4 months. Attempt 1: Rejected under 4.3(a) with: "We noticed the app shares a similar binary, metadata, and/or concept..." I explained what makes the game different, filed an appeal, added a new feature, and submitted again. Attempt 2: Same rejection. I requested a phone call with App Review. During the call, I was told that their system had detected a "binary match" with another developer’s game in the same genre. The reviewer explained that similarities could come from game code, assets, shared engine code, ad SDKs, third-party libraries, etc. When I asked what I could change, the main advice was to change the code. Attempts 3 & 4: I removed unused code and libraries, changed dependencies, reorganized and refactored parts of the project, and also tried obfuscation. The result was still the same 4.3(a) rejection. After that, I spent around 3 months working on a major update. I updated Unity and dependencies, removed anything unnecessary, added new cars, reworked the physics, reorganized assemblies, changed and renamed large parts of the codebase, and did a substantial code refactor. Attempt 5: After 9 days in review, I received a different 4.3(a) message: "This app still exhibits an app with a spam like template that shows similarities in concept and look with apps already on the app store in a saturated category." This is where I’m confused. The previous feedback focused on binary similarity, while the latest rejection seems to focus on the concept and visual similarity instead. The game is not based on a template. It has hundreds of scripts written specifically for the project, a custom physics engine, custom UI, and many systems and features developed specifically for this game. There are also only a few comparable vehicle physics sandbox games on iOS. I have already used the Review Notes to explain what is new in the sequel and how it differs from both my previous game and other games in the genre. I also appealed the first rejection, but the decision was upheld. At this point, I’m not sure what else I can reasonably change or what exactly is triggering 4.3(a). Any advice would be greatly appreciated. App: Crash Test Simulator 3 Bundle ID: com.FozerGames.CrashTestSimulator3
3
0
94
3h
Launch event in a few days — expedited review approved but still Waiting for Review
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!
0
0
47
7h
One or more screenshots are in the wrong format
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.
14
2
18k
7h
2.1 Information Needed: replied in Resolution Center a day ago, still silent — how long is normal?
First app, first review, so I don't know what's normal here. Submitted 1.0 on August 11. On August 14 it came back Rejected under Guideline 2.1, Information Needed: they asked for a screen recording from a physical device plus written answers about the app. I missed the message for a week, my fault. On August 21 I replied in Resolution Center with the recording and answers to every question. The letter said not to resubmit, just reply from the App Review page, so that's what I did. Since then nothing: still Rejected, still unresolved issues. How long does a Resolution Center reply normally take to get an answer, and does the status change at all when someone picks it up? Did the week I took to reply push me back in the queue? And would resubmitting the same build be faster than waiting, or does that just cancel the conversation and cost me my place? In case anyone from App Review sees this: App Apple ID: 6800427314 Version: 1.0 Submission ID: 9091a840-5818-4767-84ca-4b2c822f93c0 Rejected: August 14, 2026 · Replied in Resolution Center: August 21, 2026
0
0
42
9h
No response to a Resolution Center reply on a 2.1 Information Needed rejection (7 days)
Timeline Submitted: August 10, 2026 - first submission of a new app Rejected: August 14, 2026 - Guideline 2.1 Information Needed - New App Submission Replied: August 14, 2026, about 17 hours later, in the same thread Current status: Unresolved Issues / Rejected, 7 days with no response Submission ID: 5aa5647f-7c12-4949-ba8e-dfba1bad3047 What happened The rejection asked us to reply in App Store Connect with seven specific items, including a recording captured on a physical device running the latest OS. We replied on the App Review page the same day, about 17 hours after the rejection. All seven items were answered in order and the recording was attached to the reply. Both the reply and the attachment are visible in the thread. We also copied the same seven answers into the Notes field of the App Review Information section, as the message asked. Seven days later there has been no response, and the submission is still showing Unresolved Issues. We have not resubmitted. The rejection asked us to reply rather than resubmit, and resubmitting would close the open thread. Questions Does replying on the App Review page put the item back in front of a reviewer on its own, or is a further step required on the developer side? Is seven days without a response typical once an information request has been answered in full? If it is not, what is the correct way to have the reply picked up? App name, Apple ID and Team ID available on request.
2
0
128
9h
App stuck in "Waiting for Review" longer than usual (almost 3 days)
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!
3
0
213
9h
App stuck in "Waiting for Review" for 7+ days — anyone else since the Aug 8 maintenance?
Our update has been sitting in "Waiting for Review" since August 14, 2026 — over 7 days (171 hours as I write this). Details: iOS app, version 3.1.1, build 170 — build is VALID and correctly attached to the version Submission created, release type set to "after approval" No rejection, no Resolution Center message, no request for additional information Developer support case opened Aug 18 — still no reply The app was transferred to a new team (company account) on Aug 14, a few hours before the upload. The only warning we got was ITMS-90076 (keychain access change due to the new team ID), which is expected after a transfer and documented as non-blocking. Context that makes this painful: we have a commercial launch scheduled for September 1 that depends on this update, and the version currently live has bugs this release fixes. Questions for anyone in the same boat: Has anyone seen 7+ day waits specifically since the August 8 maintenance? Several threads here suggest a backlog. Did an app transfer right before the upload put your submission in a slower lane? That is the one thing that makes our case unusual. For those who eventually got through: what actually moved it — expedited review, a support case, or just time? (We already used an expedite earlier, so we would rather not burn another one.) Not looking to vent, just trying to figure out whether this is the general backlog or something specific to our submission that we could fix on our side.
1
1
130
9h
Expedited Review Request is taking a long time — any advice?
Has anyone experienced Apple App Review being really slow lately? I already submitted an Expedited Review Request through Apple Developer Support, but it still seems to be moving really slowly. My app is still stuck on “Waiting for Review.” How long does it usually take after submitting an expedited review request? If the request has already been submitted through Developer Support, is there anything else I can do to get Apple to take a look at it sooner? Or is App Review just slower than usual right now and I basically just have to wait? 😭 Would really appreciate it if anyone who recently got an expedited review could share how long it took for them! My App ID is 6800172081
0
0
8
9h
First iOS release stuck in “Waiting for Review” since July 21, 2026
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.
8
1
632
9h
ITMS-91064 persists across 8+ builds despite verified-correct PrivacyInfo.xcprivacy
I'm getting the following error on every submission (Build 1 through 8), even after multiple clean rebuilds and manual verification of the raw manifest content: ITMS-91064: Invalid tracking information - A PrivacyInfo.xcprivacy file contains invalid tracking information at the following path: "PrivacyInfo.xcprivacy" and also "PlugIns/[WidgetName].appex/PrivacyInfo.xcprivacy" NSPrivacyTracking must be true if NSPrivacyTrackingDomains isn't empty. What I've verified locally (via plutil -p and raw cat on both the .xcarchive and the exported .ipa): Main app PrivacyInfo.xcprivacy: NSPrivacyTracking=false, NSPrivacyTrackingDomains=[] (empty) Widget PrivacyInfo.xcprivacy: same, false + empty No duplicate keys found in either file Generated an official "Privacy Report" from Xcode Organizer - no obvious conflict at the app or widget level was shown Updated GoogleMobileAds/UserMessagingPlatform SDKs to the latest version - issue persists Bundle version increments correctly with each build (confirmed via Info.plist inside the actual uploaded archive) Is there a known caching issue on the App Store Connect validation side, or something else I might be missing? Happy to share the Privacy Report PDF and archive details if helpful.
3
0
73
9h
Bank Account Stuck in "Processing"
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!
2
1
587
1d
Stuck in "Waiting for Review" for 9 days after Aug 13 resubmission — launch committed Aug 28
Dear whom it may concern— We resubmitted our app PALJA (Apple ID: 6794835089) on August 13, 2026, and it has remained in "Waiting for Review" status for 9 days without being picked up. The resubmission addressed a Guideline 3.1.2 issue and included a detailed reconsideration request and metadata update regarding an earlier Guideline 4.3(b) finding in our review notes. So far we have: Submitted an expedited review request (our public launch is committed for August 28, with US marketing commitments in the first week of September) Opened a Developer Support case on the review status (Case ID: 20000141709580) Is there anything we should be doing differently, or a way to confirm the submission is actively in the review queue? Thank you very much for any guidance! Kijun Seo
0
1
388
1d
Another "Waiting for Review"
First time app submission. Business account. Platform: iOS Category: Sports Nothing controversial. No wagering. No adult content. No health-related topics or information. Free app. No in-app purchases. Originally submitted August 8. Included all the standard information. Provided a video walk-through. First review August 14 (six days later). Rejected literally in the same minute the review was opened. Reviewer (?bot) requested additional information. 99% of the information the reviewer requested had already been provided in the original submission. We immediately provided the requested information. August 17 the second review came through. The app was rejected due to "4.3(a) - Design - Spam. - Submitting an app with the same source code or assets as other apps already submitted to the App Store. Creating and submitting multiple similar apps using a repackaged app template. Purchasing an app template with problematic code from a third party. Submitting several similar apps across multiple accounts". The reviewer suggested we "submit a unique app with distinct content and functionality". This made absolutely no sense. We coded the app completely in-house. No third party. No templates. This is the only app we have submitted. We don't have any other accounts. There are literally no other apps that do what ours does. We have two pending patents on the technology. We developed four of our own computer vision models trained on literally thousands of images. The app is completely unique. We provided a detailed response on the same day (August 17), explaining all of the above and attaching our two patent documents. We've worked 9 months on developing this technology and application. The suggestion to just create a new "unique app" seems trite. Four days later, still zero response. It almost feels like nobody is actually reviewing the app at all. At best, they are taking a cursory one-minute look and just hitting reject and moving on to the next developer's submission. Any ideas or suggestions, other than starting a new business and inventing another new technology so we can create a different app as Apple suggests?
0
0
154
1d
Locate the In-App Purchases and Subscriptions Section in App Store Connect
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.
Replies
0
Boosts
0
Views
2.2k
Activity
Jun ’26
First-time subscription submission stuck — "add an app version" error even with a fresh, unreleased build attached
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?
Replies
0
Boosts
0
Views
2
Activity
24m
Waiting for Review for over 2 weeks
Hi. I submitted my very first app for review on July 22. After waiting nearly two weeks, I received the 4.3a Spam rejection notice on Aug 4. I cleaned up some of my shared framework code, changed some of my images and explained that no app in the marketplace currently does what I'm trying to do. I submitted my appeal via reply on the review on August 5 and I'm still waiting for review. It's been over two weeks and I don't have any indication that anyone is actually looking at this. Most comments talk about the long wait times but it's been over 2 weeks and I don't know what to do next. Any help would be awesome. Thanks.
Replies
2
Boosts
0
Views
72
Activity
42m
App Review Delayed for Over a Month Despite Multiple Submissions and Support Requests
Hello, I’m looking for guidance regarding an unusually long App Review process for my app, Auto Deal. The app was originally submitted on July 2, 2026. It eventually entered “In Review,” but remained there for an unusually long period without any update or decision. After waiting for a long time with no progress, I deleted the submission and uploaded it again. On the second submission, we again experienced a long delay. The app was eventually reviewed and rejected because of an issue that occurred when tapping the “Confirm” button inside the app. I immediately fixed the exact issue identified by App Review and submitted the corrected build. The corrected submission then entered “In Review,” but once again remained there for a long period without any further feedback or decision. After waiting again with no progress, I deleted the submission and uploaded a new build. When the same prolonged delay continued, I deleted that submission and submitted another fresh build. I understand that deleting and resubmitting can restart the review process. However, I only took these steps after repeatedly experiencing unusually long periods in review without any decision or explanation. Throughout this entire process, I have contacted Apple Developer Support multiple times and submitted three expedited review requests, but the issue remains unresolved. The app is complete and already available on Google Play. We have customers waiting for the iOS version, and this prolonged review process has significantly delayed our business launch. I am not requesting another expedited review through this post. I am trying to understand why this keeps happening and whether there is an issue with the app submission, my developer account, or the review process that requires action from my side. If an Apple engineer or App Review representative can look into this situation or advise me on the appropriate next step, I would greatly appreciate it. Thank you.
Replies
15
Boosts
0
Views
1.1k
Activity
1h
TestFlight builds expired across multiple apps; new builds cannot be installed (“Requested app is not available or doesn’t exist”)
Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds
Replies
25
Boosts
3
Views
2.3k
Activity
2h
Stuck At Waiting For Review
Hello! I am very upset to write this down, but apple keep ignoring the reply i gave them for something they wanted from me on my first app submission. I understand they got some important work to do, but it says that 90% of the people get response in 48 hours. I am waiting for 72 currently and not happy with this. Please do something apple...
Replies
0
Boosts
0
Views
28
Activity
3h
First iOS submission stuck in “Waiting for Review” for 6+ days
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.
Replies
1
Boosts
0
Views
128
Activity
3h
Guideline 4.3(a): 5 rejections despite major code and content changes
Hi everyone. I’m looking for some advice regarding repeated rejections under Guideline 4.3(a) - Design - Spam. I’m a solo developer and have been making car simulator sandbox games since 2020. I already have an older game in the same genre on the App Store, and I’ve spent around 2 years developing its sequel. The new game is also available on Google Play, where it has passed 1M installs in its first month and currently has a 4.9 rating. The iOS version has now been rejected 5 times over the last 4 months. Attempt 1: Rejected under 4.3(a) with: "We noticed the app shares a similar binary, metadata, and/or concept..." I explained what makes the game different, filed an appeal, added a new feature, and submitted again. Attempt 2: Same rejection. I requested a phone call with App Review. During the call, I was told that their system had detected a "binary match" with another developer’s game in the same genre. The reviewer explained that similarities could come from game code, assets, shared engine code, ad SDKs, third-party libraries, etc. When I asked what I could change, the main advice was to change the code. Attempts 3 & 4: I removed unused code and libraries, changed dependencies, reorganized and refactored parts of the project, and also tried obfuscation. The result was still the same 4.3(a) rejection. After that, I spent around 3 months working on a major update. I updated Unity and dependencies, removed anything unnecessary, added new cars, reworked the physics, reorganized assemblies, changed and renamed large parts of the codebase, and did a substantial code refactor. Attempt 5: After 9 days in review, I received a different 4.3(a) message: "This app still exhibits an app with a spam like template that shows similarities in concept and look with apps already on the app store in a saturated category." This is where I’m confused. The previous feedback focused on binary similarity, while the latest rejection seems to focus on the concept and visual similarity instead. The game is not based on a template. It has hundreds of scripts written specifically for the project, a custom physics engine, custom UI, and many systems and features developed specifically for this game. There are also only a few comparable vehicle physics sandbox games on iOS. I have already used the Review Notes to explain what is new in the sequel and how it differs from both my previous game and other games in the genre. I also appealed the first rejection, but the decision was upheld. At this point, I’m not sure what else I can reasonably change or what exactly is triggering 4.3(a). Any advice would be greatly appreciated. App: Crash Test Simulator 3 Bundle ID: com.FozerGames.CrashTestSimulator3
Replies
3
Boosts
0
Views
94
Activity
3h
Launch event in a few days — expedited review approved but still Waiting for Review
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!
Replies
0
Boosts
0
Views
47
Activity
7h
App Waiting for Reviw
Hi Team, My App is waiting for review for about 11 days, may I know what is holding up. my App id : 6776106885. Request to review and provide your feedback. Swetha Pabolu.
Replies
1
Boosts
0
Views
50
Activity
7h
One or more screenshots are in the wrong format
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.
Replies
14
Boosts
2
Views
18k
Activity
7h
2.1 Information Needed: replied in Resolution Center a day ago, still silent — how long is normal?
First app, first review, so I don't know what's normal here. Submitted 1.0 on August 11. On August 14 it came back Rejected under Guideline 2.1, Information Needed: they asked for a screen recording from a physical device plus written answers about the app. I missed the message for a week, my fault. On August 21 I replied in Resolution Center with the recording and answers to every question. The letter said not to resubmit, just reply from the App Review page, so that's what I did. Since then nothing: still Rejected, still unresolved issues. How long does a Resolution Center reply normally take to get an answer, and does the status change at all when someone picks it up? Did the week I took to reply push me back in the queue? And would resubmitting the same build be faster than waiting, or does that just cancel the conversation and cost me my place? In case anyone from App Review sees this: App Apple ID: 6800427314 Version: 1.0 Submission ID: 9091a840-5818-4767-84ca-4b2c822f93c0 Rejected: August 14, 2026 · Replied in Resolution Center: August 21, 2026
Replies
0
Boosts
0
Views
42
Activity
9h
No response to a Resolution Center reply on a 2.1 Information Needed rejection (7 days)
Timeline Submitted: August 10, 2026 - first submission of a new app Rejected: August 14, 2026 - Guideline 2.1 Information Needed - New App Submission Replied: August 14, 2026, about 17 hours later, in the same thread Current status: Unresolved Issues / Rejected, 7 days with no response Submission ID: 5aa5647f-7c12-4949-ba8e-dfba1bad3047 What happened The rejection asked us to reply in App Store Connect with seven specific items, including a recording captured on a physical device running the latest OS. We replied on the App Review page the same day, about 17 hours after the rejection. All seven items were answered in order and the recording was attached to the reply. Both the reply and the attachment are visible in the thread. We also copied the same seven answers into the Notes field of the App Review Information section, as the message asked. Seven days later there has been no response, and the submission is still showing Unresolved Issues. We have not resubmitted. The rejection asked us to reply rather than resubmit, and resubmitting would close the open thread. Questions Does replying on the App Review page put the item back in front of a reviewer on its own, or is a further step required on the developer side? Is seven days without a response typical once an information request has been answered in full? If it is not, what is the correct way to have the reply picked up? App name, Apple ID and Team ID available on request.
Replies
2
Boosts
0
Views
128
Activity
9h
App stuck in "Waiting for Review" longer than usual (almost 3 days)
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!
Replies
3
Boosts
0
Views
213
Activity
9h
App stuck in "Waiting for Review" for 7+ days — anyone else since the Aug 8 maintenance?
Our update has been sitting in "Waiting for Review" since August 14, 2026 — over 7 days (171 hours as I write this). Details: iOS app, version 3.1.1, build 170 — build is VALID and correctly attached to the version Submission created, release type set to "after approval" No rejection, no Resolution Center message, no request for additional information Developer support case opened Aug 18 — still no reply The app was transferred to a new team (company account) on Aug 14, a few hours before the upload. The only warning we got was ITMS-90076 (keychain access change due to the new team ID), which is expected after a transfer and documented as non-blocking. Context that makes this painful: we have a commercial launch scheduled for September 1 that depends on this update, and the version currently live has bugs this release fixes. Questions for anyone in the same boat: Has anyone seen 7+ day waits specifically since the August 8 maintenance? Several threads here suggest a backlog. Did an app transfer right before the upload put your submission in a slower lane? That is the one thing that makes our case unusual. For those who eventually got through: what actually moved it — expedited review, a support case, or just time? (We already used an expedite earlier, so we would rather not burn another one.) Not looking to vent, just trying to figure out whether this is the general backlog or something specific to our submission that we could fix on our side.
Replies
1
Boosts
1
Views
130
Activity
9h
Expedited Review Request is taking a long time — any advice?
Has anyone experienced Apple App Review being really slow lately? I already submitted an Expedited Review Request through Apple Developer Support, but it still seems to be moving really slowly. My app is still stuck on “Waiting for Review.” How long does it usually take after submitting an expedited review request? If the request has already been submitted through Developer Support, is there anything else I can do to get Apple to take a look at it sooner? Or is App Review just slower than usual right now and I basically just have to wait? 😭 Would really appreciate it if anyone who recently got an expedited review could share how long it took for them! My App ID is 6800172081
Replies
0
Boosts
0
Views
8
Activity
9h
First iOS release stuck in “Waiting for Review” since July 21, 2026
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.
Replies
8
Boosts
1
Views
632
Activity
9h
ITMS-91064 persists across 8+ builds despite verified-correct PrivacyInfo.xcprivacy
I'm getting the following error on every submission (Build 1 through 8), even after multiple clean rebuilds and manual verification of the raw manifest content: ITMS-91064: Invalid tracking information - A PrivacyInfo.xcprivacy file contains invalid tracking information at the following path: "PrivacyInfo.xcprivacy" and also "PlugIns/[WidgetName].appex/PrivacyInfo.xcprivacy" NSPrivacyTracking must be true if NSPrivacyTrackingDomains isn't empty. What I've verified locally (via plutil -p and raw cat on both the .xcarchive and the exported .ipa): Main app PrivacyInfo.xcprivacy: NSPrivacyTracking=false, NSPrivacyTrackingDomains=[] (empty) Widget PrivacyInfo.xcprivacy: same, false + empty No duplicate keys found in either file Generated an official "Privacy Report" from Xcode Organizer - no obvious conflict at the app or widget level was shown Updated GoogleMobileAds/UserMessagingPlatform SDKs to the latest version - issue persists Bundle version increments correctly with each build (confirmed via Info.plist inside the actual uploaded archive) Is there a known caching issue on the App Store Connect validation side, or something else I might be missing? Happy to share the Privacy Report PDF and archive details if helpful.
Replies
3
Boosts
0
Views
73
Activity
9h
Bank Account Stuck in "Processing"
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!
Replies
2
Boosts
1
Views
587
Activity
1d
Stuck in "Waiting for Review" for 9 days after Aug 13 resubmission — launch committed Aug 28
Dear whom it may concern— We resubmitted our app PALJA (Apple ID: 6794835089) on August 13, 2026, and it has remained in "Waiting for Review" status for 9 days without being picked up. The resubmission addressed a Guideline 3.1.2 issue and included a detailed reconsideration request and metadata update regarding an earlier Guideline 4.3(b) finding in our review notes. So far we have: Submitted an expedited review request (our public launch is committed for August 28, with US marketing commitments in the first week of September) Opened a Developer Support case on the review status (Case ID: 20000141709580) Is there anything we should be doing differently, or a way to confirm the submission is actively in the review queue? Thank you very much for any guidance! Kijun Seo
Replies
0
Boosts
1
Views
388
Activity
1d
Another "Waiting for Review"
First time app submission. Business account. Platform: iOS Category: Sports Nothing controversial. No wagering. No adult content. No health-related topics or information. Free app. No in-app purchases. Originally submitted August 8. Included all the standard information. Provided a video walk-through. First review August 14 (six days later). Rejected literally in the same minute the review was opened. Reviewer (?bot) requested additional information. 99% of the information the reviewer requested had already been provided in the original submission. We immediately provided the requested information. August 17 the second review came through. The app was rejected due to "4.3(a) - Design - Spam. - Submitting an app with the same source code or assets as other apps already submitted to the App Store. Creating and submitting multiple similar apps using a repackaged app template. Purchasing an app template with problematic code from a third party. Submitting several similar apps across multiple accounts". The reviewer suggested we "submit a unique app with distinct content and functionality". This made absolutely no sense. We coded the app completely in-house. No third party. No templates. This is the only app we have submitted. We don't have any other accounts. There are literally no other apps that do what ours does. We have two pending patents on the technology. We developed four of our own computer vision models trained on literally thousands of images. The app is completely unique. We provided a detailed response on the same day (August 17), explaining all of the above and attaching our two patent documents. We've worked 9 months on developing this technology and application. The suggestion to just create a new "unique app" seems trite. Four days later, still zero response. It almost feels like nobody is actually reviewing the app at all. At best, they are taking a cursory one-minute look and just hitting reject and moving on to the next developer's submission. Any ideas or suggestions, other than starting a new business and inventing another new technology so we can create a different app as Apple suggests?
Replies
0
Boosts
0
Views
154
Activity
1d