Overview

Each time I launch a Debug version of the app on iOS Simulator, I see the Launch Screen presented and then about a 30-second delay before the app is responsive and debug output appears in the console panel. Filed FB22345091

I'm investigating repeated WindowServer watchdog kernel panics on a Mac mini M6 running macOS 27.0.1 (build 26A434), and would appreciate technical guidance on identifying the initiating failure. System configuration Mac mini M6, 16 GB unified memory macOS 27.0.1 (26A434) Redmi G Pro 27U external monitor Physical output: 3840 × 2160 @ 160 Hz, RGB 10-bit HDR10 USB-C-to-DisplayPort 1.4 direct connection, HBR3 ×4, DSC enabled Similar system-level crashes have occurred over both HDMI and DisplayPort The system has experienced repeated freezes and forced restarts over several days. Kernel panic signature userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds WindowServer initialization not complete (post IOKitWaitQuiet)Some WindowServer recovery diagnostics involve IOMobileFramebuffer and IOMobileGraphicsFamily-DCP. Latest incident: October 24, 2026 (UTC+08:00) At 01:33:25.578, the unified log began recording repeated messages: DCPEXT1:GMailboxHandler.cpp:232 apt firmware: immediate_swap_denied landed frame_id = 1, reason = 1At 01:33:35.612, WindowServer reported: [Watchdog] display 1 has become stuck after 10.00154s of unreadiness (2463 failures)Approximately 14,264 immediate_swap_denied messages were recorded in the retrieved interval ending at 01:34:55, followed by a system restart around 01:35. The corresponding panic report is: panic-full-2026-10-24-013618.0002.panic What I have checked The failures are not limited to one video connection type. The physical display signal is 4K 160 Hz, not 5K 160 Hz. The 5120 × 2880 value reported by HiDPI utilities represents the internal scaling buffer. Crashes occurred before BetterDisplay was first used. The latest incident occurred while viewing a remote desktop stream, but available process-count samples did not reveal proliferation of the remote-control processes. Memory/resource pressure remains under investigation; there is not enough evidence to attribute the panics to memory exhaustion. It is unclear whether the initial WindowServer stall precedes or follows the DCP frame-swap errors. Questions What does immediate_swap_denied with frame_id=1, reason=1 indicate in the Apple DCP display pipeline? Can this error be a downstream symptom of an already-stalled WindowServer, or does it suggest a DCP/display frame-submission failure? Is there a known macOS 27 issue involving WindowServer watchdog failures or recovery stalls in IOMobileGraphicsFamily-DCP? What additional diagnostics would help distinguish a macOS display firmware/driver problem from external-display compatibility, memory pressure, or defective hardware? I can provide the panic report, WindowServer diagnostic samples, relevant unified-log extracts, display configuration information, and a sysdiagnose through Feedback Assistant. Feedback Assistant report: FB25300098 Any guidance from Apple DTS engineers or developers who have encountered a similar DCP/WindowServer failure would be appreciated.

I'm posting here after 8 months of back-and-forth with Developer Support (case 102685152651) because I've exhausted that channel and need to know if others have experienced this or if any Apple engineers can advise. The issue: When a user types "Dabah" — the exact name of my app — the App Store autocorrects/redirects to "Sabah." My app does not appear in those results. It only appears when the user searches "Dabah recipes." This means users who know the app by name cannot find it unless they add a secondary keyword. What makes this clearly a system-level bug, not a ranking issue: The same behavior occurs inside Apple's own Developer Marketing Tools portal. Searching "Dabah" returns only Sabah-related apps. Searching "Dabah recipes" finds my app immediately. This is not a user-facing algorithm issue — it's happening in an internal Apple tool. "Dabah" is a unique, uncommon word with no major competing apps. There is no legitimate reason an exact-name search should be overridden. The app has been live on the App Store since mid-2024, is properly indexed (it surfaces on keyword searches), and has "Dabah" listed as a keyword. The problem is specifically in the autocorrect/normalization layer treating "Dabah" as a misspelling of "Sabah." I've submitted screen recordings demonstrating both behaviors. Developer Support has confirmed my ticket is with the engineering team, but I've received no resolution or timeline in 8 months. Has anyone else encountered autocorrect overriding an exact app name match? Is there a known path to escalate search indexing bugs beyond the standard Developer Support channel? App: Dabah (id6745241806) Category: Food & Drink

