Overview

I'm trying to change an app's Primary Language in App Store Connect from de-DE to nl-NL and hitting a state I can't resolve through any interface available to me. Environment App Store Connect (web UI) and App Store Connect API v1 Problem UI: App Information → Primary Language → nl-NL → Save fails with: "Primary Locale couldn't be saved because you must first provide all the required screenshots for each version in this language." API: PATCH /v1/apps/1669670490 with attributes.primaryLocale = "nl-NL" returns HTTP 409: ENTITY_ERROR.ATTRIBUTE.INVALID.INVALID_STATE.MISSING_SCREENSHOTS_PRIMARY_LOCALE Error detail contains an unsubstituted placeholder: "...you must first provide all the required @@LANGUAGE_VALUE@@ screenshots..." What I've verified Current live version (3.7.6) and current editable version (3.7.11) both have complete nl-NL screenshot sets for all required device sizes (6.9" iPhone, 13" iPad). No Watch app, iMessage extension, Custom Product Pages, In-App Events, or IAPs. Enumerated all 23 versions via the API (1.0 → 4.1.0). 19 of them have an nl-NL appStoreVersionLocalization (with real historical description/keywords/support URL) but zero nl-NL screenshots attached. Tried POSTing an nl-NL screenshot set to one historical version (4.1.0) directly via the API to confirm this isn't just a UI restriction. Also returns 409 ENTITY_ERROR.ATTRIBUTE.INVALID.INVALID_STATE — historical versions are locked against edits (including screenshots) at the API level, not just the UI. Question Since these historical versions can't be edited through any supported interface, is there a documented way to satisfy or bypass the "screenshots for each version" check for locked historical versions when changing Primary Locale? Filed as case 20000130035264 with Developer Support, who pointed me here for the technical side.

I am planning an app transfer between two developer teams, iOS only, no macOS app. The app shares an app group with a notification service extension and a share extension. The container holds a SQLite database, message attachments and user avatars. The database encryption key is in the keychain. I have read thread https://developer.apple.com/forums/thread/706128 (including the 2026-03-31 revision), and the plan is to follow it: a pre-transfer release moving keychain items into the AGI keychain access group, time for adoption, then the app transfer, then the app group transfer. I've also read https://developer.apple.com/forums/thread/774831, https://developer.apple.com/forums/thread/782132 and https://developer.apple.com/forums/thread/815779. My questions are about the container rather than the keychain: Step 7 of 706128 says that when a user installs the post-transfer version, "it will have access to your app group, and hence your keychain items". Does that access include the files already in the app group container, written while the app was signed by the old team? Or does the transfer restore only AGI keychain access group membership, leaving the container's prior contents inaccessible? If those files are not preserved, is there a supported way to migrate them, or should I relocate that data into the app's own container before the transfer? Thread 815779 asked this and I do not think it was answered. While the app group transfer is in progress, do already installed builds signed by the old team, which the user has not updated, keep working against the original container? App Store Connect Help (Transfer an app > Overview of app transfer > Apps using App Groups) says the app group "can be deleted from the transferor's account and registered to the recipient's account". Is that the same operation as step 5 of 706128, "transfer the app group ID", or two different things? I ask because the developer in thread 774831, who lost shared container data for roughly 25% of users, deleted and recreated the group during the transfer, whereas 706128 step 5 says to do it once the app transfer is complete.

