App Review

RSS for tag

App review is the process of evaluating apps and app updates submitted to the App Store to ensure they are reliable, perform as expected, and follow Apple guidelines.

Posts under App Review tag

200 Posts

Post

Replies

Boosts

Views

Activity

Request for Clearer App Review Feedback and Faster Review
Hello Apple Developer Forums team, I would like to ask for help with my app review (App ID: 6755685130). I first submitted my app on February 14, 2026, and it has been almost 50 days. However, I still have not received clear feedback on what needs to be fixed. If there are issues with my app, I sincerely ask the review team not to provide only general guideline references. I still cannot tell which page, feature, or user flow is causing the problem. If possible, I would really appreciate screenshots, screen recordings, or a written description of the specific issue so I can make the right changes. I also want to clarify that this app is not AI-generated. It is a carefully planned app built with real effort using multiple native Swift frameworks. Thank you very much for your time and help.
5
0
269
Apr ’26
Testlight error
Hello everyone I'm currently experiencing an error when submitting a public link for internal downloads. When I submit and review, it says: "There was an error processing your request. Please try again later." I've reported this to the support team but haven't received a response yet. I would be very grateful if the technical team on this forum could help me. Case ID: 102861441465
4
0
260
Apr ’26
App Stuck in Review for 20+ Days After Escalation – Support Responding but No Progress
Hi everyone, I’m experiencing a serious issue with my app review process on App Store (Apple ID: 6760103989). My app has been stuck in review for a very long time — I’ve contacted Apple Developer Support multiple times, had my case escalated, waited over 20 days after escalation, requested an expedited review, and already posted on the forum. I received this response from Apple (Mar ’12): “Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.” However, since then, there has been no follow-up, the app is still stuck, and there is no reviewer activity (no login detected in my app). At this point, I’m extremely frustrated and actively losing users who pre-subscribed for the iOS app on release. I don’t understand what is causing the delay, whether something is wrong with my app, or what I can do to move the process forward. Has anyone experienced something similar or found a way to resolve this? Any advice would be greatly appreciated.
1
0
94
Apr ’26
Guideline 4.3(b) Spam rejection again and again – need help from App Review experts
My iOS app is getting repeatedly rejected under Guideline 4.3(b) Spam. Apple says the app is astrology / horoscope category, but the app is actually a B2B partner dashboard for verified consultants and contains no horoscope content. We already: Removed astrology keywords Renamed the app Changed metadata Restricted login Removed China region Explained multiple times to App Review Still getting same rejection again and again. Has anyone successfully resolved 4.3(b) spam rejection for astrology / consultation / marketplace apps? What exact change finally worked? Should we appeal? Request call? Change bundle? New app? Different category? Need expert advice urgently.
2
0
151
Apr ’26
App Store Guideline 4.3(b): A Barrier to Meaningful Innovation?
After months of hard work developing an app with unique mechanics and a distinct user experience, we recently faced a rejection under Guideline 4.3(b) (Spam/Saturated Category). The feedback we received stated that there are "already enough of these apps on the App Store." While we completely understand Apple's need to filter out low-quality clones, it feels like this guideline sometimes overlooks genuine originality. The most frustrating part for independent developers is that the category you fall into seems to matter more than the actual value your app provides. Whether the app is positioned in lifestyle, entertainment, or productivity, a rigid "category quota" can prevent reviewers from truly seeing the unique features we built. This creates a significant hurdle for new entrants and makes it incredibly difficult for fresh ideas to break into established categories. It feels less about the quality of the application and more about timing—as if early arrivers have a permanent advantage over newcomers, regardless of how much innovation the new app brings to the table. Ultimately, we believe this limits consumer choice. Users deserve the opportunity to discover and decide between new, modern alternatives, rather than having their options restricted by a pre-determined saturation limit. We hope Apple reconsiders how 4.3(b) is applied, ensuring that the App Store remains a place where truly innovative apps, regardless of their category, have a fair chance to be evaluated on their own merits.
2
0
216
Apr ’26
Working Anti Virus for iOS
https://youtube.com/shorts/mVjjWDagSI0 I created this working anti virus app for iOS. It scans images such as this one from your camera roll to find any that may have contained or may still contain malicious code. https://github.com/hunters-sec/CVE-2025-43300 Apple terminated our developer account as a joke app. We have had several co-orindated attacks on our developer and businesses accounts around Jewish holidays and Shabbat. So it's not surprising it's like Apple uses automated app review or something. if isAntivirus() { terminateDeveloperAccount() } They said we were dishonest when in reality they were the ones that outright lied or refused to read our app review notes.
1
0
269
Apr ’26
App aguardando revisão
Enviei meu app (xek) pra revisão desde terça feira. Recebi a solicitação de ajustes na quarta e depois de ajusta-lo na quarta mesmo, ele ficou travado em “Aguardando revisão” desde então. Um app simples que está no processo de liberação desde terça e desde quarta sem nenhum retorno da Apple, isso eh normal? Tenho outro app que nunca demorou tanto nas aprovações. mandei mensagem por outros canais e nada. Vamos ver se por aqui tenho algum retorno.
1
0
110
Apr ’26
"Unable to Add for Review" - MRDP Error
Hello, since yesterday I've been seeing this error that prevents me from submitting my app for review: "To submit new apps or avoid potential payment blocks, add compliance information for Model Reporting Rules for Digital Platforms (MRDP)." Despite the cryptic information, I've already found the "Model Reporting Rules for Digital Platforms" Compliance documents in the Business section of my account and I've already declared multiple times that no, none of my apps provide personal services in any country or region. And despite that, I still see the damn error. What gives? Is it the same issue I see other users reporting about this DAC7 error? I'm based in the UK. The app is meant to be released in the anglosphere territories of UK, Ireland, Australia and New Zealand. I've managed to submit one version for review but I hadn't linked "In-App Purchases and Subscription" in the review page of the distribution tab, so I had to make a new build to add that and re-submit. This is how I got stuck. Any feedback appreciated. Thanks!
3
1
180
Apr ’26
Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
Hi, I’m hoping someone can help clarify the correct entitlement format for the Enhanced Security capability in a macOS App Store build. Context Our app is a sandboxed macOS app built with Xcode 26.4. We enabled the Enhanced Security capability in Signing & Capabilities, and we configured the entitlements based on the current documentation. What’s confusing me The Xcode 26.4 release notes say apps that already adopted Enhanced Security should remove: com.apple.security.hardened-process.enhanced-security-version com.apple.security.hardened-process.platform-restrictions and replace them with: com.apple.security.hardened-process.enhanced-security-version-string with value 1 com.apple.security.hardened-process.platform-restrictions-string with value 2 Reference: https://developer.apple.com/documentation/xcode-release-notes/xcode-26_4-release-notes The entitlement reference pages also seem consistent with that: https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.security.hardened-process.enhanced-security-version-string https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.security.hardened-process.platform-restrictions-string So our app currently uses the new -string entitlements with values "1" and "2". Our App Review rejection said: The app incorrectly implements sandboxing, or it contains one or more entitlements with invalid values. Entitlement "com.apple.security.hardened-process.enhanced-security-version-string" value must be boolean and true. Entitlement "com.apple.security.hardened-process.platform-restrictions-string" value must be boolean and true. That’s the part I can’t reconcile with the documentation. Questions For a Mac App Store submission built with Xcode 26.4, should these two entitlements use the new string-based form, or Boolean true? If the expected format has changed, is there any updated guidance beyond the Xcode 26.4 release notes and current entitlement reference? If Apple staff or anyone familiar with this can clarify what format is currently expected, I’d really appreciate it. Thanks.
4
0
910
Apr ’26
App Stuck in “In Review'' status
Hi everyone, My app has been stuck in "In Review" status for over 20 days with no updates. I submitted the app on March 1, 2026, the status changed to "In Review" on March 4, 2026, and after that no changes. App ID: 6755649144 I also reached out to Apple Developer Support on March 15 but haven't received any response. Support Case ID: 102845096494 Could someone from App Review please take a look? Also any advice on how to move things forward would be appreciated. Thank you!
2
1
126
Apr ’26
In-App Purchases “Waiting for Review” but not available during App Review (subscriptions unavailable)
Hi everyone, I’m stuck in the App Review process with In-App Purchases (subscriptions) and would really appreciate some guidance. Situation: I have an app with subscriptions (Premium Monthly and Premium Yearly) Both subscriptions are in “Waiting for Review” status I submitted a new app version for review Issue: The app was rejected with: “subscriptions were unavailable at time of review” Before that, I also received a rejection saying the reviewer could not locate the In-App Purchases. What’s confusing: Subscriptions are not yet approved (still “Waiting for Review”) In the current app version page, I do not see the “In-App Purchases” section at all, so I cannot confirm whether they are attached to this build The app correctly loads products via StoreKit, but returns empty when products are not available Questions: Do subscriptions need to be approved before they can be used during app review? Should I reject the current version and resubmit while manually attaching the subscriptions? Is it expected that the “In-App Purchases” section is missing from the version page in this case? Has anyone experienced this “subscriptions unavailable” issue while IAPs are still “Waiting for Review”? I feel like I’m stuck in a loop where: The app needs IAP to pass review But IAP are not available yet during review Any advice on the correct process would be greatly appreciated. Thanks!
1
0
98
Apr ’26
Unable to Save my build
I am unable to submit my app EggZap for review. When I navigate to my iOS App Version 1.0 submission page, I can make all edits and save successfully — screenshots, description, keywords, contact info all save without issue. However, as soon as I add a build to the submission and click Save, the button turns red with a ! error indicator and will not save. Removing the build allows the page to save normally again. The build (Build 51) is fully validated and shows as Complete in TestFlight. It is fully playable via TestFlight on my device. I have tried multiple browsers on multiple devices with the same result. Browser console shows a 409 Conflict error from the PATCH endpoint when saving with a build attached. I have already contacted Apple Developer Support (Case ID: 102858642503) but wanted to reach out to the community as well. I have seen other posts about this same issue but no real answer on how it was fixed. Has anyone experienced this? Any suggestions appreciated.
0
0
99
Apr ’26
Stuck in "Waiting for Review" for 9 days (v1.0.3 Update)
Hi everyone, I am experiencing an unusual delay with my app update. I submitted version 1.0.3 of my app, "MarketNow", on March 12, 2026, but it has been stuck in the "Waiting for Review" status for 9 days now. Typically, updates are reviewed within 24–48 hours, so this 9-day wait is quite concerning. I have already sent a formal inquiry through App Store Connect but haven't received a specific update yet. Is anyone else seeing long wait times for updates this week? Could this be related to a backlog before the April SDK deadline, or is there a known issue with the Finance category review queue? Any insights would be helpful. Thanks!
4
0
177
Apr ’26
No response and stuck in waiting for review
Hello, app name: raw films app id: 6761117809 I need some help or guidance. I submitted my app on 25 of March and it got rejected due to guideline 2.1b, the reviewer couldn’t locate the button to unlock the premium filters with in-app purchase. I provided them screenshots and exact steps to locate the filters on 26 of March, and no response since then. I resubmitted the app on 30th of March, but still no response in App Store Connect messages, I requested help from support via email, but again no response. :( Can anyone help me with an advice? Thank you..
3
0
96
Apr ’26
App Store version stuck after Pending Developer Release – cannot add builds or create new versions
Hello everyone, I’m running into a situation in App Store Connect that appears to be a backend lock related to an approved version, and I’m looking for confirmation or similar experiences. Context: App had version 1.2.6 Version progressed to Pending Developer Release Before releasing to users, I chose Developer Reject I then edited the version number (to 1.2.7) Current State / Issue: After this, App Store Connect is effectively blocked: ❌ Cannot associate any builds to the version ❌ Uploading a build with the same version and higher build number does not help ❌ Cannot create a fresh version (no “+ Version” button is visible) ❌ App Store Connect API returns: ENTITY_ERROR.RELATIONSHIP.INVALID ❌ Remove Version / Delete Version is not available Even attempting brand‑new version numbers does not work. It looks like App Store Connect still considers the previously approved Pending Developer Release version to be active and locked internally. What I understand so far From my understanding: Once a version reaches Pending Developer Release, the appStoreVersion record becomes finalized Editing the version number does not truly create a new version Developer rejection does not unlock the version–build relationship Only one approved / pending version is allowed per app This seems to leave the app in a state where no new versions can be created without backend intervention. Question Can anyone confirm: That once a version reaches Pending Developer Release, it can only be reset or removed by App Store Connect Support, and That there is no self‑service workaround (UI, API, CI, or Transporter) to recover from this state? If anyone has gone through this and successfully had Apple reset the appStoreVersion record, I’d appreciate confirmation or tips on getting it routed correctly. Thanks in advance.
0
0
295
Apr ’26
App Review stuck for weeks on individual account, expedite requests ignored, multiple apps affected
Hello everyone, I am trying to understand whether this is a normal delay or if there may be an account-level review issue affecting my submissions. I am an individual developer. I submitted my first app for review on March 14, 2026. It remained without a meaningful response until March 31, 2026. During this time, I sent three expedite review requests, but none of them helped. Because nothing moved, I withdrew the previous submission and uploaded a third build for the same app. However, the app is still stuck in review flow. At the same time, I submitted my second app on March 22, 2026. I also requested an expedite review for that app, but it is still in Waiting for Review as well. So currently: • App 1 was first submitted on March 14, 2026 • Multiple expedite requests were sent • The original submission was withdrawn and a new build was submitted • App 2 was submitted on March 22, 2026 • Both apps have been heavily delayed • One is still in review flow, and the other is still Waiting for Review I would like to ask: 1. Has anyone experienced this kind of delay on an individual account, especially with multiple apps at the same time? 2. Could this indicate an account-level issue, manual queue hold, or some kind of hidden review flag? 3. Is there any effective way to escalate this beyond normal expedite requests? 4. Would contacting App Review again help, or is there another correct channel for this situation? 5. If I withdraw and resubmit again, is there any chance that it makes the delay worse? I am not asking for special treatment. I am only trying to understand what may be causing such an unusual delay and what the most effective next step is. Any insight from developers who faced a similar situation would be very helpful. Thank you.
3
0
292
Apr ’26
Request for Clearer App Review Feedback and Faster Review
Hello Apple Developer Forums team, I would like to ask for help with my app review (App ID: 6755685130). I first submitted my app on February 14, 2026, and it has been almost 50 days. However, I still have not received clear feedback on what needs to be fixed. If there are issues with my app, I sincerely ask the review team not to provide only general guideline references. I still cannot tell which page, feature, or user flow is causing the problem. If possible, I would really appreciate screenshots, screen recordings, or a written description of the specific issue so I can make the right changes. I also want to clarify that this app is not AI-generated. It is a carefully planned app built with real effort using multiple native Swift frameworks. Thank you very much for your time and help.
Replies
5
Boosts
0
Views
269
Activity
Apr ’26
Testlight error
Hello everyone I'm currently experiencing an error when submitting a public link for internal downloads. When I submit and review, it says: "There was an error processing your request. Please try again later." I've reported this to the support team but haven't received a response yet. I would be very grateful if the technical team on this forum could help me. Case ID: 102861441465
Replies
4
Boosts
0
Views
260
Activity
Apr ’26
App Stuck in Review for 20+ Days After Escalation – Support Responding but No Progress
Hi everyone, I’m experiencing a serious issue with my app review process on App Store (Apple ID: 6760103989). My app has been stuck in review for a very long time — I’ve contacted Apple Developer Support multiple times, had my case escalated, waited over 20 days after escalation, requested an expedited review, and already posted on the forum. I received this response from Apple (Mar ’12): “Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.” However, since then, there has been no follow-up, the app is still stuck, and there is no reviewer activity (no login detected in my app). At this point, I’m extremely frustrated and actively losing users who pre-subscribed for the iOS app on release. I don’t understand what is causing the delay, whether something is wrong with my app, or what I can do to move the process forward. Has anyone experienced something similar or found a way to resolve this? Any advice would be greatly appreciated.
Replies
1
Boosts
0
Views
94
Activity
Apr ’26
App waiting for review for almost 2 months
Re. APP ID 6758894172 This app was submitted on February 16, and since then it has been showing as waiting for review. I have contacted the support email multiple times as well as requesting the review to be expedited, but no response and no change in app status. Could you please investigate this matter and let me know what the issue is?
Replies
3
Boosts
1
Views
204
Activity
Apr ’26
Guideline 4.3(b) Spam rejection again and again – need help from App Review experts
My iOS app is getting repeatedly rejected under Guideline 4.3(b) Spam. Apple says the app is astrology / horoscope category, but the app is actually a B2B partner dashboard for verified consultants and contains no horoscope content. We already: Removed astrology keywords Renamed the app Changed metadata Restricted login Removed China region Explained multiple times to App Review Still getting same rejection again and again. Has anyone successfully resolved 4.3(b) spam rejection for astrology / consultation / marketplace apps? What exact change finally worked? Should we appeal? Request call? Change bundle? New app? Different category? Need expert advice urgently.
Replies
2
Boosts
0
Views
151
Activity
Apr ’26
App Store Guideline 4.3(b): A Barrier to Meaningful Innovation?
After months of hard work developing an app with unique mechanics and a distinct user experience, we recently faced a rejection under Guideline 4.3(b) (Spam/Saturated Category). The feedback we received stated that there are "already enough of these apps on the App Store." While we completely understand Apple's need to filter out low-quality clones, it feels like this guideline sometimes overlooks genuine originality. The most frustrating part for independent developers is that the category you fall into seems to matter more than the actual value your app provides. Whether the app is positioned in lifestyle, entertainment, or productivity, a rigid "category quota" can prevent reviewers from truly seeing the unique features we built. This creates a significant hurdle for new entrants and makes it incredibly difficult for fresh ideas to break into established categories. It feels less about the quality of the application and more about timing—as if early arrivers have a permanent advantage over newcomers, regardless of how much innovation the new app brings to the table. Ultimately, we believe this limits consumer choice. Users deserve the opportunity to discover and decide between new, modern alternatives, rather than having their options restricted by a pre-determined saturation limit. We hope Apple reconsiders how 4.3(b) is applied, ensuring that the App Store remains a place where truly innovative apps, regardless of their category, have a fair chance to be evaluated on their own merits.
Replies
2
Boosts
0
Views
216
Activity
Apr ’26
Working Anti Virus for iOS
https://youtube.com/shorts/mVjjWDagSI0 I created this working anti virus app for iOS. It scans images such as this one from your camera roll to find any that may have contained or may still contain malicious code. https://github.com/hunters-sec/CVE-2025-43300 Apple terminated our developer account as a joke app. We have had several co-orindated attacks on our developer and businesses accounts around Jewish holidays and Shabbat. So it's not surprising it's like Apple uses automated app review or something. if isAntivirus() { terminateDeveloperAccount() } They said we were dishonest when in reality they were the ones that outright lied or refused to read our app review notes.
Replies
1
Boosts
0
Views
269
Activity
Apr ’26
App aguardando revisão
Enviei meu app (xek) pra revisão desde terça feira. Recebi a solicitação de ajustes na quarta e depois de ajusta-lo na quarta mesmo, ele ficou travado em “Aguardando revisão” desde então. Um app simples que está no processo de liberação desde terça e desde quarta sem nenhum retorno da Apple, isso eh normal? Tenho outro app que nunca demorou tanto nas aprovações. mandei mensagem por outros canais e nada. Vamos ver se por aqui tenho algum retorno.
Replies
1
Boosts
0
Views
110
Activity
Apr ’26
"Unable to Add for Review" - MRDP Error
Hello, since yesterday I've been seeing this error that prevents me from submitting my app for review: "To submit new apps or avoid potential payment blocks, add compliance information for Model Reporting Rules for Digital Platforms (MRDP)." Despite the cryptic information, I've already found the "Model Reporting Rules for Digital Platforms" Compliance documents in the Business section of my account and I've already declared multiple times that no, none of my apps provide personal services in any country or region. And despite that, I still see the damn error. What gives? Is it the same issue I see other users reporting about this DAC7 error? I'm based in the UK. The app is meant to be released in the anglosphere territories of UK, Ireland, Australia and New Zealand. I've managed to submit one version for review but I hadn't linked "In-App Purchases and Subscription" in the review page of the distribution tab, so I had to make a new build to add that and re-submit. This is how I got stuck. Any feedback appreciated. Thanks!
Replies
3
Boosts
1
Views
180
Activity
Apr ’26
Should Enhanced Security entitlements use string values or Boolean true for Mac App Store submission?
Hi, I’m hoping someone can help clarify the correct entitlement format for the Enhanced Security capability in a macOS App Store build. Context Our app is a sandboxed macOS app built with Xcode 26.4. We enabled the Enhanced Security capability in Signing & Capabilities, and we configured the entitlements based on the current documentation. What’s confusing me The Xcode 26.4 release notes say apps that already adopted Enhanced Security should remove: com.apple.security.hardened-process.enhanced-security-version com.apple.security.hardened-process.platform-restrictions and replace them with: com.apple.security.hardened-process.enhanced-security-version-string with value 1 com.apple.security.hardened-process.platform-restrictions-string with value 2 Reference: https://developer.apple.com/documentation/xcode-release-notes/xcode-26_4-release-notes The entitlement reference pages also seem consistent with that: https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.security.hardened-process.enhanced-security-version-string https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.security.hardened-process.platform-restrictions-string So our app currently uses the new -string entitlements with values "1" and "2". Our App Review rejection said: The app incorrectly implements sandboxing, or it contains one or more entitlements with invalid values. Entitlement "com.apple.security.hardened-process.enhanced-security-version-string" value must be boolean and true. Entitlement "com.apple.security.hardened-process.platform-restrictions-string" value must be boolean and true. That’s the part I can’t reconcile with the documentation. Questions For a Mac App Store submission built with Xcode 26.4, should these two entitlements use the new string-based form, or Boolean true? If the expected format has changed, is there any updated guidance beyond the Xcode 26.4 release notes and current entitlement reference? If Apple staff or anyone familiar with this can clarify what format is currently expected, I’d really appreciate it. Thanks.
Replies
4
Boosts
0
Views
910
Activity
Apr ’26
The Problem with TestLight
I successfully registered an account a few days ago and tested the app internally, but when I published the link, the application automatically expired. When I submitted it again, I received the message: "There was an error processing your request. Please try again later." I have contacted support but have not received a response. Case ID: 102861441465
Replies
0
Boosts
0
Views
182
Activity
Apr ’26
App Stuck in “In Review'' status
Hi everyone, My app has been stuck in "In Review" status for over 20 days with no updates. I submitted the app on March 1, 2026, the status changed to "In Review" on March 4, 2026, and after that no changes. App ID: 6755649144 I also reached out to Apple Developer Support on March 15 but haven't received any response. Support Case ID: 102845096494 Could someone from App Review please take a look? Also any advice on how to move things forward would be appreciated. Thank you!
Replies
2
Boosts
1
Views
126
Activity
Apr ’26
I received notification 3.2, and am awaiting processing.
As shown in the image, my application was working normally, then suddenly this happened. I've sent an email to support but haven't received a response yet. Has anyone else experienced this?
Replies
0
Boosts
0
Views
65
Activity
Apr ’26
In-App Purchases “Waiting for Review” but not available during App Review (subscriptions unavailable)
Hi everyone, I’m stuck in the App Review process with In-App Purchases (subscriptions) and would really appreciate some guidance. Situation: I have an app with subscriptions (Premium Monthly and Premium Yearly) Both subscriptions are in “Waiting for Review” status I submitted a new app version for review Issue: The app was rejected with: “subscriptions were unavailable at time of review” Before that, I also received a rejection saying the reviewer could not locate the In-App Purchases. What’s confusing: Subscriptions are not yet approved (still “Waiting for Review”) In the current app version page, I do not see the “In-App Purchases” section at all, so I cannot confirm whether they are attached to this build The app correctly loads products via StoreKit, but returns empty when products are not available Questions: Do subscriptions need to be approved before they can be used during app review? Should I reject the current version and resubmit while manually attaching the subscriptions? Is it expected that the “In-App Purchases” section is missing from the version page in this case? Has anyone experienced this “subscriptions unavailable” issue while IAPs are still “Waiting for Review”? I feel like I’m stuck in a loop where: The app needs IAP to pass review But IAP are not available yet during review Any advice on the correct process would be greatly appreciated. Thanks!
Replies
1
Boosts
0
Views
98
Activity
Apr ’26
Unable to Save my build
I am unable to submit my app EggZap for review. When I navigate to my iOS App Version 1.0 submission page, I can make all edits and save successfully — screenshots, description, keywords, contact info all save without issue. However, as soon as I add a build to the submission and click Save, the button turns red with a ! error indicator and will not save. Removing the build allows the page to save normally again. The build (Build 51) is fully validated and shows as Complete in TestFlight. It is fully playable via TestFlight on my device. I have tried multiple browsers on multiple devices with the same result. Browser console shows a 409 Conflict error from the PATCH endpoint when saving with a build attached. I have already contacted Apple Developer Support (Case ID: 102858642503) but wanted to reach out to the community as well. I have seen other posts about this same issue but no real answer on how it was fixed. Has anyone experienced this? Any suggestions appreciated.
Replies
0
Boosts
0
Views
99
Activity
Apr ’26
Stuck in "Waiting for Review" for 9 days (v1.0.3 Update)
Hi everyone, I am experiencing an unusual delay with my app update. I submitted version 1.0.3 of my app, "MarketNow", on March 12, 2026, but it has been stuck in the "Waiting for Review" status for 9 days now. Typically, updates are reviewed within 24–48 hours, so this 9-day wait is quite concerning. I have already sent a formal inquiry through App Store Connect but haven't received a specific update yet. Is anyone else seeing long wait times for updates this week? Could this be related to a backlog before the April SDK deadline, or is there a known issue with the Finance category review queue? Any insights would be helpful. Thanks!
Replies
4
Boosts
0
Views
177
Activity
Apr ’26
No response and stuck in waiting for review
Hello, app name: raw films app id: 6761117809 I need some help or guidance. I submitted my app on 25 of March and it got rejected due to guideline 2.1b, the reviewer couldn’t locate the button to unlock the premium filters with in-app purchase. I provided them screenshots and exact steps to locate the filters on 26 of March, and no response since then. I resubmitted the app on 30th of March, but still no response in App Store Connect messages, I requested help from support via email, but again no response. :( Can anyone help me with an advice? Thank you..
Replies
3
Boosts
0
Views
96
Activity
Apr ’26
App Store version stuck after Pending Developer Release – cannot add builds or create new versions
Hello everyone, I’m running into a situation in App Store Connect that appears to be a backend lock related to an approved version, and I’m looking for confirmation or similar experiences. Context: App had version 1.2.6 Version progressed to Pending Developer Release Before releasing to users, I chose Developer Reject I then edited the version number (to 1.2.7) Current State / Issue: After this, App Store Connect is effectively blocked: ❌ Cannot associate any builds to the version ❌ Uploading a build with the same version and higher build number does not help ❌ Cannot create a fresh version (no “+ Version” button is visible) ❌ App Store Connect API returns: ENTITY_ERROR.RELATIONSHIP.INVALID ❌ Remove Version / Delete Version is not available Even attempting brand‑new version numbers does not work. It looks like App Store Connect still considers the previously approved Pending Developer Release version to be active and locked internally. What I understand so far From my understanding: Once a version reaches Pending Developer Release, the appStoreVersion record becomes finalized Editing the version number does not truly create a new version Developer rejection does not unlock the version–build relationship Only one approved / pending version is allowed per app This seems to leave the app in a state where no new versions can be created without backend intervention. Question Can anyone confirm: That once a version reaches Pending Developer Release, it can only be reset or removed by App Store Connect Support, and That there is no self‑service workaround (UI, API, CI, or Transporter) to recover from this state? If anyone has gone through this and successfully had Apple reset the appStoreVersion record, I’d appreciate confirmation or tips on getting it routed correctly. Thanks in advance.
Replies
0
Boosts
0
Views
295
Activity
Apr ’26
App Review stuck for weeks on individual account, expedite requests ignored, multiple apps affected
Hello everyone, I am trying to understand whether this is a normal delay or if there may be an account-level review issue affecting my submissions. I am an individual developer. I submitted my first app for review on March 14, 2026. It remained without a meaningful response until March 31, 2026. During this time, I sent three expedite review requests, but none of them helped. Because nothing moved, I withdrew the previous submission and uploaded a third build for the same app. However, the app is still stuck in review flow. At the same time, I submitted my second app on March 22, 2026. I also requested an expedite review for that app, but it is still in Waiting for Review as well. So currently: • App 1 was first submitted on March 14, 2026 • Multiple expedite requests were sent • The original submission was withdrawn and a new build was submitted • App 2 was submitted on March 22, 2026 • Both apps have been heavily delayed • One is still in review flow, and the other is still Waiting for Review I would like to ask: 1. Has anyone experienced this kind of delay on an individual account, especially with multiple apps at the same time? 2. Could this indicate an account-level issue, manual queue hold, or some kind of hidden review flag? 3. Is there any effective way to escalate this beyond normal expedite requests? 4. Would contacting App Review again help, or is there another correct channel for this situation? 5. If I withdraw and resubmit again, is there any chance that it makes the delay worse? I am not asking for special treatment. I am only trying to understand what may be causing such an unusual delay and what the most effective next step is. Any insight from developers who faced a similar situation would be very helpful. Thank you.
Replies
3
Boosts
0
Views
292
Activity
Apr ’26
Submission stuck in Waiting for Review
Hello, I’m writing you because my app submission has been in ‘Waiting for Review’ for longer than expected. My app id its : Apple ID: 6759054133 can you help me please? Best regards!
Replies
2
Boosts
0
Views
107
Activity
Apr ’26