I’m an independent developer and my app, TalkCity (version 1.0.3, build 23648159), has been in review for an unusually long time: September 1 — first submission September 7 — resubmission September 25 — resubmission October 1 — latest resubmission October 23 — still “In Review” That’s 52 days since the first submission and 22 days since the latest one, with no decision. I’ve contacted Developer Support several times. My expedited review request was accepted, and Apple confirmed the app is still under review, but no timeline or further information was given. I’m not asking for automatic approval, just a decision. If something needs to be fixed, I’ll fix it right away. If the review needs more time, any indication of why would help me plan the launch. To other developers: Has anyone had a review take this long? Has anyone had an expedited request accepted without visible progress? Is there an effective way to escalate beyond the standard support replies? Thanks in advance for any advice.

Our organization enrollment (Enrollment ID S9SZ49Y7M5, DG MIDDLE EAST TECHNOLOGIES - L.L.C - S.P.C, UAE) was accepted after document verification, and the Program License Agreement is accepted. 09/10/2026: purchased the membership (order W1781979751, AED 379). The card was charged, but the order was later canceled without notice. The account has shown "Pending — Purchase your membership" ever since. Since then, every attempt to purchase again fails with "Authorization Failed – A request to your bank … was declined." We tried several cards: Jordanian Visa/Mastercard, Apple Pay, and two UAE-issued cards. The banks show no declined transaction, so the payment seems to be stopped on Apple's side. Support cases 102996084487 (14/10) and 103000637398 (18/10) have had no response. Phone callback shows "temporarily unavailable due to high call volumes".

Hello Apple Developer Community, We are developing an iOS application using StoreKit 2 with four consumable in-app purchase products. All four products have been successfully purchased using real Apple Sandbox transactions on a physical iPhone. The transactions were verified using the App Store Server API, and our backend credited the corresponding virtual points exactly once. However, we are encountering an issue when attempting to request a refund using StoreKit 2. Environment Xcode 27.0 Physical iPhone Apple Sandbox tester account StoreKit 2 Consumable in-app purchases App Store Server Notifications V2 Steps to reproduce Complete a consumable in-app purchase using an Apple Sandbox tester. Confirm that the transaction is verified and not revoked. Invoke the StoreKit 2 refund request sheet using beginRefundRequest. The Apple-provided interface displays a connection-related error. The API returns cancelled. Expected result The Sandbox tester should be able to submit a refund request through the supported Apple refund flow. Actual result The refund sheet displays a connection-related error and returns cancelled. No refund is confirmed, and the transaction remains non-revoked. We have successfully received a TEST notification through App Store Server Notifications V2, but this does not validate an actual REFUND notification. Questions Is beginRefundRequest supported for consumable in-app purchases in Apple Sandbox? Is this connection-related error a known Sandbox limitation? Is there an alternative supported way to generate a real Sandbox refund event? What is the recommended approach to validating the complete refund lifecycle, including App Store Server Notifications V2, for consumable products? Any guidance from Apple engineers would be greatly appreciated. Thank you!