I'm seeing two related UI issues when presenting MFMailComposeViewController from SwiftUI using .sheet. The Cancel button disappears During the sheet presentation animation, the Cancel button is visible in the navigation bar. However, once the presentation animation completes, the Cancel button disappears. This is particularly problematic when the mail composer is presented full-screen: since the Cancel button is removed, there is no longer any way for the user to cancel composing the email and dismiss MFMailComposeViewController. The navigation bar changes abruptly when the presentation animation finishes The navigation bar has one appearance while the sheet is being presented, including the Cancel button and the layout/styling of its navigation items. As soon as the presentation animation finishes, the navigation bar abruptly changes to a different appearance. This causes a noticeable flicker/jump at the end of the animation. In other words, the appearance of MFMailComposeViewController during the sheet transition does not match its final appearance after the transition completes. The sample code below reproduces the issue. Steps to reproduce: Run the sample on an iPad Pro 13-inch (M5) running iPadOS 26.5. Present MFMailComposeViewController using the provided SwiftUI .sheet. Observe the navigation bar during the presentation animation. When the animation completes, observe that the navigation bar changes abruptly and the Cancel button disappears. Is this a known issue with MFMailComposeViewController when presented from SwiftUI using .sheet? struct ContentView: View { @State private var isMailComposerPresented = false var body: some View { VStack { Button("Send") { isMailComposerPresented = true } .buttonStyle(.borderedProminent) } .sheet(isPresented: $isMailComposerPresented) { MailComposerView() } } } struct MailComposerView: UIViewControllerRepresentable { @Environment(\.dismiss) private var dismiss func makeUIViewController(context: Context) -> MFMailComposeViewController { let composer = MFMailComposeViewController() composer.mailComposeDelegate = context.coordinator return composer } func updateUIViewController(_ uiViewController: MFMailComposeViewController, context: Context) {} func makeCoordinator() -> Coordinator { Coordinator(dismiss: dismiss) } final class Coordinator: NSObject, MFMailComposeViewControllerDelegate { private let dismiss: DismissAction init(dismiss: DismissAction) { self.dismiss = dismiss } func mailComposeController( _ controller: MFMailComposeViewController, didFinishWith result: MFMailComposeResult, error: Error? ) { dismiss() } }}

I submitted an Endpoint Security entitlement request today (request ID NWFPYC286F, Team type). The request shows up in my Request History with status "Submitted," but I never received an ACK email or follow-up number. I've checked spam/junk folders and the email associated with our team account. Nothing from Apple. Two questions: Is the request actually in the review queue if I have a request ID in the portal but no email confirmation? Is there any way to check status or get a timeline estimate? This entitlement is critical for our product development. We're building agent identity infrastructure that needs ES for process-level attestation on macOS. Appreciate any help, especially from anyone who's been through this recently.

I'm hoping someone from Apple or another developer has some advice. I have an app update that has been stuck in "Waiting for Review" for 12 days. This is not a new app, it's a small update whose primary purpose is to fix a critical bug that's affecting my users. Here's what I've already tried: Submitted two expedite review requests through the official form (I rarely use this process, so it's not something I've abused). Emailed App Review support twice to explain the situation. So far, I've received no response to either the expedite requests or the emails. At this point, users are continuing to experience a bug that has already been fixed, but I have no way to get the update to them. It's hurting the user experience, causing me to lose users, and is directly impacting my revenue. Has anyone experienced something similar recently? Is there anything else I can do besides waiting? I'd really appreciate any guidance, and if anyone from Apple is reading this, I'd be grateful if someone could look into this situation.

Hi, I was trying to run a macOS VM under a launchd daemon as part of a requirement. The parent daemon spawns a macOS VM under root user. Sometimes this is fine, but sometimes I'm getting a security error from VZ library : Unable to access security information. The virtual machine encountered a security error. In system logs, I was able to see this : ctkd: unable to generate key: error e00002e2 for com.apple.Virtualization.VirtualMachine with SepKey ACL I think this indicates Virtualization.framework asked CryptoTokenKit/Secure Enclave to create a key, and the security subsystem rejected it in the current execution context. Is it possible to run VM this way ? If yes, what am I missing ?

It seems like macOS 27 beta 2 has some issues with NSStatusItem buttons added to the menu bar - this creates difficulties for some menu bar extra apps. NSStatusItem buttons does not receive mouse hover/movement events - FB23329983 On macOS 27, views inside an NSStatusItem button no longer receive hover or mouse-movement events. The same code works correctly on macOS 26. What I tried: An NSTrackingArea attached to a subview of NSStatusBarButton An NSTrackingArea attached directly to the status-bar button Replacing NSStatusItem.view with a custom view Embedding an NSHostingView and using SwiftUI onHover/onContinuousHover NSStatusItem button highlight cannot be set programmatically. - FB23330269 The following code no longer has any effect (does not provide the highlight capsule): NSStatusItem.button?.highlight(true) NSStatusItem window occlusionState no longer reflects hidden menu bar visibility - FB23349447 The following no longer works: statusItem.button?.window?.occlusionState.contains(.visible) These changes may be related to some of the touch related changes or maybe it's about how menu items are now seemingly more "managed" in a way that their position, visibility may change in a way that is transparent/undetectable to the app.

