Overview

My app update has been in "Waiting for Review" since January 31. This is my second post here, as it appears the App Review team is monitoring these posts, and this is the only place where I’ve seen direct responses. I’ve submitted multiple support requests and called Apple Developer Support several times, but they can only leave messages for the App Review team, which remain unanswered (support case ID: 102819325365). I also requested an expedited review — with no response. This update is urgent for my app and my team. We are currently blocked and losing revenue each day. I would greatly appreciate any information on how much longer this might take, or whether it is worth continuing to wait.

Hi everyone, I have two questions that I hope someone from the community (or Apple team) could help clarify: Use of real Apple Executives in a creative scene In a short introductory scene of my app playground, I included the names and emojis representing Apple executives in a respectful and creative way. There are: No official logos No copyrighted assets No branding elements It is purely fictional and made for storytelling purposes. Would this be acceptable under the submission guidelines, or should all characters be entirely unrelated to real individuals? Submission file concern After submitting my application, I realized I may have accidentally uploaded the wrong ZIP file (I mean I'm not sure tbh). Is there any way to review the exact file that was submitted? Would it be possible to withdraw and resubmit again? If so, would that count as multiple submissions (since only one submission is allowed)? I’d really appreciate any clarification from those who may have experienced something similar or from the Apple team. Many thanks!

Hello, We are facing an issue with performing a DTLS handshake when our iOS application is in the background. Our app (Vocera Collaboration Suite – VCS) uses secure DTLS-encrypted communication for incoming VoIP calls. Problem Summary: When the app is in the background and a VoIP PushKit notification arrives, we attempt to establish a DTLS handshake over our existing socket. However, the handshake consistently fails unless the app is already in the foreground. Once the app is foregrounded, the same DTLS handshake logic succeeds immediately. Key Questions: Is performing a DTLS handshake while the app is in the background technically supported by iOS? Or is this an OS-level limitation by design? If not supported, what is the Apple-recommended alternative to establish secure DTLS communication for VoIP flows without bringing the app to the foreground? Any guidance or clarification from Apple engineers or anyone who has solved a similar problem would be greatly appreciated. Thank you.

Hi everyone, I’m implementing subscriptions using StoreKit v2, and I’ve noticed a behavior change starting with iOS 26.1. I’d like to ask if anyone else has experienced the same issue. ■ Issue Immediately after purchasing a new subscription, the value of auto_renew_status (or autoRenewStatus) returned in the receipt is 0 (auto-renew OFF). This issue occurs on iOS 26.1. On iOS 26.0 and earlier, the same parameter returned 1 (auto-renew ON) right after purchase. Sometimes, after executing a “restore” operation, the value changes to 1 later. Since we’ve been using this parameter to determine whether a user’s subscription is active or not, the current behavior is causing some difficulties on our end. ■ Questions Has anyone else observed this issue (where autoRenewStatus is 0 immediately after purchase on iOS 26.1 or later)? How are you handling or working around this behavior in your implementation? If autoRenewStatus is unreliable, we’re considering determining the subscription state based on receipt fields instead. Would this approach be reasonable? "status" is 1 (indicates active subscription) "expire_time" is in the future "deleted_at" is null If anyone has encountered the same behavior or knows of any Apple-recommended implementation approach, I’d really appreciate your insights. Thank you! 🙏

Hello everyone, My app (App ID: 6758463939) has been waiting for review since February 3 and the status has not changed since then. All issues from the previous rejection were fixed: App name corrected and now matches after installation Demo account with full access provided All requested changes completed I also contacted App Review through Resolution Center and opened a support case, but have not received any response yet. I just want to confirm that everything is normal and that the app is still in the review queue. Has anyone experienced similar delays recently with first submissions? If there is any additional step I should take or another place to contact Apple, please let me know. Thank you.

Hello everyone, I’m currently experiencing unusually long wait times for app reviews and wanted to check if others are seeing similar delays this week. Here is the current status of my submissions: App Store Update: Stuck in "Waiting for Review" much longer than the typical 24–48 hour window. New Version: A newly submitted version also seems to be stalled in the initial phase. TestFlight Processing: Even TestFlight builds are taking longer than usual to process. Expedited Review: I've attempted an expedited review request and direct communication, but the status remains unchanged so far. What’s confusing is that I see other apps in the same category receiving updates, so I’m unsure if this is a localized technical glitch or a broader delay affecting a specific group of developers. I’m not looking to escalate anything just yet; I’m simply trying to gauge if this is a widespread issue at the moment. I would greatly appreciate any insights into your recent experiences or if you've noticed similar patterns over the last few days. Thanks in advance, and good luck to everyone with pending submissions! 🙂

Context: Xcode 16.4, Appkit In a windowController, I need to create and send a mouseDown event (newMouseDownEvent). I create the event with: let newMouseDownEvent = NSEvent.mouseEvent( with: .leftMouseDown, location: clickPoint, // all other fields I also need to make window key and front, otherwise the event is not handled.   func simulateMouseDown() { self.window?.makeFirstResponder(self.window) self.calepinFullView.perform(#selector(NSResponder.self.mouseDown(with:)), with: newMouseDownEvent!) }   As I have to delay the call( 0.5 s), I use asyncAfter: DispatchQueue.main.asyncAfter(deadline: .now() + 0.5, qos: .userInteractive) { self.simulateMouseDown() }   It works as intended, but that generates the following (purple) warning at runtime: [Internal] Thread running at User-interactive quality-of-service class waiting on a lower QoS thread running at Default quality-of-service class. Investigate ways to avoid priority inversions I have tried several solutions, change qos in await: DispatchQueue.main.asyncAfter(deadline: .now() + 0.5, qos: ..default) call from a DispatchQueue let interactiveQueue = DispatchQueue.global(qos: .userInteractive) interactiveQueue.async { self.window?.makeFirstResponder(self.window) self.calepinFullView.perform(#selector(NSResponder.self.mouseDown(with:)), with: newMouseDownEvent!) } But that's worse, it crashes with the following error: FAULT: NSInternalInconsistencyException: -[HIRunLoopSemaphore wait:] has been invoked on a secondary thread; the problem is likely in a much shallower frame in the backtrace; { NSAssertFile = "HIRunLoop.mm"; NSAssertLine = 709; }   How to eliminate the priority inversion risk (not just silencing the warning) ?

I keep submitting versions of my app, but days go by without review, and I am forced to resubmit (development does not stop obviously). It has now been 8 days since I have been trying to submit 1.1, with no success. Previously review happened within 12-24 hours. What happened? This is a key time in my development, as the first update has many improvements, and I have fresh installs that I don't want to disappoint. Please help me out. App ID: 6758430790

Hello everyone, My app (App ID: 6758463939) has been waiting for review since February 3 and the status has not changed since then. All issues from the previous rejection were fixed: App name corrected and now matches after installation Demo account with full access provided All requested changes completed I also contacted App Review through Resolution Center and opened a support case, but have not received any response yet. I just want to confirm that everything is normal and that the app is still in the review queue. Has anyone experienced similar delays recently with first submissions? If there is any additional step I should take or another place to contact Apple, please let me know. Thank you.

We received a DPLA compliance notification from Apple referencing Section 11.2(g) for our developer account (REVSTREAM LLC). We responded promptly and have taken corrective measures to ensure full compliance. However, when attempting to send a follow-up message through the developer.apple.com/contact form (Membership and Account → Agreements and Contracts), we receive the error: "There was a problem processing your request." We are unable to reach Apple Developer Support through this channel to confirm our response was received and to provide additional information. Could the @Apple team please advise on an alternative way to communicate regarding this matter? We want to ensure we are fully addressing all concerns. Thank you.

Description On macOS, system-level autocomplete suggestions appear in <textarea> elements even when all relevant HTML attributes intended to disable autocomplete and text assistance are explicitly set. Is this behavior intentional, or is there any supported way for developers to control or disable this functionality? Steps to Reproduce Send yourself an email using the native macOS Mail app containing a verification code (for example). Focus an HTML <textarea> element in any web application. Focus the textarea. Expected Result The autocomplete popup should be controllable from the code, and it should be possible to fully disable it using standard HTML attributes or browser APIs. Actual Result The system autocomplete popup appears in all cases and cannot be controlled or disabled by the code, even when all known attributes (autocomplete="off", autocorrect="off", autocapitalize="off", spellcheck="false") are set.

Hi everyone, I’m running into a strange issue with UISearchController placement with iOS 26 SDK. In one of my view controllers, I was able to move the search bar to the top of the navigation bar by setting: navigationItem.searchController = searchController navigationItem.hidesSearchBarWhenScrolling = false navigationItem.preferredSearchBarPlacement = .stacked This works as expected — the search bar is placed at the top. However, in another view controller with almost identical configuration, the search bar always shows up at the bottom. If I delay the setup with DispatchQueue.main.async, it appears at the bottom; if I don’t, it doesn’t appear at all. Both VCs are wrapped in their own UINavigationController. So my questions are: Has anyone faced this issue where preferredSearchBarPlacement = .stacked is ignored? Are there hidden requirements or limitations for placing the search bar at the top? Why could the same setup behave differently in two controllers? Any help or ideas would be appreciated!

I want to know if the program written in C language can be implemented through the software package, write a software package containing C language on Xcode, and then apply it in Swift Playground.

I have an App stuck in waiting for review. ’ve raised an expedite request and still no response. Anyone experiencing this and know how to get a review in this case?

Hi everyone, I’m currently experiencing unusually long review waiting times and wanted to ask if others see the same behavior this week. My situation: App Store update has been in “Waiting for Review” significantly longer than usual, my apps are pending from last 2 weeks. I’m not trying to escalate anything just looking to understand if this is currently affecting more developers. Would really appreciate hearing about your recent experiences.

Environment OS: iOS 26.2 ~ 26.3 SDK: Xcode 16.4 (Target: iOS 17.6) Framework: StoreKit 2 Environment: Production (Cannot reproduce in Sandbox or Xcode Configuration) Issue Description We are encountering a critical purchase failure that occurs exclusively in the Production environment. When a user who has a "Pending Downgrade" (scheduled for the next renewal date) attempts to re-purchase their current higher-tier product to cancel the downgrade, StoreKit 2 returns an error. Steps to Reproduce User is currently on "Product A" (Higher Tier). User schedules a downgrade to "Product B" (Lower Tier). The status changes to "Pending Downgrade". User attempts to purchase "Product A" again via Product.purchase(). The system purchase sheet appears, and the user confirms the purchase. Immediately after authentication, a system alert from StoreKit appears saying: "Cannot process request at this time. Please try again later." (現在リクエストを一時的に処理できません。しばらくしてからもう一度お試しください。) After dismissing the alert, the app receives StoreKitError code 2 (unknown) with the localized message: "Request could not be completed" (リクエストを完了できません). Technical Observations Transaction.currentEntitlements: Does not change. App Store Server Notifications (V2): No notifications are sent to our server. Sandbox Behavior: Works perfectly. Re-purchasing Product A successfully cancels the downgrade and the subscription remains at the Higher Tier. AppStore.sync(): Running a manual sync does not resolve the pending state after the error. Question Since we cannot debug production-level logs, we are stuck. Is this a known regression in the StoreKit 2 commerce engine regarding state synchronization for downgrades? Has anyone found a workaround for this specific scenario? Any insights would be greatly appreciated.

Hello everyone, I’m currently trying to enroll in the Apple Developer Program, but I received the message: “Your enrollment in the Apple Developer Program could not be completed at this time.” I contacted Apple Developer Program Support and received a case ID, but so far I haven’t received clear guidance on what specifically needs to be fixed or verified. I’ve checked the following already: Apple ID information matches my legal identity Two-factor authentication is enabled Payment method is valid Address and country details are correct I’ve noticed several similar reports in the forums and even blog posts describing long delays or no resolution, so I wanted to ask developers who experienced this: Did your enrollment eventually get approved after waiting? Did Apple ever explain the issue? Is it better to wait for support to resolve the case, or create a new Apple ID and restart the enrollment process? I’d really appreciate hearing your experiences or any steps that helped resolve this. Thank you!

Hello, I recently purchased the Apple Developer Program and the payment is visible in my Apple subscriptions as active. However, when I open the Apple Developer app, I see the message:“Enrollment through the Apple Developer app is not available for this Apple Account.” When I follow the link to enroll via the website, it asks me to pay again even though I have already been charged. I have contacted support twice but haven’t received a response yet. It seems like my enrollment is stuck or not finalized. Has anyone experienced this before? How did you resolve it? Thanks in advance.

Hello, I am attempting to enroll in the Apple Developer Program as an Organization. During the email verification step, I encountered a technical error: no verification code was sent to my email (I confirmed the email address was correct and checked all folders). There was no "Resend" button available on the screen. After refreshing the page to try and fix the UI glitch, I was immediately blocked with the following error: "Contact us to continue your enrollment. You’ve exceeded the maximum number of attempts. Please contact us." I have already opened a support ticket (Case ID: 102824565622), but since this is a time-sensitive corporate enrollment, I am looking for advice. Any help from the community or an Apple representative would be greatly appreciated. Thanks in advance, Yoni

When you share a Url from any Google product, it creates a share.google minify Url. When iMessage fetch the Url meta headers, it receives the og:title, og:url, og:site_name, og:image. But it only show the preview card with og:image, og:title, and og:site_name, ignoring the value of og:description.