What happens Since installing macOS 27.2 b2 (didn't go through b1, might have been there already), the Contacts app has become almost unusable on my two Macs. Opening a contact or moving to the next one often freezes the app for 8 to 10 seconds, with the spinning wheel. It happens many times in a row while browsing the address book. It comes back no matter what I try: restarting, letting iCloud resync the contacts, deleting and recreating cards. Once, it seemed to go away for a couple of minutes upon restarting, but it returned. Both Macs share the same iCloud account (~690 contacts): a MacBook Pro M4 Pro and a Mac mini M4, both on 27.2 b2 (26B5091g). Reported as FB24928119. Technical details All 18 Contacts_*.spin reports show the main thread blocked in CNCDContactFetcher withLockedContext_fetchPosterData, waiting on a synchronous XPC call to com.apple.contacts.poster.api. That service is postersyncd, which syncs Contact Posters. The kernel kills postersyncd with exceeded mem limit: InactiveHard 20 MB (fatal) at 30–35 MB. launchd relaunches it every ~10 s: 74 kills in 26 h on one Mac, 54 in 24 h on the other. log stream --level debug shows the same sequence on every relaunch: START: Background cleanup → Potential cleanup for missingLocalContactIdentifiers → FetchingContacts → killed within the same second. The cleanup never finishes, so it restarts forever. The poster store (group.com.apple.contacts/ContactsMetadata) is ~85 MB, with blobs of up to 9 MB each. The memory limit stays InactiveHard even while Contacts is frontmost. Moving the poster store aside doesn't help: iCloud rebuilds it in ~25 s. Posters deleted from iOS or iCloud.com get a deletion date but are never purged. Question: has anyone else seen this on 27.2 b2? Is there a way to reset the Contact Posters data stored in iCloud?

Hello, New individual developer account (enrolled October 2026). My first iOS app cannot be tested via TestFlight. 1) Internal testing: builds 1.1.2 (16), (17), (18) and (19) all show "Testing" in my internal group. Two different internal testers (Account Holder and a Marketing-role user) on two different iPhones (iOS 26) get: "Could not install. The requested app is not available or doesn't exist." App Store Connect shows 2 invites but 0 installs for every build. 2) External testing: when I add build 19 to an external group and press "Submit for Review", App Store Connect says: "There was an error processing your request. Please try again later." Already checked: membership active, Free Apps Agreement active, export compliance answered, build metadata "Validated" (SDK 23F81a, min iOS 15.0), pricing Free and available in Türkiye, testers accepted the invitations, TestFlight reinstalled, devices restarted. Developer Support case: 102998773608 (opened October 16, no reply yet) Feedback: FB25298826 Screenshots attached: (1) the install error on iPhone (Turkish UI: "Could not install ASG – Afyon Scooter Derneği. The requested app is not available or doesn't exist."), (2) the App Store Connect error when submitting build 19 to the external group. I don't have a Mac, so I can't attach Xcode device logs; builds are made with Codemagic. Could someone from Apple please check whether a TestFlight/beta setting is missing on my account? Thank you.

Hi, I'm running into two related issues in App Store Connect under Business > Agreements, and Apple Developer Support hasn't responded to my case in a while. U.S. Form W-8BEN — On Line 2 ("Country or Region of Citizenship"), the field is automatically set to Thailand and is read-only. I am a Russian citizen; Thailand is only my current country of residence, not my citizenship. I have not submitted the form yet, and there's no way to edit this field myself. Bank Account stuck in "Processing" — my bank account (Citibank NA, United States, USD) has been in "Processing" status for two weeks with no change, despite all tax information being submitted. This seems to be blocking the Paid Apps Agreement from activating. Has anyone run into either of these and found a way to resolve it, or know the right way to escalate? Thanks in advance.

I’m an independent developer and my app, TalkCity (version 1.0.3, build 23648159), has been in review for an unusually long time: September 1 — first submission September 7 — resubmission September 25 — resubmission October 1 — latest resubmission October 23 — still “In Review” That’s 52 days since the first submission and 22 days since the latest one, with no decision. I’ve contacted Developer Support several times. My expedited review request was accepted, and Apple confirmed the app is still under review, but no timeline or further information was given. I’m not asking for automatic approval, just a decision. If something needs to be fixed, I’ll fix it right away. If the review needs more time, any indication of why would help me plan the launch. To other developers: Has anyone had a review take this long? Has anyone had an expedited request accepted without visible progress? Is there an effective way to escalate beyond the standard support replies? Thanks in advance for any advice.