I'm debugging the following kernel panic to do with my custom filesystem KEXT: panic(cpu 0 caller 0xfffffe004cae3e24): [kalloc.type.var4.128]: element modified after free (off:96, val:0x00000000ffffffff, sz:128, ptr:0xfffffe2e7c639600) My reading of this is that somewhere in my KEXT I'm holding a reference 0xfffffe2e7c639600 to a 128 byte zone that wrote 0x00000000ffffffff at offset 96 after that particular chunk of memory had been released and zeroed out by the kernel. The panic itself is emitted when my KEXT requests the memory chunk that's been tempered with via the following set of calls. zalloc_uaf_panic() __abortlike static void zalloc_uaf_panic(zone_t z, uintptr_t elem, size_t size) { ... (panic)("[%s%s]: element modified after free " "(off:%d, val:0x%016lx, sz:%d, ptr:%p)%s", zone_heap_name(z), zone_name(z), first_offs, first_bits, esize, (void *)elem, buf); ... } zalloc_validate_element() static void zalloc_validate_element( zone_t zone, vm_offset_t elem, vm_size_t size, zalloc_flags_t flags) { ... if (memcmp_zero_ptr_aligned((void *)elem, size)) { zalloc_uaf_panic(zone, elem, size); } ... } The panic is triggered if memcmp_zero_ptr_aligned(), which is implemented in assembly, detects that an n-sized chunk of memory has been written after being free'd. /* memcmp_zero_ptr_aligned() checks string s of n bytes contains all zeros. * Address and size of the string s must be pointer-aligned. * Return 0 if true, 1 otherwise. Also return 0 if n is 0. */ extern int memcmp_zero_ptr_aligned(const void *s, size_t n); Normally, KASAN would be resorted to to aid with that. The KDK README states that KASAN kernels won't load on Apple Silicon. Attempting to follow the instructions given in the README for Intel-based machines does result in a failure for me on Apple Silicon. I stumbled on the Pishi project. But the custom boot kernel collection that gets created doesn't have any of the KEXTs that were specified to kmutil(8) via the --explicit-only flag, so it can't be instrumented in Ghidra. Which is confirmed as well by running: % kmutil inspect -B boot.kc.kasan boot kernel collection at /Users/user/boot.kc.kasan (AEB8F757-E770-8195-458D-B87CADCAB062): Extension Information: I'd appreciate any pointers on how to tackle UAFs in kernel space.

At first, the MacBook Air M2 gives an "failed to personalize" error when updating, the detailed error message shown by softwareupdate shows that something related a recovery partition is wrong. The exact error message is not available now. (To solve this issue) I tried to revive the Mac, but it failed the first time and multiple tries also failed after that. The Mac is unable to boot into macOS and the Recovery. The MacUpdater.log shows the following: [12:13:52.3728] find_filesystem_partitions: recovery os container= volume= [12:13:52.3728] entering fsck_recovery_os_filesystems [12:13:52.3728] ramrod_display_set_granular_progress_forced: 29.000000 [12:13:52.3728] fsck_recovery_os_filesystems: No dev node for 'Recovery' partition [12:13:52.3728] leaving fsck_recovery_os_filesystems, returning 26 [12:13:52.3728] [04:13:49.0882-GMT]{3>6} CHECKPOINT FAILURE:(FAILURE:26) MOUNTED:[0x1605] fsck_recovery_volume [0]D(failed to fsck recovery OS filesystems) Since there are many important data on the Mac, I cannot do a restore on it. How should I restore the data?

The set bitrate is not respected when kVTCompressionPropertyKey_AverageBitRate is used. constant and variable bitrates seems to work, only average that is broken. All three modes works in iOS 26.

Hello, My Team ID: 536YC9W689 I submitted my App Store Small Business Program application on July 7, 2026. On the same day, I received the confirmation email titled "We’ve received your request to join the App Store Small Business Program". It has now been more than 30 days since submission. The application status still remains under review, and I have not received any follow-up emails, requests for additional documentation, or approval/rejection notifications. All items in my Paid Applications Agreement are fully completed and active: Contract status: Active Tax information: Submitted and verified Banking information: Verified Could anyone from the Apple team help check the current status of my application? Please let me know if there is any missing information or further action required on my end. Thank you.

