Overview

Hi everyone, My iOS app “TaskCal: Task Manager” (version 1.2.8) has been stuck in “Waiting for Review” for more than 3 weeks, and I’m not sure what else I can do at this point. Here are the key dates (GMT+8): Jan 30, 2026 – Version 1.2.3 was approved and marked “Ready for Distribution”. Jan 31 – Feb 8, 2026 – I submitted version 1.2.8 multiple times. Several submissions were later marked as “Removed” in App Store Connect. Feb 9, 2026, 12:39 AM – I submitted version 1.2.8 again. This submission has been in “Waiting for Review” ever since. Today is Mar 3, 2026 (Taipei time) – The status is still “Waiting for Review” with no change. Because of this, I contacted Apple Developer Support multiple times through Contact Support. I only received one reply, on Feb 21, 2026, which said: Hello Alan, Thank you for reaching out to Developer Support about your app, “TaskCal: Task Manager.” I understand that you’re concerned. After reviewing your app’s submission history, I can confirm that your apps is still in the “Waiting for Review” status as of February 8th 2026. To address your concern about the duration of your of the review, I’ve contacted the review team to bring this to their attention. At this time, there’s no further action required from your end. If the review team needs any additional information to complete the review, they’ll reach out to you directly. We appreciate your patience during this process. Your case number is 20000107493507. Stephanie Developer Support Since then, there has been no visible progress and no follow‑up messages. The App Review page still shows: Version: iOS 1.2.8 Status: Waiting for Review Case ID: 20000107493507 I completely understand that review times can vary, but: My previous version (1.2.3) was reviewed and approved normally. This is a relatively small productivity app with no major policy changes. It’s been over 3 weeks in “Waiting for Review” for this specific submission, with multiple earlier submissions of the same version being “Removed” without clear explanation in the UI. My questions: Is there anything I may have done wrong in the submission process (for example, causing multiple “Removed” submissions) that could block or delay this review? Is there any other official channel I can use to get more clarity beyond contacting Developer Support (which only confirmed that it’s “Waiting for Review”)? Has anyone here experienced a similar long “Waiting for Review” state recently, and if so, how was it resolved? I’m worried that there might be some issue with this build or with my account that I’m not seeing in App Store Connect. At the same time, I don’t want to keep canceling and re‑submitting if that could make the situation worse. Any advice from Apple or other developers who have gone through something similar would be greatly appreciated. Thank you, Alan

Hello Apple Developer Support, My app has been stuck in “Waiting for Review” since February 7, and I have submitted multiple inquiries without receiving any response. This delay has now become extremely concerning. Missing a planned launch due to an indefinite review timeline is very difficult for independent developers. If there is an issue with the submission, I would appreciate clear communication. If there are review delays, transparency would help us plan accordingly. I respect the review process, but the lack of updates after this amount of time is frustrating. I would sincerely appreciate clarification on the status. I kindly ask for a specific and personalized response regarding my case, as my previous inquiries received only general or automated replies without addressing the actual issue. Apple ID: 6758804549 Thank you.

My app (App ID: 6757516331) has been stuck in "Waiting for Review" since February 3rd. It has been over a week, and I have not received any updates yet. Any assistance would be greatly appreciated. Thank you.