Requesting staff review. Team ID: RMHZ6VXS4C (individual, Account Holder, India). Case ID: 103000814312. What happened My Apple Developer Program membership lapsed. I renewed it on 18 October 2026. developer.apple.com/account → Membership details now shows the renewal: Renewal date October 18, 2027, annual fee US$99. So the renewal is recorded on my account. Even so, App Store Connect still shows "Your Apple Developer Program membership has expired," and the agreement banner that used to be there disappeared without anything to accept. App Store Connect → Business → Agreements lists no agreements at all. Notarization has failed the whole time. Every notarytool call returns: HTTP status code: 403. A required agreement is missing or has expired. This request requires an in-effect agreement that has not been signed or has expired. This happens with xcrun notarytool history as well as submit, using an app-specific password and the Team ID above. Last checked 23 October 2026. What I have checked The US$99 renewal was charged on 18 October 2026. I am the Account Holder, and there is no pending agreement to accept anywhere on developer.apple.com/account or in App Store Connect. My Developer ID Application certificate for this team is valid; code signing works, only notarization is refused. I corrected my membership address (city/state) on 23 October in case an identity check was holding the renewal. Impact I distribute a macOS app outside the App Store under Developer ID. Without notarization, new users get Gatekeeper's "Apple could not verify" block, so I am shipping unnotarized builds as a stopgap and my launch is on hold. I emailed Developer Support a week ago (case above) and have had no reply; the contact form offers no phone or callback option for India. Ask Could someone on the Developer Program team check why this team's membership shows as renewed on the account page but expired for App Store Connect and notarization, and push it through, or tell me what is still missing on my side? Happy to provide the receipt and logs.

Hello, Our first app, Juno and the Dragon King (Apple ID 6817828591, submission ID 9374ef26-560c-4aef-8086-e06298512921), received a Guideline 2.1 Information Needed request on 13 October. We replied the same day with a screen recording and full answers to all six questions. The app has been in Waiting for Review ever since, now 10 days. We requested an expedited review on 18 October, asked App Review for a phone call, and opened Developer Support case 103003156236 on 20 October. We have had no response to any of these. It is a simple offline platform game with no accounts, no in-app purchases, no user content and no data collection. Could someone please look into this submission? Thank you.

I'm building an App, that is drawing power values in the Dynamic Island area. So the primary indicator is a circle presenting the charge. I've noticed the first issue with this in the landscape orientation, that it then gets clipped by the camera. So I've moved it a few pixels up, which also makes it look really snug with equal distance to the upper outline of the layout. However this then causes issues, when my app gets pushed into the minimal detached position. This is the same view and I can't seem to differentiate, which is which. So either I offset the camera and clip in the detached island or i render perfectly there and clip the camera. iOS 27 added isDynamicIslandLimitedInWidth, which sounds like the right indicator, but what's there before? I've tried measuring the area to get any indication, but it's equal in all regards. Did anyone solve this?

My Apple Developer Program organization enrollment was accepted on Oct 15. The only step left is the membership payment. When I continue to payment, the page hangs and then shows "redirected too many times." I tried two different cards with the same result, and other online payments work fine. In the Apple Developer app I get "Enrollment through the Apple Developer app is not available for this Apple account." I have an open support case but have only received automatic acknowledgments. Can the Developer Support / Enrollment team please review this manually, repair the stuck purchase or allow payment another way, without cancelling the approved enrollment? Has anyone else gotten past this state, and how? Thank you.