App Store Connect will not let me attach the subscription to a version submission. App stack: React Native / Expo, EAS builds Subscription: monthly auto-renewable, single tier Payment integration: RevenueCat What is working: Subscription fully configured in App Store Connect (Prepare for Submission status) All metadata complete: localization, price, availability, App Review screenshot, review notes Paywall works on device: StoreKit fetches the product live, Apple purchase confirmation flow initiates correctly Paid Applications Agreement, banking, and tax info all Active RevenueCat integration validated (Valid credentials, price fetches at runtime) What is failing: App Store Connect submission UI shows: "Unable to Submit for Review - Your first subscription group must be submitted with a new app version. New subscription groups must be submitted with an auto-renewable subscription from within that group." No option to attach a version in the draft submission flow The rejected version's Edit flow does not offer an In-App Purchases and Subscriptions section Standard documented flow does not produce a bundling option What I have tried: 4 submissions across multiple builds and versions - all rejected under 2.1(b) with "app references pro features but the associated In-App Purchase products have not been submitted for review" 3 Developer Support cases - all responses confirmed this issue is outside Developer Support scope, pointed here Removed all previous rejected submissions to reset the version to "Prepare for Submission" - no change in behavior This matches known Apple Developer Forums threads 713221, 812514, 705460 where developers in the same stuck state required App Store Connect engineering to manually push the subscription to "In Review" on the backend. If any Apple engineers are able to look into this: happy to provide App ID, submission ID, and product IDs privately via DM. Requesting assistance getting the subscription attached to the pending version submission so review can complete.

Hi all, I hope someone from App Review can take a look My situation: QuidProQuote: Memory Keeper (app ID: 6791349683) is a simple cross-platform app where a single purchase unlocks both the macOS and iOS versions. Both versions were submitted from the same build/codebase. The problem is that while my macOS version has been approved and is now pending my release, the iOS version (submission ID: 9fba8d59-d9a7-4a09-bbbe-1d23035adbe1) has been "Waiting for Review" for 12 days now. 2026-07-30, ~4:30pm ET: Both macOS and iOS submissions entered "Waiting for Review" 2026-08-06, ~10am ET: macOS version approved, now Pending Developer Release 2026-08-11 (Today): iOS version still showing "Waiting for Review," 12 days with no status change This ends up being more than a normal wait because the purchase is shared across platforms... releasing the macOS version now would put it in front of customers without the iOS half of what they're paying for. I can't release the approved macOS build until the iOS version clears review, so the delay on one platform is effectively holding both hostage. I did file an expedited review request today (2026-08-11), received confirmation ("we'll expedite this review"). But I read advice that additionally it would be wise to register the problem here. Thanks for any visibility into this!

Hi Apple DTS and community, My developer account's app has been granted the Default Mail App managed capability (com.apple.developer.mail-client). The capability works for Development and App Store Connect distribution, but it is not enabled for Ad Hoc distribution. This prevents us from using our Xcode Cloud “Archive & TestFlight” workflow: The archive succeeds. Development and App Store Connect exports succeed. Xcode Cloud then automatically attempts an Ad Hoc export. The Ad Hoc export fails, causing the entire archive action to fail and the TestFlight post-action to be skipped. The export log reports: Entitlement com.apple.developer.mail-client not found and could not be included in profile. This likely is not a valid entitlement and should be removed from your entitlements file. We have reproduced this in two consecutive Xcode Cloud runs. We also confirmed that: The App ID has the Default Mail App capability enabled. The entitlement is present and correctly spelled in the app’s entitlements file. The App ID’s provisioning support lists Development and App Store Connect, but not Ad Hoc. Our Xcode Cloud workflow does not expose an option to disable the automatically attempted Ad Hoc export. This appears to match these previous reports: https://developer.apple.com/forums/thread/774506 — a DTS engineer enabled Ad Hoc support for the entitlement, after which the developer confirmed the issue was resolved. https://developer.apple.com/forums/thread/800072 — DTS confirmed that the Ad Hoc distribution option must be enabled for the Default Mail App managed capability. We also opened an Apple Developer Support case (102945477410). Developer Support directed us to the forums and indicated that this issue would need to be handled by DTS engineers. I can provide our Team ID, Developer Support case number, Xcode Cloud run identifiers, and any other account details privately if needed. Thank you!

