Overview

Hi everyone, I'm experiencing an unusually long wait time for my TestFlight external build review and wanted to see if others are facing similar issues in 2026. Current Status: Platform: iOS App Version: 1.2.90 (Build 24) Build Type: TestFlight External Testing Current Status: In Review - not "Waiting for Review" Time in Current Status: Over 2 weeks Submission Timeline: Current Submission: Wednesday at 9:49 AM (iOS 1.2.90 Build 24) Previous Submission: March 9, 2026 at 2:20 PM (iOS 1.2.90 Build 11) - Status: Completed (Rejected) Full History: March 9, 2026 2:20 PM - Initial submission (Build 11) March 15, 2026 5:25 AM - Rejection from Apple March 24 - April 15, 2026 - Multiple back-and-forth communications (5 messages total) April 15, 2026 2:22 PM - Last response from Apple Recent (Wednesday 9:49 AM) - Resubmitted new build (Build 24) Current - Still "In Review" after 2+ weeks What I've Tried: ✅ Addressed all rejection issues from the previous review ✅ Submitted a new build with higher build number (11 → 24) ✅ Submitted expedited review request through App Store Connect ✅ Contacted Apple Developer Support via email ✅ Requested phone callback for escalation What Concerns Me: The build has been stuck in "In Review" status for over 2 weeks This is AFTER already going through a full review cycle (rejection + resubmission) Normal review times are supposed to be 24-48 hours, even with the 2026 backlog The previous review cycle took over 1 month (March 9 → April 15) This is completely blocking our beta testing program Questions for the Community: Is anyone else experiencing 2+ week "In Review" times for TestFlight external builds in 2026? Does a previous rejection cause indefinite review delays on resubmission? Has anyone successfully resolved this by canceling and submitting a brand new build? Are there effective escalation paths beyond standard support channels? Could this indicate an account-level review issue? What I Understand: Review times have increased in 2026 due to higher submission volumes Previous rejections can lead to more thorough reviews However, 2+ weeks "In Review" (not even "Waiting") seems abnormal This delay is severely impacting our development timeline and beta testing plans. Any advice or shared experiences would be greatly appreciated! Thanks in advance for your help.

Hi, We are awaiting processing of our enrolment. We have submitted everything and are still waiting. We haven't had any correspondence.

Feedback ID: FB22759977 After clicking add to apple wallet in our app, I launch the PKAddPaymentPassViewController and click next. It loads for a few seconds and then I get: [] ProvisioningOperationComposer: Step '' failed with error Error Domain=PKProvisioningErrorDomain Code=5 UserInfo={PKErrorHTTPResponseStatusCodeKey=500}

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?

Hi everyone, I'm hoping someone has run into this before because it's completely blocking our release. When we try to submit a new version of our app, we get an error saying the Account Holder must accept a pending agreement. The problem is, when the Account Holder logs into App Store Connect, there are no agreements showing up to accept. To make things worse, the Business page is broken — every time we try to open it, it throws an error and won't load at all. This means we can't access the Agreements, Tax, and Banking section through the UI. Things we've already tried: Logging in as the Account Holder (not just an Admin) Trying different browsers and incognito mode Going directly to appstoreconnect.apple.com/agreements/#/ Checking email for any agreement links from Apple Nothing has worked so far. The page just errors out every time. Has anyone experienced this and found a fix? Did you have to go through Apple Support directly to get it resolved? We've already reached out to Apple Support but wanted to check here in case there's a known workaround we're missing. Any help is appreciated!

Hello, My app (Apple ID: 6760485927) has been in "Waiting for Review" status since May 7, 2026 — now over 5 days with no progress and no messages in the Resolution Center. The account is in good standing, all agreements and banking information are active, and no action appears to be required from my side. Could someone from the App Review team please check whether there is any issue with this submission, or confirm that it is simply pending reviewer assignment? Thank you.

Dear App Review Team, I'm following up on our submission with App ID: 6762607820, submitted on April 30, 2026. The build has now been sitting in 'Waiting for Review' for 12 days. During that time, we have received no status update, no rejection, no metadata feedback, and no communication of any kind. We have also reached out via Apple Developer Support regarding this issue and have not received a response from that channel either. A 12-day silence is significantly outside the typical review window Apple publishes. We need clarity on the following: The current status of the submission and the reason it has not entered active review after 12 days A concrete timeline for when the review will begin or conclude Confirmation of whether any internal flag, hold, or routing issue is affecting this build The submission is complete and ready for review on our end. We respectfully ask for a prompt response and resolution. Thank you.

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

When working with an Objective-C project in Xcode 26.5, I'm unable to establish outlet and action connections by dragging between XIB files and the corresponding .h header files. This drag-and-drop connection works perfectly after switching to Xcode 26.3.0. In addition, under Xcode 26.5, drag-and-drop linking works normally for projects using Swift files together with XIB files. The issue only occurs with Objective-C .h files and XIB files.

Hi, We are able to successfully perform in-app provisioning and add cards to the native wallet. However, we are unable to retrieve the existing card status from the wallet. Even when the card is already added to the device or Apple Watch, the status is always returning as false for both. Could you please let us know if there are any additional configurations, entitlements, or issuer onboarding steps required to retrieve the existing card status from Apple Wallet?