Is anyone else feeling deeply disappointed by the lack of communication around App Review? I submitted my iOS app on October 6. As of October 24, it is still “Waiting for Review” — approximately 18 days later. I contacted Apple Developer Support on October 13 and followed up on October 22. So far, I have received no response explaining what is happening, whether anything is wrong with my submission, or whether I need to take any action. For reference, here are the details of my submission: App ID: 6817446637 Platform / Version: iOS / 1.0.0 Submitted: October 6, 2026, at 14:18 JST (UTC+9) Current status: Waiting for Review Support case: 102995107676 Reading other threads here, I have seen developers describing similar experiences: prolonged waits, unanswered inquiries, and no clear indication of what to do next. Seeing those reports makes this situation even more discouraging. I understand that review times vary and that some apps require additional checks. I do not expect an annual membership fee to guarantee approval or priority treatment. But we pay an annual fee to participate in the Apple Developer Program, and I think it is reasonable to expect basic communication and a meaningful response when something appears to be stuck. Waiting more than two weeks without review starting is frustrating enough. Having no response to a support inquiry after 11 days makes it much worse. Even a brief explanation that the case is being investigated, or an indication of when to expect an update, would make a difference. As an independent developer who has put considerable time and effort into building an app, this experience has been deeply disappointing. In my view, this level of communication is not acceptable for a paid developer program. For others who have been in this situation, did you eventually receive a response or find a way to get the issue investigated? Was there a specific support channel that actually helped? If Apple staff are reading this, I hope you will take these experiences seriously. Developers should not have to post publicly just to find out whether their submissions and support requests are being handled.

Hello App Review, Our first iOS release has been in "Waiting for Review" since September, 30 at 3:01 PM CST and has never moved from this step. App: RetireRight Military Apple ID: 6810867467 I sent an email via the developer website requesting assistance on October 19 and was assigned Case ID: 103001700822 Please look into this issue for me. Thank you.

I see a yellow banner on my App Store Connect page with the following message: Apple Developer Program License Agreement Updated The updated Apple Developer Program License Agreement needs to be reviewed. In order to update your existing apps and submit new apps to the App Store, the Account Holder must review and accept the updated agreement by signing in to their account on the Apple Developer website. I am the account owner and I don't see any option to accept the license agreement. I see that the last agreement was signed on 13th December 2021 and it is accepted. I don't see any other agreements anywhere. I am unable to release any apps due to this issue. Does anyone know how to resolve this, please?

Environment: macOS 26.6.2 (25G83) Xcode 26.6 (17F113) macOS command-line process Security.framework SessionGetInfo ASID obtained from the kernel-provided audit token in a received Mach message I’m implementing a security-sensitive Mach IPC receiver. The receiver obtains the sender’s audit token from the Mach message trailer and derives the sender PID, effective UID, and audit session ID (ASID). The sender executable identity is validated separately. Given the ASID, SessionGetInfo can successfully return the corresponding SecuritySessionId and session attributes. The question is about the freshness and synchronization semantics of that lookup. At the point where the receiver authorizes a request, can a successful SessionGetInfo(asid, ...) result be treated as authoritative evidence that the corresponding login/audit session is still currently valid? In particular: What happens if the session logs out, terminates, or is revoked concurrently with the lookup? Can SessionGetInfo successfully return information for a session that is no longer current due to caching or propagation delay? Are there documented ordering or synchronization guarantees between session termination and subsequent SessionGetInfo calls from another process? Can the lookup block for an unbounded period if the underlying security service is unavailable? Is there a supported timeout or cancellation mechanism? Is there another supported public macOS API better suited to establishing authoritative current-session liveness for an ASID obtained from an audit token? The security requirement is fail-closed. I’m specifically trying to avoid private APIs, process-table heuristics, diagnostic launchctl output, or assumptions that the ASID encoded in a previously received audit token necessarily represents current session state. If the public API does not provide an authoritative liveness/freshness guarantee, confirmation of that limitation would also answer the design question. I also have a minimal 122-line Xcode sample that: creates and receives a Mach message, reads the kernel-provided audit trailer, extracts the ASID, calls SessionGetInfo, and prints the returned session ID and attributes. I can provide the sample project if useful.