Hello everyone, I'm facing a frustrating issue with the new App Store Connect UI when trying to submit In-App Purchases alongside my app version. My Situation: App: Nagpur Prime Property (iOS) Rejected under Guideline 2.1(b) — App Completeness Reason: IAPs not submitted with the binary What I've Done: Uploaded new Build 7 (v1.0.1) ✅ Created 2 auto-renewable subscriptions: • Basic Plan (npp_basic_plan) — Ready for Review ✅ • Premium Plan (npp_premium_plan) — Ready for Review ✅ Added both to a Draft Submission (3 items total) ✅ Sandbox tester account added ✅ The Problem: The Draft Submission panel shows: ⚠️ "Unable to Submit for Review — To submit your items for review, add an app version for the selected platform." The "Submit for Review" button is permanently GRAYED OUT. The Draft Submission shows: Versions column: "-" (no app version linked) Items: 3 (Subscription Group + 2 subscriptions) The App Version (Build 7) is in a SEPARATE submission showing "Ready for Review" — but there is NO UI option to link the two submissions together. What I've Tried: Clicking "Add for Review" from Subscription Group page Clicking "Add for Review" from individual plan pages Clicking "Draft Submissions (1)" from version page Contacted Apple Review team — no solution provided Tried "Resubmit to App Review" on version — IAPs not included Question: In Apple's new App Store Connect UI, how do you correctly link an IAP Draft Submission to an App Version submission so they can be reviewed together? Is there a specific order of operations that needs to be followed? Or is there a known workaround for this issue? Thank you in advance!

Hi! I'd like to share an implementation of 2D soft shadows using SpriteKit and custom Metal rendering. GitHub Repo SpriteKit-SoftShadows The demo app runs on iOS and Mac Catalyst. The soft shadow implementation is based on Scott Lembcke's algorithm. Pipeline The app uses MTKView to drive the rendering loop at the desired frame rate. Each frame: SpriteKit renders the scene into a Metal texture using SKRenderer. The CPU sends each light's properties and the relevant shape edges to a Metal vertex shader. The vertex shader projects shadow geometry from each edge. A fragment shader calculates the shadow opacity at each pixel, producing a soft shadow mask for each light. A final fragment shader combines the SpriteKit texture, lights, and shadow masks to produce the displayed image. The SwiftUI controls update variables inside the SpriteKit scene through @Observable. The rendering loop consumes the new values on its next cycle. Let me know if you have any feedback!

Our initial release has been in "Waiting for Review" since July 29, 2026. As of today, August 11, it has never progressed to "In Review." App ID: 6771136749 Version: 1.0 Submitted: July 29, 2026 Support Case ID: 20000135031799 Details: Initial release, not an update Build has not been cancelled or resubmitted at any point Free Apps Agreement is active; no paid features or IAP Metadata, screenshots, and App Review Information (including demo credentials) are complete No messages in Resolution Center I filed a support case today but wanted to post here as well in case anyone from App Review can confirm whether the submission is correctly in the queue. Has anyone seen initial submissions sit this long recently without moving? Interested in whether this matches the backlog others have reported this year.

My app start up has became horrid. It takes 1 minute to open SQLlite database for my rust core. Impossible to work... I have Address Sanitizer, Thread Perf Checker and Thread Sanitizer disabled...

A build has been uploaded to TestFlight, and we have existing Internal Testing groups that have worked successfully in the past. However, when I click the blue + button under Groups, all groups are disabled and cannot be selected. The same issue occurs with a newly created group. I’m an Admin and have permission to manage testers and groups. Build Distribution is set to Automatic for Xcode Builds, as it was previously when this worked without issue. Is there a known workaround or setting that could resolve this? Thank you

In my apps, I have a requirement to display an image of the application icon is certain circumstances. This is fairly straightforward for iOS/iPadOS and it used to be straightforward for macCatalyst. For MacCatalyst, this is no longer true (at least since macOS 26). This is because the app icon is now stored as an .icns file and (in the case of using an IconComposer icon), the `'png' in the Asset Catalog now has an unknown name. So the following code no longer works: public extension Bundle { var icon: UIImage? { #if targetEnvironment(macCatalyst) guard let iconName = infoDictionary?["CFBundleIconName"] as? String else { return nil } return UIImage(named: iconName, in: self, compatibleWith: nil) #else guard let icons = infoDictionary?["CFBundleIcons"] as? [String : Any] else { return nil } guard let primaryIcon = icons["CFBundlePrimaryIcon"] as? [String : Any] else { return nil } guard let iconFiles = primaryIcon["CFBundleIconFiles"] as? [String] else { return nil } guard let file = iconFiles.last else { return nil } return UIImage(named: file, in: self, compatibleWith: nil) #endif } The obvious solution is to place an Image in the Asset Catalog which I can access, but this is a maintenance headache. What I would actually like to do is either create a UIImage directly from the .icns file, or access the .png file in the Asset Catalog (which has a name beginning with the icon file name, but has additional characters in its name that I don't know). Can you help?