Overview

Post

Replies

Boosts

Views

Activity

App Stuck in “Waiting for Review” for Several Days Without Response
Hi Team, We are facing an issue with our app review process for Chinmaya Clix. Our previous build was submitted on April 30, 2026, and it remained in the “Waiting for Review” state until May 7, 2026 without any update or response from Apple. During this period, we also submitted an expedited review request and contacted Apple Support multiple times, but did not receive any response. After waiting for several days, we rejected the previous build and submitted a new build on May 7, 2026 at 3:36 PM (IST). We again submitted an expedited review request for the latest build, but the app is still stuck in the “Waiting for Review” state. Details for reference: App Name: Chinmaya Clix Support Case ID: 102886900142 Previous Submission ID: eff3c432-bc87-4ec8-9fac-3b23b795cb7d Current Submission ID: a1fc7506-b47c-4da6-9248-207c9b318f70 Current Submission Date: May 7, 2026 at 3:36 PM (IST) Our app release is time-sensitive and planned for this week, so we would really appreciate any guidance regarding: Possible reason for the delay Expected review timeline Any further communication or escalation process we should follow If anyone from Apple or the developer community has experienced something similar, please let us know. Thank you.
0
0
35
1d
App Review Delay for so long
Hello App Review Team, We respectfully ask for your assistance regarding our app review status. Our submission was re-submitted on April 29, 2026, and it has now been waiting for review for more than 12 days without any update or response. In addition, we have already been working through the review process for this app on this developer account for almost 4 months. We carefully addressed all previous review feedback and submitted the required fixes, but the review process continues to experience very long delays. This situation is now seriously impacting our planned product launch, business operations, and partner commitments. We sincerely ask if the App Review Team could please help: Review the current submission status Escalate the case internally if possible Help move the review process forward Reference Information: Case Number: 102877213113 Submission ID: 68850cef-1651-40c8-b717-7916b679a467 We would greatly appreciate any assistance or update regarding this matter. Thank you very much.
0
0
37
1d
App stuck “In Review” for 10 days – is anyone else experiencing this?
Hello everyone, My app has been stuck in “In Review” for around 10 days without any update. I have not received any rejection, metadata request, or additional information request from the review team. The app is simply remaining in review with no movement. What worries me the most is that I have already contacted the App Review Team multiple times through App Store Connect, but I still have not received any response. Is anyone else experiencing the same situation recently? Have you found any effective way to speed up the review process? Thank you very much.
0
0
12
1d
StoreKit Product.products(for:) returns empty / fails during App Review
Hi, My macOS app was rejected because the reviewer saw "Couldn't load purchase options" on the paywall. The same build works correctly for me. Product.products(for:) either throws or returns an empty array, triggering the error UI. Has anyone else experienced this specifically during App Review? Is there anything specific about the review environment that could cause StoreKit to fail to fetch products? Thank you.
1
0
57
1d
Best practices for bypassing critical system daemons in NETransparentProxyProvider
Hello, I am working on a network security and DLP (Data Loss Prevention) solution. A core requirement of our architecture is the ability to modify network traffic payloads in-flight (e.g., stripping sensitive data or altering packets). So, the only way to implement this is via the NETransparentProxyProvider which allows us to handle, evaluate, and modify network flows (NEAppProxyFlow). However, because this is such a powerful mechanism, my primary goal is to ensure the absolute stability of the operating system. I want to minimize the risk of interfering with core Apple services. When evaluating a flow, I have access to NEFlowMetaData, specifically properties like sourceAppUniqueIdentifier and sourceAppAuditToken. Could you please assist me with the following questions: Is there a recommended list of Apple system Application IDs (Bundle IDs) or executable names that should be strictly bypassed (ignored) by the Network Extension to maintain system integrity? Since system daemons can change between OS releases, are there any programmatic best practices or specific rules to dynamically identify core OS traffic that must not be intercepted? Are there any specific network ports or protocols that Apple strongly recommends excluding from NENetworkRule matches at the proxy provider configuration level to ensure daemons like apsd or mDNSResponder function correctly? Thank you in advance.
2
0
126
1d
VMs for automated testing vs 2 macOS instance limit
Hello, I'm evaluating possibility to use virtualization to setup on-permise parallel testing system for a product I work on. My compatibility range is wide, i.e. it would cover macOS 12 - 26, so any testcase needs to be executed on at least 5 different OS versions (and introducing any parallization to the test execution would mean I deal with higher number of VMs). As far as I understand, there is a constraint in Apple Software License, that limits number of OS VM installations per one physical system to 2 (section 2.B.(iii)) in case of OS downloaded from the Internet or through App Store. Clearly these days a single high-end Mac hardware could sustain more than 2 VMs running in parallel. The license also mentions it is also possible to be in a volume or maintenance license program and then the terms of this program apply instead. So I wonder how do people normally deal with the above limitation? What is the path I need to follow if I want to be able to run more than "2 additional copies or instances of" macOS on my VMs?
0
0
51
1d
[macOS 26.4.x, iOS 26.4.x] Handoff broken?
Hello, with macOS' and iOS' recent updates (26.4.x), Handoff in my app appears to have become dysfunctional, as I receive the following message in the logs: getContinuationStreamsWithCompletionHandler(), inputStream=(null) outputStream=(null) error=Error Domain=NSPOSIXErrorDomain Code=94 "Bad message" UserInfo={NSLocalizedDescription=Could not set up internal streams} It ONLY works: From a Mac with 15.x to other Macs or iOS devices (on 26.4.x). All other combinations (see below) do NOT work: iOS (26.4.x) > iOS (26.4.x) iOS (26.4.x) > Mac (26.4.x) iOS (26.4.x) > Mac (15.x) Mac (26.4.x) > iOS (26.4.x) The Handoff prompt is shown in the Dock on Mac, in the app switcher on iOS, and in the Dock on iPadOS, but once I click/press it, I get the continuationStreams error. Now, is it my app, or the OS? Thank you kindly, – Matthias
5
0
285
1d
App rejected under Guideline 5.1.1(ix) - Organization account required for restaurant driver app
Hello everyone, My iOS app was rejected by App Review under: Guideline 5.1.1(ix) - Legal - Privacy - Data Collection and Storage The review message says that the app must be submitted through an Apple Developer Program account enrolled as an Organization, not as an Individual. The app is a private restaurant delivery driver app in Saudi Arabia. It is used only by approved restaurant delivery drivers to view and manage assigned food delivery orders. The app uses location only for normal restaurant food delivery workflow. It is not related to healthcare, finance, insurance, legal, government, cryptocurrency, education, or any other regulated service. The restaurant company has valid Commercial Registration and National Address documents in Saudi Arabia. I am an employee / authorized technical representative of the company, and I manage the app submission and technical deployment for them. My questions: Is an Organization Apple Developer account strictly required for this type of restaurant delivery driver app? Can this be resolved by replying to App Review with company authorization and business documents? Or is converting/updating the Apple Developer membership from Individual to Organization the only practical solution? If I am not the founder/co-founder but I am an employee/authorized representative of the company, can the current Individual membership be updated to Organization, or should the company owner create a new Organization membership? Any guidance from developers who faced a similar 5.1.1(ix) rejection would be appreciated. Thank you.
2
0
89
1d
Sectigo Public Server Authentication CA DV R36?
When I submit an https web request I receive both of those funny errors. In particular I do not understand what that “Sectigo Public Server Authentication” message represents, perhaps yet another certification for Apple to access the request, when of course by connecting to that web address on Safari produces no errors. Connection error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} (+[PPSClientDonation isRegisteredSubsystem:category:]) Permission denied: Maps / SpringfieldUsage (+[PPSClientDonation sendEventWithIdentifier:payload:]) Invalid inputs: payload={ isSPR = 1; } urlstring=https://taxiprofessional.net/***.php process loading tcp_input [C2.1.1.1:3] flags=[R] seq=2572529641, ack=2572529641, win=251 state=ESTABLISHED rcv_nxt=2572535079, snd_una=3494441675 tcp_input [C2.1.1.1:3] flags=[R] seq=2572535079, ack=2572535079, win=1981 state=ESTABLISHED rcv_nxt=2572535079, snd_una=3494441675 nw_endpoint_flow_failed_with_error [C2.1.1.1 82.223.15.117:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: pdp_ip0[lte], ipv4, dns, expensive, uses cell, LQM: moderate)] already failing, returning nw_endpoint_flow_failed_with_error [C2.1.1.1 82.223.15.117:443 cancelled channel-flow ((null))] already failing, returning Connection 2: received failure notification Connection 2: received ECONNRESET with incomplete TLS handshake - generating errSSLClosedNoNotify Connection 2: failed to connect 3:-9816, reason -1 Connection 2: encountered error(3:-9816) Task <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1> HTTP load failed, 0/0 bytes (error code: -1200 [3:-9816]) Task <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1> finished with error [-1200] Error Domain=NSURLErrorDomain Code=-1200 "Connessione sicura non riuscita a causa di un errore TLS." UserInfo={NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x121bd4240>, NSErrorFailingURLKey=https://taxiprofessional.net/...php, NSErrorFailingURLStringKey=https://taxiprofessional.net/....php, NSErrorClientCertificateStateKey=0, NSErrorPeerCertificateChainKey=( "<cert(0x11bfcca00) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x121a27200) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x122dac000) s: Sectigo Public Server Authentication CA DV R36 i: Sectigo Public Server Authentication Root R46>" ), _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1>" ), NSLocalizedDescription=Connessione sicura non riuscita a causa di un errore TLS., _kCFStreamErrorDomainKey=3, NSUnderlyingError=0x121b7b0c0 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "(null)" UserInfo={_kCFNetworkCFStreamSSLErrorOriginalValue=-9816, kCFStreamPropertySSLPeerCertificates=( "<cert(0x11bfcca00) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x121a27200) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x122dac000) s: Sectigo Public Server Authentication CA DV R36 i: Sectigo Public Server Authentication Root R46>" ), _kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x121bd4240>, _NSURLErrorNWPathKey=satisfied (Path is satisfied), viable, interface: pdp_ip0[lte], ipv4, dns, expensive, uses cell, LQM: moderate, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9816}}, _kCFStreamErrorCodeKey=-9816}
1
0
48
1d
"Waiting for Review" for 30 days😭😭
Hello, our App (appleId: 6761799912) has stuck in review process since 30+ days ago, I have tried resubmit it for few times, please check the status of our App, thank you!! I understand that review times can vary and that the queue may currently be experiencing higher-than-usual volume. I'm not trying to escalate — I simply want to confirm whether: 1、There is any specific issue or blocker with this submission 2、Any additional information or documentation is required from my side 3、Or whether the app is simply still pending reviewer assignment Thank you
0
1
64
1d
App Store Server Notification v2: how to distinguish a resubscription that happened in-app from one that happened in Settings → Subscriptions?
Context We're handling App Store subscriptions on the server side using App Store Server Notification v2. Our pipeline currently identifies each event by transactionId and originalTransactionId. A few notes about our client: Our app is built with Flutter and uses the standard in_app_purchase plugin layer to drive App Store purchases (StoreKit 1 under the hood). We have not migrated to StoreKit 2 on the client yet. We have not been setting SKPayment.applicationUsername on outgoing purchases, so every transaction we've ever produced has appAccountToken: null in its v2 notification. This question is purely about what the server-side notification can tell us, given the current client state above. What we're trying to figure out A user can resubscribe to an expired subscription in two different places: In-app — the user opens our app and re-purchases through our normal in-app purchase flow. App Store — the user goes to Settings → Apple ID → Subscriptions and resubscribes from the system UI, without ever returning to the app. Both paths trigger a SUBSCRIBED notification (subtype RESUBSCRIBE) with structurally identical payloads as far as we can tell — same shape for data.transactionInfo, data.renewalInfo, etc. From the notification alone we can't decide which path produced it. The reason this matters: in our system, the two paths require different business handling: In-app path: the user may have signed in to a different business account in our app. The new subscription should be attributed to whoever paid in the app just now, not to the previous owner of originalTransactionId. App Store path: there is no in-app signal, so the business owner can only be inferred from the previous originalTransactionId mapping. If we get it wrong, the subscription's entitlement ends up on the wrong business account. What we do today Because we can't tell the paths apart from the notification, we defer processing for a few minutes and check whether an in-app order for the same transaction has arrived in the meantime: If an in-app order shows up → it's the in-app path; attribute to the in-app account. If nothing shows up after the delay → assume App Store path; fall back to the previous owner mapping. This works but adds latency to entitlement activation and forces us to build a deferred-retry queue with idempotency against the in-app callback path. Possible direction: appAccountToken / applicationUsername We noticed that v2 notifications carry transactionInfo.appAccountToken, and the docs suggest that StoreKit 1's SKPayment.applicationUsername (when it's a valid UUID) is mirrored into this field. In theory, if we start setting it on every in-app purchase from the Flutter client, the field could double as a path discriminator on the server: appAccountToken != null → in-app path (only the app can set it), and we even get the business user id for free appAccountToken == null → App Store path (no UI to populate it) But we have some open questions before committing to this direction: Questions Is there an existing signal in ResponseBodyV2 / JWSTransactionDecodedPayload / JWSRenewalInfoDecodedPayload that distinguishes these two paths, that I might be missing? Can the same distinction be obtained via getAllSubscriptionStatuses / getTransactionHistory / any other Server API endpoint? Is applicationUsername (StoreKit 1) still a reliable way to populate appAccountToken on v2 notifications today? Specifically: Are there format constraints beyond "valid UUID" that cause Apple to drop the value? Any known differences between sandbox and production in how it's mirrored? Does the App Store path ever strip or overwrite a previously-set value when the same originalTransactionId is reused? For existing subscriptions where applicationUsername was never set (which is all of ours today, since we've never polient), is there any way to retroactively distinguish the in-app vs App Store path? Or is timing-based deferred matching theonly option for that cohort, even after we start setting the value on new purchases? If neither (1) nor (2) is currently possible, is the timing-based heuristic we use today the pattern Apple expects developers to follow, or is there a recommended approach we're missing? A small suggestion, if it turns out there's no existing way If the information genuinely isn't exposed today, it might be worth surfacing a salesChannel-style field on the transaction, similar to what Google Play Developer API exposes on Order.salesChannel (IN_APP, PLAY_STORE, etc.). That would let server-side handlers route each event to the correct business owner immediately, regardless of whether appAccountToken was set, and would also cover legacynt never had a chance to populate it. Thanks — happy to share sample payloads or more detail if helpful.
1
0
56
1d
After enabling Enhaced Security the linker error Library 'c++polyfills' not found occurs (Simulator only)
After enabling Enhanced Security for an existing iOS project (mixed Objective-C / Swift) I get the linker error: Library 'c++polyfills' not found This happens when compiling for a simulator as run destination. Device builds (debug) or archiving a release build works. However I need to be able to test on a simulator... Xcode version is 26.4.1, Simulator uses iOS 26.4.1
4
0
251
1d
Free sports prediction app with prizes being classified as gambling under Guideline 5.3.4
I’m looking for guidance regarding App Review classifying my app as gambling / real-money gaming under Guideline 5.3.4. My app is a free football prediction competition app where users predict match scores and compete in rankings based on prediction accuracy. Top-ranked users may occasionally receive promotional physical prizes such as headphones, consoles, or other products. Important details: participation is completely free there are no entry fees users cannot deposit money users cannot withdraw money there is no wagering or betting system there are no sportsbooks, odds, or casino mechanics users never risk money to participate prizes are funded directly by the platform as promotional rewards Apple rejected the app under: Guideline 2.3.6 – Accurate Metadata Guideline 5.3.4 – Gaming, Gambling, and Lotteries App Review is stating that the app includes “real money gambling, real money betting, or real money skill-based gaming” and is requesting gambling licenses and geo-restrictions. My understanding was that gambling generally requires users to risk something of value (money/payment/consideration) for a chance to win prizes, which does not happen in this app. I would appreciate guidance from developers who have experience with: Free prediction or fantasy-style apps with promotional prizes Skill-based competitions reviewed by Apple Sweepstakes/contest compliance on the App Store UI/wording that may accidentally trigger gambling classification Whether App Review typically requires legal contest rules instead of gambling licenses in cases like this If anyone has successfully published a similar app, I’d really appreciate hearing what changes or clarifications helped during review. I want to launch initially in Brazil Thank you.
2
0
64
1d
-startDownloadingUbiquitousItemAtURL:error: and NSURLUbiquitousItemDownloadRequestedKey
I'm trying to update the iCloud data handling in our app, and I'm running into an issue with a particular file on one particular device. This file never downloads & I haven't been able to pinpoint what's off about it. Right now we just have 2 iCloud accounts & a handful of devices, so I haven't been able to narrow it down yet, but in most cases, all the cloud files download as expected. However, whether or not the file eventually downloads, the NSURLUbiquitousItemDownloadRequestedKey key seems to be completely useless. For the following code: NSError *error = nil; BOOL success = [[NSFileManager defaultManager] startDownloadingUbiquitousItemAtURL:self.fileURL error:&error]; if (!success) { NSLog(@"error downloading %@ : %@", self.fileURL, error); } else { NSDictionary *resourceValues = [self.fileURL resourceValuesForKeys:@[NSURLUbiquitousItemDownloadRequestedKey, NSURLUbiquitousItemIsDownloadingKey, NSURLUbiquitousItemDownloadingErrorKey, NSURLUbiquitousItemDownloadingStatusKey] error:&error]; if (!error) { NSString *downloadStatus = resourceValues[NSURLUbiquitousItemDownloadingStatusKey]; bool downloadRequested = [resourceValues[NSURLUbiquitousItemDownloadRequestedKey] boolValue]; NSLog(@"download requested: %d", downloadRequested); } // ... } downloadRequested is always false, regardless of whether or not the cloud file eventually downloads. I have 2 questions: is there a way to actually check if a download has been requested for a file? what could be preventing this file from downloading? -startDownloadingUbiquitousItemAtURL:error: doesn't report an error, NSURLUbiquitousItemDownloadingErrorKey is always nil, and no error is reported in the NSMetadataQuery observer.
1
0
54
1d
Using Xcode with Claude Opus 4.7
Has anyone got Xcode working with Opus 4.7? I have Claude Code running 4.7, but Xcode insists on running 4.6. Even working with Claude to try to configure Xcode doesn't work. Apparently Xcode does something that prevents using Opus 4.7. Any reason for this? Xcode has a really nice integration, but I guess It's bak to Terminal and Claude Code if I want to use the better Model. Anyone else got this working?
3
0
236
1d
Background Assets Mac (Designed for iPad)
Hello, I have followed the instructions in https://developer.apple.com/documentation/backgroundassets to setup background asset to work on the iPhone. I am able to confirm successfully test the asset packs locally on the iPhone. However, when I try to run the my test code on the Mac (Designed for iPad), I get this error. BackgroundAssets/AssetPackManager.swift:206: Fatal error: The app couldn’t be validated: The bundle’s info dictionary lacks a string value for the key “BAAppGroupID”. Is this feature not supported on the Mac?
6
0
169
1d
Setting massProperties on a USDZ-loaded entity corrupts its transform (position/scale → NaN)
Setting massProperties on a USDZ-loaded entity corrupts its transform (position/scale → NaN) Category: RealityKit / visionOS Environment: visionOS 26.x Summary: Modifying PhysicsBodyComponent.massProperties at runtime on an entity loaded from a .usdz file silently corrupts the entity's transform. The translation and scale components become NaN, while rotation remains valid. The corruption occurs during the next RealityKit scene update cycle (e.g., during an await suspension on the main actor). Steps to Reproduce: Author a .usda file with a RigidBody component including valid m_mass and m_inertia values Load the entity at runtime via Entity(named: "MyEntity.usdz", in: bundle) Read the existing PhysicsBodyComponent, modify massProperties, and set it back: if var physics = entity.components[PhysicsBodyComponent.self] { physics.massProperties = .init( mass: 1.944, inertia: SIMD3<Float>(0.013, 0.026, 0.016), centerOfMass: (position: .zero, orientation: .init()) ) entity.components.set(physics) } Add the entity to the scene Perform any await call (e.g., TextureResource(contentsOf:)) that yields to the main actor, allowing a RealityKit scene update to run Expected: The entity retains its position and scale with the updated mass/inertia values. Actual: The entity's transform becomes corrupted: Transform( scale: SIMD3<Float>(nan, nan, nan), rotation: simd_quatf(real: 1.0, imag: SIMD3<Float>(0.0, 0.0, 0.0)), // ← fine translation: SIMD3<Float>(-nan, -nan, -nan) ) Additional findings from investigation: The entity's physics mode does not matter — corruption occurs even when the entity is .kinematic Creating a new PhysicsBodyComponent(...) and replacing the existing one also triggers the bug Modifying other properties on the same component (linearDamping, angularDamping, material, mode) does not cause corruption — only massProperties triggers it The parent entity's transform remains valid The computed mass/inertia values themselves are valid (finite, positive) The corruption is silent — no error, no warning, no crash from RealityKit itself Workaround: Author mass and inertia values directly in the .usda file and do not modify massProperties at runtime: def RealityKitStruct "massFrame" { float3 m_inertia = (0.02, 0.02, 0.038) float m_mass = 2.5 def RealityKitStruct "m_pose" { } } Other PhysicsBodyComponent properties (damping, material, mode) can safely be modified at runtime.
0
0
192
1d
ARIA Life v1.0 stuck “Waiting for Review” 5 days — Expedited request approved, still no movement
Hi, I submitted ARIA Life (iOS, Version 1.0) on May 4th. It has been stuck in “Waiting for Review” for 5 days with no status change and no emails from Apple. Current average wait time for May 2026 is under 9 hours per live data. I submitted an expedited review request today which was confirmed approved, but the status has still not changed. No messages in Resolution Center, account is in good standing. Is anyone from Apple able to help or has anyone experienced this recently?
1
1
159
1d
Severe App Review delay since January, app still broken and TestFlight also blocked
Hello, I am posting regarding my app, Apple ID 6755677576. My app was rejected on April 2, and I resubmitted it. After several weeks without any progress, I had to cancel the submission because the delay had become highly abnormal. I resubmitted the app again on April 23, and it is still stuck in “Waiting for Review.” This situation is critical because the live version of the app has contained a severe blocking bug since January 23. Due to these unusually long App Review delays, I have been unable to release the fix, and users continue to leave negative reviews because the app remains broken. In addition, for months, TestFlight builds have also remained pending review for unusually long periods. This means I no longer have any practical way to provide affected users with a corrected version while waiting for App Review, even though they are actively complaining about the blocking bug in the live version. I would like to know whether other developers are currently experiencing similarly unusual delays for both App Store review and TestFlight review. Thank you.
1
1
68
1d
Stuck in app review
Dear App Review Team, I am writing to escalate an ongoing and critical issue regarding our app review. App ID: 6705133649 Status: Waiting for Review since April 30, 2026 — now over 10 days with no progress. Timeline of events: • April 30 – Submitted for review • ~May 4 – Posted on Apple Developer Forums requesting an update • May 5 – Apple responded: "We're investigating and will contact you in App Store Connect" • May 9 – Followed up again after no contact was made • Today – Still no review, no contact, no explanation We have received no communication via App Store Connect as promised. This is part of a larger pattern we have experienced: • Our reviews previously completed within 48 hours consistently • Our last review cycle took approximately 1.5 months • This current review is now past 10 days with no movement We are formally requesting: Immediate escalation to a senior App Review team member A clear explanation of why this review has stalled Confirmation of whether any action is required from our side A committed timeline for resolution This delay is directly impacting our users and business. We are fully available to provide any additional information, demo credentials, or clarification needed — and will respond immediately to any request. We respectfully ask that this be treated as urgent and resolved within 48 hours. Thank you.
1
1
66
1d
App Stuck in “Waiting for Review” for Several Days Without Response
Hi Team, We are facing an issue with our app review process for Chinmaya Clix. Our previous build was submitted on April 30, 2026, and it remained in the “Waiting for Review” state until May 7, 2026 without any update or response from Apple. During this period, we also submitted an expedited review request and contacted Apple Support multiple times, but did not receive any response. After waiting for several days, we rejected the previous build and submitted a new build on May 7, 2026 at 3:36 PM (IST). We again submitted an expedited review request for the latest build, but the app is still stuck in the “Waiting for Review” state. Details for reference: App Name: Chinmaya Clix Support Case ID: 102886900142 Previous Submission ID: eff3c432-bc87-4ec8-9fac-3b23b795cb7d Current Submission ID: a1fc7506-b47c-4da6-9248-207c9b318f70 Current Submission Date: May 7, 2026 at 3:36 PM (IST) Our app release is time-sensitive and planned for this week, so we would really appreciate any guidance regarding: Possible reason for the delay Expected review timeline Any further communication or escalation process we should follow If anyone from Apple or the developer community has experienced something similar, please let us know. Thank you.
Replies
0
Boosts
0
Views
35
Activity
1d
App Review Delay for so long
Hello App Review Team, We respectfully ask for your assistance regarding our app review status. Our submission was re-submitted on April 29, 2026, and it has now been waiting for review for more than 12 days without any update or response. In addition, we have already been working through the review process for this app on this developer account for almost 4 months. We carefully addressed all previous review feedback and submitted the required fixes, but the review process continues to experience very long delays. This situation is now seriously impacting our planned product launch, business operations, and partner commitments. We sincerely ask if the App Review Team could please help: Review the current submission status Escalate the case internally if possible Help move the review process forward Reference Information: Case Number: 102877213113 Submission ID: 68850cef-1651-40c8-b717-7916b679a467 We would greatly appreciate any assistance or update regarding this matter. Thank you very much.
Replies
0
Boosts
0
Views
37
Activity
1d
App stuck “In Review” for 10 days – is anyone else experiencing this?
Hello everyone, My app has been stuck in “In Review” for around 10 days without any update. I have not received any rejection, metadata request, or additional information request from the review team. The app is simply remaining in review with no movement. What worries me the most is that I have already contacted the App Review Team multiple times through App Store Connect, but I still have not received any response. Is anyone else experiencing the same situation recently? Have you found any effective way to speed up the review process? Thank you very much.
Replies
0
Boosts
0
Views
12
Activity
1d
StoreKit Product.products(for:) returns empty / fails during App Review
Hi, My macOS app was rejected because the reviewer saw "Couldn't load purchase options" on the paywall. The same build works correctly for me. Product.products(for:) either throws or returns an empty array, triggering the error UI. Has anyone else experienced this specifically during App Review? Is there anything specific about the review environment that could cause StoreKit to fail to fetch products? Thank you.
Replies
1
Boosts
0
Views
57
Activity
1d
Best practices for bypassing critical system daemons in NETransparentProxyProvider
Hello, I am working on a network security and DLP (Data Loss Prevention) solution. A core requirement of our architecture is the ability to modify network traffic payloads in-flight (e.g., stripping sensitive data or altering packets). So, the only way to implement this is via the NETransparentProxyProvider which allows us to handle, evaluate, and modify network flows (NEAppProxyFlow). However, because this is such a powerful mechanism, my primary goal is to ensure the absolute stability of the operating system. I want to minimize the risk of interfering with core Apple services. When evaluating a flow, I have access to NEFlowMetaData, specifically properties like sourceAppUniqueIdentifier and sourceAppAuditToken. Could you please assist me with the following questions: Is there a recommended list of Apple system Application IDs (Bundle IDs) or executable names that should be strictly bypassed (ignored) by the Network Extension to maintain system integrity? Since system daemons can change between OS releases, are there any programmatic best practices or specific rules to dynamically identify core OS traffic that must not be intercepted? Are there any specific network ports or protocols that Apple strongly recommends excluding from NENetworkRule matches at the proxy provider configuration level to ensure daemons like apsd or mDNSResponder function correctly? Thank you in advance.
Replies
2
Boosts
0
Views
126
Activity
1d
VMs for automated testing vs 2 macOS instance limit
Hello, I'm evaluating possibility to use virtualization to setup on-permise parallel testing system for a product I work on. My compatibility range is wide, i.e. it would cover macOS 12 - 26, so any testcase needs to be executed on at least 5 different OS versions (and introducing any parallization to the test execution would mean I deal with higher number of VMs). As far as I understand, there is a constraint in Apple Software License, that limits number of OS VM installations per one physical system to 2 (section 2.B.(iii)) in case of OS downloaded from the Internet or through App Store. Clearly these days a single high-end Mac hardware could sustain more than 2 VMs running in parallel. The license also mentions it is also possible to be in a volume or maintenance license program and then the terms of this program apply instead. So I wonder how do people normally deal with the above limitation? What is the path I need to follow if I want to be able to run more than "2 additional copies or instances of" macOS on my VMs?
Replies
0
Boosts
0
Views
51
Activity
1d
[macOS 26.4.x, iOS 26.4.x] Handoff broken?
Hello, with macOS' and iOS' recent updates (26.4.x), Handoff in my app appears to have become dysfunctional, as I receive the following message in the logs: getContinuationStreamsWithCompletionHandler(), inputStream=(null) outputStream=(null) error=Error Domain=NSPOSIXErrorDomain Code=94 "Bad message" UserInfo={NSLocalizedDescription=Could not set up internal streams} It ONLY works: From a Mac with 15.x to other Macs or iOS devices (on 26.4.x). All other combinations (see below) do NOT work: iOS (26.4.x) > iOS (26.4.x) iOS (26.4.x) > Mac (26.4.x) iOS (26.4.x) > Mac (15.x) Mac (26.4.x) > iOS (26.4.x) The Handoff prompt is shown in the Dock on Mac, in the app switcher on iOS, and in the Dock on iPadOS, but once I click/press it, I get the continuationStreams error. Now, is it my app, or the OS? Thank you kindly, – Matthias
Replies
5
Boosts
0
Views
285
Activity
1d
App rejected under Guideline 5.1.1(ix) - Organization account required for restaurant driver app
Hello everyone, My iOS app was rejected by App Review under: Guideline 5.1.1(ix) - Legal - Privacy - Data Collection and Storage The review message says that the app must be submitted through an Apple Developer Program account enrolled as an Organization, not as an Individual. The app is a private restaurant delivery driver app in Saudi Arabia. It is used only by approved restaurant delivery drivers to view and manage assigned food delivery orders. The app uses location only for normal restaurant food delivery workflow. It is not related to healthcare, finance, insurance, legal, government, cryptocurrency, education, or any other regulated service. The restaurant company has valid Commercial Registration and National Address documents in Saudi Arabia. I am an employee / authorized technical representative of the company, and I manage the app submission and technical deployment for them. My questions: Is an Organization Apple Developer account strictly required for this type of restaurant delivery driver app? Can this be resolved by replying to App Review with company authorization and business documents? Or is converting/updating the Apple Developer membership from Individual to Organization the only practical solution? If I am not the founder/co-founder but I am an employee/authorized representative of the company, can the current Individual membership be updated to Organization, or should the company owner create a new Organization membership? Any guidance from developers who faced a similar 5.1.1(ix) rejection would be appreciated. Thank you.
Replies
2
Boosts
0
Views
89
Activity
1d
Sectigo Public Server Authentication CA DV R36?
When I submit an https web request I receive both of those funny errors. In particular I do not understand what that “Sectigo Public Server Authentication” message represents, perhaps yet another certification for Apple to access the request, when of course by connecting to that web address on Safari produces no errors. Connection error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} (+[PPSClientDonation isRegisteredSubsystem:category:]) Permission denied: Maps / SpringfieldUsage (+[PPSClientDonation sendEventWithIdentifier:payload:]) Invalid inputs: payload={ isSPR = 1; } urlstring=https://taxiprofessional.net/***.php process loading tcp_input [C2.1.1.1:3] flags=[R] seq=2572529641, ack=2572529641, win=251 state=ESTABLISHED rcv_nxt=2572535079, snd_una=3494441675 tcp_input [C2.1.1.1:3] flags=[R] seq=2572535079, ack=2572535079, win=1981 state=ESTABLISHED rcv_nxt=2572535079, snd_una=3494441675 nw_endpoint_flow_failed_with_error [C2.1.1.1 82.223.15.117:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: pdp_ip0[lte], ipv4, dns, expensive, uses cell, LQM: moderate)] already failing, returning nw_endpoint_flow_failed_with_error [C2.1.1.1 82.223.15.117:443 cancelled channel-flow ((null))] already failing, returning Connection 2: received failure notification Connection 2: received ECONNRESET with incomplete TLS handshake - generating errSSLClosedNoNotify Connection 2: failed to connect 3:-9816, reason -1 Connection 2: encountered error(3:-9816) Task <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1> HTTP load failed, 0/0 bytes (error code: -1200 [3:-9816]) Task <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1> finished with error [-1200] Error Domain=NSURLErrorDomain Code=-1200 "Connessione sicura non riuscita a causa di un errore TLS." UserInfo={NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x121bd4240>, NSErrorFailingURLKey=https://taxiprofessional.net/...php, NSErrorFailingURLStringKey=https://taxiprofessional.net/....php, NSErrorClientCertificateStateKey=0, NSErrorPeerCertificateChainKey=( "<cert(0x11bfcca00) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x121a27200) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x122dac000) s: Sectigo Public Server Authentication CA DV R36 i: Sectigo Public Server Authentication Root R46>" ), _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1>" ), NSLocalizedDescription=Connessione sicura non riuscita a causa di un errore TLS., _kCFStreamErrorDomainKey=3, NSUnderlyingError=0x121b7b0c0 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "(null)" UserInfo={_kCFNetworkCFStreamSSLErrorOriginalValue=-9816, kCFStreamPropertySSLPeerCertificates=( "<cert(0x11bfcca00) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x121a27200) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x122dac000) s: Sectigo Public Server Authentication CA DV R36 i: Sectigo Public Server Authentication Root R46>" ), _kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x121bd4240>, _NSURLErrorNWPathKey=satisfied (Path is satisfied), viable, interface: pdp_ip0[lte], ipv4, dns, expensive, uses cell, LQM: moderate, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9816}}, _kCFStreamErrorCodeKey=-9816}
Replies
1
Boosts
0
Views
48
Activity
1d
"Waiting for Review" for 30 days😭😭
Hello, our App (appleId: 6761799912) has stuck in review process since 30+ days ago, I have tried resubmit it for few times, please check the status of our App, thank you!! I understand that review times can vary and that the queue may currently be experiencing higher-than-usual volume. I'm not trying to escalate — I simply want to confirm whether: 1、There is any specific issue or blocker with this submission 2、Any additional information or documentation is required from my side 3、Or whether the app is simply still pending reviewer assignment Thank you
Replies
0
Boosts
1
Views
64
Activity
1d
App Store Server Notification v2: how to distinguish a resubscription that happened in-app from one that happened in Settings → Subscriptions?
Context We're handling App Store subscriptions on the server side using App Store Server Notification v2. Our pipeline currently identifies each event by transactionId and originalTransactionId. A few notes about our client: Our app is built with Flutter and uses the standard in_app_purchase plugin layer to drive App Store purchases (StoreKit 1 under the hood). We have not migrated to StoreKit 2 on the client yet. We have not been setting SKPayment.applicationUsername on outgoing purchases, so every transaction we've ever produced has appAccountToken: null in its v2 notification. This question is purely about what the server-side notification can tell us, given the current client state above. What we're trying to figure out A user can resubscribe to an expired subscription in two different places: In-app — the user opens our app and re-purchases through our normal in-app purchase flow. App Store — the user goes to Settings → Apple ID → Subscriptions and resubscribes from the system UI, without ever returning to the app. Both paths trigger a SUBSCRIBED notification (subtype RESUBSCRIBE) with structurally identical payloads as far as we can tell — same shape for data.transactionInfo, data.renewalInfo, etc. From the notification alone we can't decide which path produced it. The reason this matters: in our system, the two paths require different business handling: In-app path: the user may have signed in to a different business account in our app. The new subscription should be attributed to whoever paid in the app just now, not to the previous owner of originalTransactionId. App Store path: there is no in-app signal, so the business owner can only be inferred from the previous originalTransactionId mapping. If we get it wrong, the subscription's entitlement ends up on the wrong business account. What we do today Because we can't tell the paths apart from the notification, we defer processing for a few minutes and check whether an in-app order for the same transaction has arrived in the meantime: If an in-app order shows up → it's the in-app path; attribute to the in-app account. If nothing shows up after the delay → assume App Store path; fall back to the previous owner mapping. This works but adds latency to entitlement activation and forces us to build a deferred-retry queue with idempotency against the in-app callback path. Possible direction: appAccountToken / applicationUsername We noticed that v2 notifications carry transactionInfo.appAccountToken, and the docs suggest that StoreKit 1's SKPayment.applicationUsername (when it's a valid UUID) is mirrored into this field. In theory, if we start setting it on every in-app purchase from the Flutter client, the field could double as a path discriminator on the server: appAccountToken != null → in-app path (only the app can set it), and we even get the business user id for free appAccountToken == null → App Store path (no UI to populate it) But we have some open questions before committing to this direction: Questions Is there an existing signal in ResponseBodyV2 / JWSTransactionDecodedPayload / JWSRenewalInfoDecodedPayload that distinguishes these two paths, that I might be missing? Can the same distinction be obtained via getAllSubscriptionStatuses / getTransactionHistory / any other Server API endpoint? Is applicationUsername (StoreKit 1) still a reliable way to populate appAccountToken on v2 notifications today? Specifically: Are there format constraints beyond "valid UUID" that cause Apple to drop the value? Any known differences between sandbox and production in how it's mirrored? Does the App Store path ever strip or overwrite a previously-set value when the same originalTransactionId is reused? For existing subscriptions where applicationUsername was never set (which is all of ours today, since we've never polient), is there any way to retroactively distinguish the in-app vs App Store path? Or is timing-based deferred matching theonly option for that cohort, even after we start setting the value on new purchases? If neither (1) nor (2) is currently possible, is the timing-based heuristic we use today the pattern Apple expects developers to follow, or is there a recommended approach we're missing? A small suggestion, if it turns out there's no existing way If the information genuinely isn't exposed today, it might be worth surfacing a salesChannel-style field on the transaction, similar to what Google Play Developer API exposes on Order.salesChannel (IN_APP, PLAY_STORE, etc.). That would let server-side handlers route each event to the correct business owner immediately, regardless of whether appAccountToken was set, and would also cover legacynt never had a chance to populate it. Thanks — happy to share sample payloads or more detail if helpful.
Replies
1
Boosts
0
Views
56
Activity
1d
After enabling Enhaced Security the linker error Library 'c++polyfills' not found occurs (Simulator only)
After enabling Enhanced Security for an existing iOS project (mixed Objective-C / Swift) I get the linker error: Library 'c++polyfills' not found This happens when compiling for a simulator as run destination. Device builds (debug) or archiving a release build works. However I need to be able to test on a simulator... Xcode version is 26.4.1, Simulator uses iOS 26.4.1
Replies
4
Boosts
0
Views
251
Activity
1d
Free sports prediction app with prizes being classified as gambling under Guideline 5.3.4
I’m looking for guidance regarding App Review classifying my app as gambling / real-money gaming under Guideline 5.3.4. My app is a free football prediction competition app where users predict match scores and compete in rankings based on prediction accuracy. Top-ranked users may occasionally receive promotional physical prizes such as headphones, consoles, or other products. Important details: participation is completely free there are no entry fees users cannot deposit money users cannot withdraw money there is no wagering or betting system there are no sportsbooks, odds, or casino mechanics users never risk money to participate prizes are funded directly by the platform as promotional rewards Apple rejected the app under: Guideline 2.3.6 – Accurate Metadata Guideline 5.3.4 – Gaming, Gambling, and Lotteries App Review is stating that the app includes “real money gambling, real money betting, or real money skill-based gaming” and is requesting gambling licenses and geo-restrictions. My understanding was that gambling generally requires users to risk something of value (money/payment/consideration) for a chance to win prizes, which does not happen in this app. I would appreciate guidance from developers who have experience with: Free prediction or fantasy-style apps with promotional prizes Skill-based competitions reviewed by Apple Sweepstakes/contest compliance on the App Store UI/wording that may accidentally trigger gambling classification Whether App Review typically requires legal contest rules instead of gambling licenses in cases like this If anyone has successfully published a similar app, I’d really appreciate hearing what changes or clarifications helped during review. I want to launch initially in Brazil Thank you.
Replies
2
Boosts
0
Views
64
Activity
1d
-startDownloadingUbiquitousItemAtURL:error: and NSURLUbiquitousItemDownloadRequestedKey
I'm trying to update the iCloud data handling in our app, and I'm running into an issue with a particular file on one particular device. This file never downloads & I haven't been able to pinpoint what's off about it. Right now we just have 2 iCloud accounts & a handful of devices, so I haven't been able to narrow it down yet, but in most cases, all the cloud files download as expected. However, whether or not the file eventually downloads, the NSURLUbiquitousItemDownloadRequestedKey key seems to be completely useless. For the following code: NSError *error = nil; BOOL success = [[NSFileManager defaultManager] startDownloadingUbiquitousItemAtURL:self.fileURL error:&error]; if (!success) { NSLog(@"error downloading %@ : %@", self.fileURL, error); } else { NSDictionary *resourceValues = [self.fileURL resourceValuesForKeys:@[NSURLUbiquitousItemDownloadRequestedKey, NSURLUbiquitousItemIsDownloadingKey, NSURLUbiquitousItemDownloadingErrorKey, NSURLUbiquitousItemDownloadingStatusKey] error:&error]; if (!error) { NSString *downloadStatus = resourceValues[NSURLUbiquitousItemDownloadingStatusKey]; bool downloadRequested = [resourceValues[NSURLUbiquitousItemDownloadRequestedKey] boolValue]; NSLog(@"download requested: %d", downloadRequested); } // ... } downloadRequested is always false, regardless of whether or not the cloud file eventually downloads. I have 2 questions: is there a way to actually check if a download has been requested for a file? what could be preventing this file from downloading? -startDownloadingUbiquitousItemAtURL:error: doesn't report an error, NSURLUbiquitousItemDownloadingErrorKey is always nil, and no error is reported in the NSMetadataQuery observer.
Replies
1
Boosts
0
Views
54
Activity
1d
Using Xcode with Claude Opus 4.7
Has anyone got Xcode working with Opus 4.7? I have Claude Code running 4.7, but Xcode insists on running 4.6. Even working with Claude to try to configure Xcode doesn't work. Apparently Xcode does something that prevents using Opus 4.7. Any reason for this? Xcode has a really nice integration, but I guess It's bak to Terminal and Claude Code if I want to use the better Model. Anyone else got this working?
Replies
3
Boosts
0
Views
236
Activity
1d
Background Assets Mac (Designed for iPad)
Hello, I have followed the instructions in https://developer.apple.com/documentation/backgroundassets to setup background asset to work on the iPhone. I am able to confirm successfully test the asset packs locally on the iPhone. However, when I try to run the my test code on the Mac (Designed for iPad), I get this error. BackgroundAssets/AssetPackManager.swift:206: Fatal error: The app couldn’t be validated: The bundle’s info dictionary lacks a string value for the key “BAAppGroupID”. Is this feature not supported on the Mac?
Replies
6
Boosts
0
Views
169
Activity
1d
Setting massProperties on a USDZ-loaded entity corrupts its transform (position/scale → NaN)
Setting massProperties on a USDZ-loaded entity corrupts its transform (position/scale → NaN) Category: RealityKit / visionOS Environment: visionOS 26.x Summary: Modifying PhysicsBodyComponent.massProperties at runtime on an entity loaded from a .usdz file silently corrupts the entity's transform. The translation and scale components become NaN, while rotation remains valid. The corruption occurs during the next RealityKit scene update cycle (e.g., during an await suspension on the main actor). Steps to Reproduce: Author a .usda file with a RigidBody component including valid m_mass and m_inertia values Load the entity at runtime via Entity(named: "MyEntity.usdz", in: bundle) Read the existing PhysicsBodyComponent, modify massProperties, and set it back: if var physics = entity.components[PhysicsBodyComponent.self] { physics.massProperties = .init( mass: 1.944, inertia: SIMD3<Float>(0.013, 0.026, 0.016), centerOfMass: (position: .zero, orientation: .init()) ) entity.components.set(physics) } Add the entity to the scene Perform any await call (e.g., TextureResource(contentsOf:)) that yields to the main actor, allowing a RealityKit scene update to run Expected: The entity retains its position and scale with the updated mass/inertia values. Actual: The entity's transform becomes corrupted: Transform( scale: SIMD3<Float>(nan, nan, nan), rotation: simd_quatf(real: 1.0, imag: SIMD3<Float>(0.0, 0.0, 0.0)), // ← fine translation: SIMD3<Float>(-nan, -nan, -nan) ) Additional findings from investigation: The entity's physics mode does not matter — corruption occurs even when the entity is .kinematic Creating a new PhysicsBodyComponent(...) and replacing the existing one also triggers the bug Modifying other properties on the same component (linearDamping, angularDamping, material, mode) does not cause corruption — only massProperties triggers it The parent entity's transform remains valid The computed mass/inertia values themselves are valid (finite, positive) The corruption is silent — no error, no warning, no crash from RealityKit itself Workaround: Author mass and inertia values directly in the .usda file and do not modify massProperties at runtime: def RealityKitStruct "massFrame" { float3 m_inertia = (0.02, 0.02, 0.038) float m_mass = 2.5 def RealityKitStruct "m_pose" { } } Other PhysicsBodyComponent properties (damping, material, mode) can safely be modified at runtime.
Replies
0
Boosts
0
Views
192
Activity
1d
ARIA Life v1.0 stuck “Waiting for Review” 5 days — Expedited request approved, still no movement
Hi, I submitted ARIA Life (iOS, Version 1.0) on May 4th. It has been stuck in “Waiting for Review” for 5 days with no status change and no emails from Apple. Current average wait time for May 2026 is under 9 hours per live data. I submitted an expedited review request today which was confirmed approved, but the status has still not changed. No messages in Resolution Center, account is in good standing. Is anyone from Apple able to help or has anyone experienced this recently?
Replies
1
Boosts
1
Views
159
Activity
1d
Severe App Review delay since January, app still broken and TestFlight also blocked
Hello, I am posting regarding my app, Apple ID 6755677576. My app was rejected on April 2, and I resubmitted it. After several weeks without any progress, I had to cancel the submission because the delay had become highly abnormal. I resubmitted the app again on April 23, and it is still stuck in “Waiting for Review.” This situation is critical because the live version of the app has contained a severe blocking bug since January 23. Due to these unusually long App Review delays, I have been unable to release the fix, and users continue to leave negative reviews because the app remains broken. In addition, for months, TestFlight builds have also remained pending review for unusually long periods. This means I no longer have any practical way to provide affected users with a corrected version while waiting for App Review, even though they are actively complaining about the blocking bug in the live version. I would like to know whether other developers are currently experiencing similarly unusual delays for both App Store review and TestFlight review. Thank you.
Replies
1
Boosts
1
Views
68
Activity
1d
Stuck in app review
Dear App Review Team, I am writing to escalate an ongoing and critical issue regarding our app review. App ID: 6705133649 Status: Waiting for Review since April 30, 2026 — now over 10 days with no progress. Timeline of events: • April 30 – Submitted for review • ~May 4 – Posted on Apple Developer Forums requesting an update • May 5 – Apple responded: "We're investigating and will contact you in App Store Connect" • May 9 – Followed up again after no contact was made • Today – Still no review, no contact, no explanation We have received no communication via App Store Connect as promised. This is part of a larger pattern we have experienced: • Our reviews previously completed within 48 hours consistently • Our last review cycle took approximately 1.5 months • This current review is now past 10 days with no movement We are formally requesting: Immediate escalation to a senior App Review team member A clear explanation of why this review has stalled Confirmation of whether any action is required from our side A committed timeline for resolution This delay is directly impacting our users and business. We are fully available to provide any additional information, demo credentials, or clarification needed — and will respond immediately to any request. We respectfully ask that this be treated as urgent and resolved within 48 hours. Thank you.
Replies
1
Boosts
1
Views
66
Activity
1d