Title: App stuck in "Waiting for Review" for over 10 days I submitted my app for review over 10 days ago, and its status is still "Waiting for Review." Apple states that 90% of reviews are completed within 48 hours, so this seems unusually long. I've contacted Apple Developer Support twice without receiving a response. Is there anything else I should be doing, or is there a way to have someone investigate or escalate the issue?

I have so far been unable to enrol a macOS 27 beta VM in to Jamf since initial beta release. Is this by design? I can’t find any documentation or posts on apple developer forums about this anywhere. My agentic coding session has done some probing around in the VM and it thinks something is going wrong with Secure Keychain within the VM. Everybody on my team is observing the same behaviour as this, and I’ve had it happening across two different laptops (one of them which is, itself, running the latest macOS 27 Beta, and the other which I created a Beta VM by installing Tahoe in the VM, logging in to iCloud, and enabling Beta channel updates) The only thing we’ve found we can do so far is to join to Jamf in Tahoe first, but the problem I have there is, often times the option for Beta channel updates just doesn’t present itself in System Settings -> Software Update after signing in to iCloud, and I don’t know why it sometimes does but often doesn’t. Logs from agentic coding session below: The core log evidence This is the whole causal chain, from the 27 guest's unified log, inside 370 microseconds. Innermost failure first: 05:24:04.967316 apsd: (CryptoTokenKit) [com.apple.CryptoTokenKit:sepkey] <sepk:* kid=0000000000000000>: (apsd) unable to generate key: error e00002e2(-536870174) ACL=<SecAccessControlRef: dk;ock(true);odel(true);osgn(true);oa(true);okd(true)> 05:24:04.967433 apsd: (Security) [com.apple.security:seckey] SecKeyCreateRandomKey_ios failed: NSOSStatusErrorDomain Code=-25308 "Failed to generate keypair" (errSecInteractionNotAllowed / Interaction is not allowed with the Security Server.) 05:24:04.967574 apsd: (DeviceIdentity) com.apple.MobileActivation.ErrorDomain Code=-1 "Failed to create reference key." 05:24:04.967600 apsd: [com.apple.apsd:courier] APSBAAClientIdentityProvider failed to obtain a BAA cert, error: com.apple.MobileActivation.ErrorDomain Code=-1 "Failed to create reference key." 05:24:04.967686 apsd: [com.apple.apsd:courier] <APSCourierConnectionManager; production>: Stream error occurred for : APSErrorDomain Code=1 "Told not to connect after fetching server bag: (null) - closing stream" Read bottom-up: Secure Enclave key generation fails, so MobileActivation cannot create the reference key, so apsd cannot obtain its BAA device-identity certificate, so APNs tells it not to connect. kid=0000000000000000 means there is no key id at all. Then every courier line reports Connected on 0 interfaces, and mdmclient sets its PushWakeTopics only to get Connection Invalid for service com.apple.apsd and tear down. The command to regenerate it: log show --predicate 'process == "apsd"' --last 60m --info | grep -iE 'BAA|unable to generate key|server bag'. New control, collected just now mac26 happened to be running, so I got the comparison. macOS 26.6 (25G72) guest, same host, same network, 3 days uptime: BAA_FAILURES: 0 SEPKEY_FAILURES: 0 APNS_SOCKETS: 192.168.64.8.52286 -> 17.57.146.7.443 ESTABLISHED 192.168.64.8.52285 -> 17.253.77.203.443 ESTABLISHED (+ 3 more into 17.0.0.0/8) No BAA or courier complaints at all over 6 hours, and live connections into Apple's network. So a virtualised guest per se is fine; the 27 guest specifically cannot mint the key. The physical host, also on macOS 27.0, likewise logged zero of both failures over 3 hours.