Hello everyone, I am currently working on an iPadOS application that requires communicating with a custom hardware board based on the Raspberry Pi RP2040 microcontroller via USB. My initial thought was to use the standard CDC-ACM (virtual serial port) profile on the RP2040. However, my understanding is that iPadOS's built-in system drivers will automatically claim any standard CDC-ACM interfaces, preempting my custom USBDriverKit driver from matching and taking control of the device. Is my assumption correct that iPadOS will strictly preempt a standard CDC-ACM device, making a custom DriverKit implementation impossible for that specific class?

The MagSafe 3 cable is an amazing piece of engineering, showing charged as green and charging as amber. Please consider that "carging," and "full" or "reached charging limit," is green, but in case you are far away, you need an estimate of battery percentage. A software magsafe update, like macOS 26.5 was very noticeable for me, as i have the charging limit set on 80%. A new MagSafe 4 would be a simple MagSafe 3 update, adding a yellow colour. it should be simple, here is the code: // 1. CRITICAL SAFETY CUT-OFF // If the system detects a hardware/thermal failure, // it cuts power and pulses RED. if (criticalError) { setLED(PULSING_RED); return; } // 2. SLOW CHARGER DETECTION // Logic: Air < 30W OR Pro < 70W triggers Pulsing Yellow. if ((isAir() && wattage < 30) || (isPro() && wattage < 70)) { setLED(PULSING_YELLOW); return; } // 3. CAPACITY GRADIENT // Simple, clear visual feedback based on your percentages. if (soc < 50) { setLED(COLOR_AMBER); // 0-50% } else if (soc >= 50 && soc < 90) { setLED(COLOR_YELLOW); // 50-90% } else if (soc >= 90) { setLED(COLOR_GREEN); // 90-100% }

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}

Good Day All, I am new to the forum so not sure if I am posting this in the correct category. I have 2 other apps that are running successfully on appstore so I am not "fresh" when it comes to creating apps. :) but I have hit a wall with the one I am currently busy with and need some help to figure out the next step please. Currently I have a app that is fully built and working perfect in testflight. However, the app connects to specifically Garmin watches to get specific triggers. When you pair the app with your watch it looks for the GarminConnect app on your phone for the details and then links it. I have the companion Garmin app for the watch on the Garmin store and that is approved. All good that also works. But when I send the app for review so I can release it I get the following response from the team : Guideline 5.2.1 - Legal - Intellectual Property Issue Description The app includes content or features from Garmin, or is marketed to control external hardware from Garmin, without the necessary authorization. The inclusion of third-party content within the app, whether retrieved from the internet by the app or embedded in the app, is subject to the terms of the Apple Developer Program License Agreement. The app and its contents should not infringe upon the rights of another party. In the event the app infringes another party’s rights, you are responsible for any liability to Apple because of a claim. Next Steps To resolve this issue, please attach documentary evidence in the App Review Information section in App Store Connect. Once we have reviewed your documentation and confirmed its validity, we will proceed with the review of the app. Alternatively, please remove the third-party content from the app and its metadata. I have sent them : Hi There My app communicates with Garmin watches exclusively through the official Garmin Connect IQ Companion App SDK. I am a registered Garmin developer (developer name: removed) and have accepted the Garmin Connect IQ Developer Agreement, which explicitly licenses the Companion App API for third-party iOS developers. My Garmin watch app is approved and published on the Garmin Connect IQ Store. I have attached: (1) the Garmin Connect IQ Developer Agreement, (2) my Garmin Developer Dashboard confirming registration, and (3) my app listing on the CIQ Store showing Approved status. I dont really know what else to add to confirm that it has been approved from Garmin's side to approve the app in IOS. I have also now attached a screenshot of the app in the GarminApp store showing that it links with IOS (Dashboard3.png) and that was approved on Garmin side. Thanks in advance Message Attachments: Garmin CONNECT IQ Agreement.pdfDownload Dashboard1.pngDownload Dashboard2.pngDownload Dashboard3.pngDownload They responded basically with the same message which I then sent them the details again and now we are stuck in this loop of them asking for that and I am sending what I have which is clearly not what they are looking for. Can anyone please assist by telling me what I need to send to them to get this resolved or what I can do? Thank you!!

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.

I would like to ask for clarification regarding the specifications of Apple Subscriptions. We are currently planning a subscription discount campaign using Offer Codes, and during testing we encountered the following issue. Test scenario: A user who does not have our app installed accesses a URL that contains an Offer Code. The App Store opens and displays the details of the Offer Code. The user reviews the offer and proceeds, at which point the App Store prompts the user to install our app. The user installs the app and launches it. Issue: The subscription remains in an unpurchased state. From the app implementation side, when the app launches, we attempt to retrieve transactions held by Apple using unfinishedTransactions. However, no transaction is returned, so the app cannot transition the user to a subscribed state. In contrast, when a user who already has the app installed accesses the Offer Code URL (step 1), the app can successfully retrieve the unfinished transaction via unfinishedTransactions on launch and correctly switch the user to a subscribed state. Could you please advise on the root cause of this behavior, or whether there is a recommended workaround for this scenario?

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.

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.

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.

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.