Hello, We're seeing a high rate of providerDidReset callbacks in production across a large user base (iOS 16, 17, 18, and 26). I'd like to understand both the correct way to handle this delegate method and strategies to reduce its frequency. Background The callback occurs across all iOS versions we support and is not isolated to a specific device or region. The callback can occur in any app state (foreground, background, inactive), however it is most dominant in the background state — particularly during VoIP push notification handling. The callback is more prevalent during long app sessions — for example, when the app has been running continuously for a day or overnight. We do not call CXProvider.invalidate() anywhere in our codebase explicitly. After providerDidReset fires, subsequent transactions fail with CXErrorCodeRequestTransactionErrorUnknownCallUUID (error code 4). Re-initializing the provider via initializeProvider() resolves this error. Our Implementation We use a singleton proxy class (CallKitProxy) that owns the CXProvider. Below is a simplified version — some logging and non-essential parts have been removed for brevity. @objcMembers public final class CallKitProxy: NSObject { private var cxProvider: CXProvider? private let cxCallController: CXCallController private let cxCallObserver: CXCallObserver private override init() { cxCallObserver = CXCallObserver() cxCallController = CXCallController() super.init() initializeProvider() cxCallObserver.setDelegate(self, queue: nil) } private func initializeProvider() { let configuration = providerConfiguration() cxProvider = CXProvider(configuration: configuration) cxProvider?.setDelegate(self, queue: nil) } private func providerConfiguration() -> CXProviderConfiguration { let soundName = SharedUDHelper.shared.string(forKey: .pushNotificationSoundNameForCall) let sound = CallNotificationSounds(name: soundName ?? "ringtoneDefault") let configuration = CXProviderConfiguration() configuration.supportsVideo = true configuration.maximumCallsPerCallGroup = 1 configuration.maximumCallGroups = 1 configuration.supportedHandleTypes = [.phoneNumber, .generic] configuration.iconTemplateImageData = UIImage( named: "callkit_mask", in: .main, compatibleWith: nil )?.pngData() configuration.ringtoneSound = sound.name return configuration } public func requestTransaction( action: CXCallAction, completion: @escaping (Error?) -> Void ) { let transaction = CXTransaction(action: action) cxCallController.request(transaction) { error in completion(error) } } } extension CallKitProxy: CXProviderDelegate { public func providerDidReset(_ provider: CXProvider) { // End any active calls, then re-initialize the provider initializeProvider() } } Questions 1. Is re-initializing the provider inside providerDidReset the correct approach? The documentation states that providerDidReset signals the provider has been reset and all calls should be considered terminated. Should we be calling CXProvider.invalidate() on the old instance before creating a new one? Or is assigning a new CXProvider to cxProvider (which releases the old instance) sufficient? 2. What could be causing providerDidReset to fire so frequently, and how can we reduce it? We're particularly concerned about cases triggered during VoIP push handling in the background and inactive states. Are there known conditions — such as provider configuration changes, app lifecycle events, or system memory pressure — that commonly trigger this callback? And are there any recommended patterns to make the provider more resilient in these scenarios? Thank you.

Hello, My app has been sitting on ‘Waiting for Review‘ for over a week now. Can anyone from App Review or Support check whether there is any underlying issues blocking the review? Apple ID: 6759161730 Thank you

Hello, I have multiple iOS app updates (for already live apps) that have remained in “Waiting for Review” status since early February (approximately 4–5 weeks). These are standard updates (minor improvements / maintenance). All builds are properly attached, agreements are active, and there are no compliance or metadata warnings in App Store Connect. The apps were moved to “Waiting for Review” on February 6–11 and have not progressed to “In Review” since. Has anyone else experienced unusually long review times for updates recently? Could this indicate a queue issue at the account level? I have already contacted App Review Support and one of the submissions was marked for expedited review approximately one week ago, but the status remains unchanged in “Waiting for Review.” Thank you in advance.

My app has been sitting in "Waiting For Review" for a month now, this coming week. I understand that it takes some time to review an app but I didn't realize it takes this long. I have deployed apps in the past and it took 1-2 days only. I just couldn't understand what's taking it that long this time. The app ID of the app I recently submitted is 6756655072. Please provide at least a specific timeframe of the review process so developers can also manage properly. It's really difficult to be patient in something that doesn't even respond properly. Please help and hope you view this post from a waiting developer‘s perspective. Thank you.

My app, which I submitted for review on February 4th and has never been published before, is still showing as "waiting for review." It has been rejected twice before. What is the reason? What is the solution? When will you respond? I did everything perfectly. I performed all the tests on iPhone devices. Everything is in order on my hesaplama.vip domain, including my privacy policy.

My app, which I submitted for review on February 4th and has never been published before, is still showing as "waiting for review." It has been rejected twice before. What is the reason? What is the solution? When will you respond? App ID: 6758409782

Hello Apple Developer Community, I am seeking assistance for my app, Mithaq (Version 1.0), which has been stuck in "Waiting for Review" since February 16, 2026. Submission ID: 1c5e2e35-1171-4348-b26f-236204d0ffc0 Questions: Will the app automatically move into the review queue now that agreements are active, or is manual action required? Should we wait for the current submission, or is it better to "Remove from Review" and resubmit? We have sent follow-up emails and an expedited review request but have received no response. Any guidance from the community or Apple Support would be greatly appreciated. Thank you,

Hello, I have quite a few apps that have been stuck in "Waiting for Review" since February 9th. This is unusual as my previous updates were always processed quickly. Due to the long delay and the number of accumulated updates pending, I decided to reset all submissions today to see if it triggers any movement. Has anyone else experienced this sudden stall with multiple apps and updates recently? Any advice on how to handle this would be appreciated.

I'm working on UI automation tests using XCUITest for an iOS application (iPhone). My goal is to programmatically scroll a view by a very precise number of pixels (e.g., exactly 500 points down). I understand the scroll(byDeltaX:deltaY:) method is not supported on iPhone, so I'm using the coordinate-based drag method as an alternative. Specifically, I am using XCUICoordinate.press(forDuration:thenDragTo:withVelocity:thenHoldForDuration:) to simulate a drag gesture. I calculate a start and end coordinate with a specific vertical offset in points, expecting the view to scroll by that exact amount. However, I'm observing that the resulting scroll offset is not perfectly accurate. There's a consistent error of several pixels, making the scroll amount unpredictable for precise test assertions. Is there a known limitation to the accuracy of coordinate-based dragging for simulating programmatic scrolling? Are there any alternative methods or best practices within XCUITest to achieve a more reliable and pixel-accurate scroll on iPhone, or is this level of precision simply not achievable with the current framework?

I'm using NEPacketTunnelProvider to intercept DNS queries, forward them upstream, and inject the responses back via writePacketObjects(). This works correctly for responses under ~500 bytes. For larger responses (~893 bytes, e.g. DNS CERT records), writePacketObjects() returns without error but mDNSResponder never receives the packet — it retries 3–4 times and then times out. What I have verified: IP and UDP checksums are correct UDP length and IP total length fields are correct Maximum packet size (MTU) set to 1500 in NEIPv4Settings/NEIPv6Settings Approaches tried: Injecting the full 921-byte packet — writePacketObjects() succeeds but the packet never reaches mDNSResponder IP-level fragmentation — fragments appear to be silently dropped Setting the TC (truncation) bit — mDNSResponder does not retry over TCP Truncating the response to ≤512 bytes — the packet arrives but the data is incomplete Questions: Is there a supported way to deliver a DNS response larger than 512 bytes through NEPacketTunnelFlow? Does NEPacketTunnelProvider impose an undocumented packet size limit below the configured MTU? Does mDNSResponder silently discard responses larger than 512 bytes when the original query had no EDNS0 OPT record? Is there a way to signal that larger responses are supported? Are IP-level fragments reliably delivered through writePacketObjects()? Tested on iOS 26.3, physical device.

Hi, We understand that there are IOS specific customization to TS.43 spec for EAP-AKA procedure for carrier entitlements. We need precise info on payload information for the below messages that will be exchanged during RCS activation.

With AI getting so powerful, do you think Swift Student Challenge will change a lot next year? Will Apple update the rules or change what they're judging? Would love to hear thoughts from anyone who's followed SSC for a while.

Hi, I submitted my Swift Student Challenge 2026 app and I'm worried about a build error I got when testing. I have both PlateClassifier_2.mlmodel and PlateClassifier_2.mlmodelc in my Sources folder. Only the .mlmodelc is listed in my Package.swift resources. When building I got: PlateClassifier_2.mlmodel: No predominant language detected. Set COREML_CODEGEN_LANGUAGE to preferred language. Build failed — 1 error Will judges hit this same error? Does having an unlisted .mlmodel alongside the .mlmodelc cause a hard build failure on other machines too, or is this specific to my setup (Xcode 26.2 beta, building to physical device)? Will this get me instantly disqualified? Any help appreciated.

For me it looks like Xcode 26 has problems reading SPM packages from a locally hosted BitBucket git solution. While Xcode 16 work perfectly fine, Xcode 26 fails to load and gives "Server SSH Fingerprint Failed to Verify" as error description. Cleaning build data and DerivedData sometimes makes loading work. Any change in Package dependencies will break it again. Anyone having same problems? How do you handle it?

Hi, I have an update on my app (904057429) that has been waiting for review for over a month. I have requested an expedited review and got the message that it was approved but that was over 2 weeks ago and it's been radio silence since. I have also tried contacting support twice and received generic responses both times. I have seen other developers have app updates reviewed within 24 hours which seems to suggest there is no queue system in place so I'm not sure how this situation will be resolved. Does anyone have any suggestions for what I can do? Thanks

I want to enroll into the Apple developer program but it keep showing me: Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. I am from iraq I contacted the support but they did not give me any solution

Hello iOS Developer Community, I submitted my app for review on February 19, 2026, and as of today (March 3, 2026), its status in App Store Connect still shows “Waiting for Review.” I contacted Apple Developer Support regarding this delay and received the following automated response: “Thanks for submitting your support request. We’ve received your support request and will get back to you as soon as possible. Your case ID is 102831222355.” It has now been more than ten days without any further communication or status update. Could anyone advise on the appropriate next steps in this situation?