Overview

We're working on an iOS app distributed through the App Store and installed on an MDM-enrolled device. Our MDM server uses InstallApplication to take management of the already-installed and running app. On iOS 27 betas 3 and 4, processing this command causes iOS to terminate the app and its extensions with SIGKILL. The same flow and MDM payload work without terminating the app on earlier iOS versions (iOS <=26). Environment OS: iOS 27 betas 3 and 4 Does not happen: iOS 26 or iOS 16.7.15 Device: iPhone SE 2nd Gen Enrollment: MDM-enrolled device Distribution: App Store app App state: Already installed and running when management is requested MDM command: InstallApplication Minimal MDM command The MDM server sends an InstallApplication command for the already-installed app: Attributes = { Removable = false; }; ChangeManagementState = Managed; Identifier = "APP_BUNDLE_ID"; InstallAsManaged = true; ManagementFlags = 1; RequestType = InstallApplication; We also tested the equivalent command using iTunesStoreID = APP_STORE_ID instead of Identifier, and removing InstallAsManaged. The targeted running app was terminated in the same way. Steps to reproduce Install and launch the App Store app as an unmanaged app. Enroll the iPhone in MDM. While the app is running, send the MDM InstallApplication command to take management of the existing installation. Observe the unified logs for mdmd, appstored, manageddeviced, installcoordinationd, and runningboardd. The issue can also be reproduced by initiating the same server-side flow while the app is already in the background. iOS 27 log sequence The command is accepted and appstored starts the managed-app tasks. manageddeviced then attempts to mark the app as managed using a null persona (this differs from iOS <26): The running app has a valid persona. After the failed mapping, installcoordinationd explicitly asks RunningBoard to terminate the app to disassociate that persona: After termination, removing the valid persona also fails. The managed-app task later reports success despite the mapping failures and termination. Earlier iOS comparison As an example, on iOS 16.7.15, using the same MDM command, **iOS routes the request through dmd with persona: default. The app remains alive and receives managed-app change notifications. Expected The existing installation becomes managed without terminating the running app, consistent with the behavior on earlier iOS versions. Actual manageddeviced tries to associate the app with persona (null) and fails with MIInstallerErrorDomain Code 191. That failure causes installcoordinationd to request termination of the app and its extensions to disassociate their valid persona. runningboardd terminates them with SIGKILL (isUserKill=0). The subsequent removal of the only valid persona fails with Code 242, although the managed-app task later reports success. Documentation checked The payload follows the documented InstallApplication flow for taking management of an existing app: Apple Docs WWDC26 app MDM updates We have not found a malformed field that explains the iOS 27-only failure. More info Detailed logs and additional info can be found on the Feedback report.

Hello everyone, Our iOS app WSH-P (Apple ID: 6503934660) has been in "Waiting for Review" for more than 7 days. This is an app update submission, and we have not received any review feedback or requests for additional information. The status has remained unchanged since submission. Has anyone experienced similar delays recently? Is there anything we should do, or is this just due to a review backlog? Any advice would be greatly appreciated. Thank you.

Hello, For tracking purpose, is there a way to know when a widget is installed/uninstalled? Also, would it be possible to check which size widget was installed?

Hi everyone, I'm facing an issue with WidgetCenter.shared.getCurrentConfigurations() and I'm trying to determine whether this is expected behavior or a WidgetKit bug. Environment WidgetKit with IntentConfiguration One widget kind: PhotoBoxWidgetGroup Supported families: .systemSmall .systemMedium .systemLarge Steps to reproduce Fresh install the app. Add the PhotoBoxWidgetGroup widget to the Home Screen. Resize the widget between Small, Medium, and Large (or create different sizes during testing). Delete all instances of the widget from the Home Screen. Call: WidgetCenter.shared.getCurrentConfigurations { result in ... } Expected Result Since there are no widgets on the Home Screen, I expect: Widget count: 0 Actual Result getCurrentConfigurations() still returns three configurations: Widget count: 3 Kind: PhotoBoxWidget Family: systemLarge configuration: nil widgetConfigurationIntent: nil Kind: PhotoBoxWidget Family: systemMedium configuration: nil widgetConfigurationIntent: nil Kind: PhotoBoxWidget Family: systemSmall configuration: nil widgetConfigurationIntent: nil Although there are no widgets on the Home Screen, WidgetKit continues to report one configuration for each supported family. Additional observations This does not happen immediately after a fresh install. The issue appears only after the widget has been resized. If I restart the device, getCurrentConfigurations() correctly returns 0. After adding the widget again, resizing it, and deleting it, the issue reappears. I have also tried: reinstalling the app adding confirmation delays before querying querying only when the app becomes active filtering by kind comparing snapshots The result is always the same. Question Has anyone experienced WidgetCenter.shared.getCurrentConfigurations() returning stale widget configurations after widgets have been resized and removed? Is this a known WidgetKit issue, or is there an additional step required to ensure deleted widget configurations are removed from getCurrentConfigurations()? Any guidance or confirmation would be greatly appreciated.

Hello Apple Developer Community and App Review Team, I received a Pending Termination Notice on May 29, 2026, for my account (Developer: Bushra Malik) related to Section 3.2(f), regarding app submissions for Dress Up Fashion: Styling Game. I submitted a formal appeal 10 days ago but have not yet received a response or case number confirmation. I want to provide brief context: Our original Clothing Store Simulator received repeated rejections. Rather than continuing to resubmit the same app, we made the decision to build a completely new game from scratch — new code, new assets, new UI, and a fully revised App Store listing. Nothing from the original submission was carried forward. This was a deliberate good faith effort to achieve compliance, not an attempt to evade review. We also believe an older binary may have been reviewed rather than our latest build — a technical issue we have experienced previously on this account. Our account has 4+ years of publishing history and 25+ live games currently on the App Store. Not a single other app is in rejection or under any violation. We have never engaged in subscription scams, fake reviews, bait-and-switch tactics, or any of the fraudulent conduct described in the termination notice. I am respectfully requesting: Confirmation that my appeal is actively under review A status update or case reference number Any additional information Apple needs from our side We are fully cooperative and have all source code, assets, and submission history available immediately upon request. Thank you sincerely for your time. Bushra Malik Apple Developer Account: Bushra Malik

My Apple Developer Program membership was originally purchased through the Apple Developer app using a Russian Apple Account for Media & Purchases. Current membership details: Program: Apple Developer Program Enrollment type: Individual Membership is active until August 31, 2026 The developer account and all apps are still accessible Automatic renewal has been cancelled Payments are no longer available for the Russian App Store region I created a second Apple Account with the United States as the country/region and successfully added a valid US payment card to it. My current setup is: Apple Developer app: signed in with the original Apple Account that owns the developer membership, Team ID, and apps Media & Purchases on the iPhone: signed in with the new US Apple Account Valid US payment method: added to the US Apple Account However, I cannot renew the membership: There is no Renew or Resubscribe button in the Apple Developer app There is no Renew Membership button on the Apple Developer website The new US Apple Account cannot see or manage the existing Apple Developer subscription The original Russian Apple Account still shows the cancelled subscription, active until August 31, 2026, but cannot use the US payment card because of the region restriction Has anyone successfully solved this situation? Specifically: Is it possible to renew an existing Apple Developer membership using a different Media & Purchases Apple Account? Will the Renew or Resubscribe button appear only after the current membership expires? Can Apple Developer Support switch this membership from App Store billing to manual web renewal? Should I change the country/region of the original Russian Apple Account to the United States instead? Is there a supported way to transfer the Apple Developer subscription between Apple Accounts without transferring the apps or creating a new developer membership? I do not want to create a new developer team or transfer the apps. I only need a supported way to pay the annual fee and keep the current Team ID and applications. Any recent experience from developers who originally paid through the Russian App Store would be very helpful.

Xcode 26.6 It's showing crashes from the App Store Analytics. But no crash logs from Xcode Organizer. I have tried to sign out and log in to Xcode again. I also changed the folder /Library/Developer/Xcode/Products and View > Reload the Organizer. Nothing helps. It's still empty for all versions.

Hello, I am unable to use TestFlight for any app (existing or new), while production uploads work normally. All TestFlight actions fail with: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING There are no pending agreements in App Store Connect. This is an older account that previously used TestFlight successfully. This appears to be a missing or detached TestFlight Beta contract on Apple’s backend. Could this be manually reattached or re-provisioned? This is time-sensitive, as I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.

Hi everyone, I am trying to wake up/relaunch an app that was force-quit by the user via a BLE advertisement packet. According to TN3115 ("App Force Quit by the user" section), an app generally cannot be woken up after a user force-quit. However, Note 5 states that starting in iOS 26, an app authorized via AccessorySetupKit can indeed be relaunched. Environment iOS Version: iOS 26.5 (Note: revised to standard versioning) Xcode Version: Xcode 26.3 Implementation Details 1. Info.plist Configuration <key>NSBluetoothAlwaysUsageDescription</key> <string>We need Bluetooth to discover and connect to your accessory.</string> <key>UIBackgroundModes</key> <array> <string>bluetooth-central</string> </array> <key>NSAccessorySetupKitSupports</key> <array> <string>Bluetooth</string> </array> <key>NSAccessorySetupBluetoothServices</key> <array> <string>0000XXXX-0000-1000-8000-00805F9B34FB</string> </array> <key>NSAccessorySetupBluetoothNames</key> <array> <string>MyDeviceName</string> </array> 2. Workflow & Code Steps Initialize ASAccessorySession and call activate(). Pair/authorize the BLE peripheral using ASPickerDisplayItem. Initialize CBCentralManager with state restoration: let options: [String: Any] = [ CBCentralManagerOptionRestoreIdentifierKey: restoreIdentifier, CBCentralManagerOptionShowPowerAlertKey: true ] centralManager = CBCentralManager(delegate: self, queue: nil, options: options) Start scanning: let scanOptions = [CBCentralManagerScanOptionAllowDuplicatesKey: true] centralManager?.scanForPeripherals(withServices: serviceUUIDs, options: scanOptions) Handle state restoration: func centralManager(_ central: CBCentralManager, willRestoreState dict: [String : Any]) { if let services = dict[CBCentralManagerRestoredStateScanServicesKey] as? [CBUUID], let options = dict[CBCentralManagerRestoredStateScanOptionsKey] as? [String : Any] { central.scanForPeripherals(withServices: services, options: options) } } Receive discovery callback: func centralManager(_ central: CBCentralManager, didDiscover peripheral: CBPeripheral, advertisementData: [String : Any], rssi RSSI: NSNumber) { if peripheral.name == "MyDeviceName" { // Send a local notification } } Current Behavior Foreground: Local notification triggers as expected. Background: Local notification triggers as expected. Force Quit by User: No notification is received / App is not relaunched. Issue The app fails to relaunch when force-quit by the user, which seems to contradict the behavior described in TN3115 Note 5. Is there a specific configuration, entitlement, or additional CBCentralManager setup required to allow BLE advertisements to relaunch the app after a user force-quit via AccessorySetupKit? Any guidance would be greatly appreciated!

We are implementing In-App Provisioning functionality for our Bank but there is always 500 Internal Server Error respond by Apple server once we tried to add card to apple wallet. Our code let request = PKAddPaymentPassRequest() request.activationData = try decodeBase64(payload.activationDataText, field: "activationDataText") request.encryptedPassData = try decodeBase64(payload.encryptedDataText, field: "encryptedDataText") request.ephemeralPublicKey = try decodeBase64(payload.ephemeralPublicKeyText, field: "ephemeralPublicKeyText") return request Because of fPanId is not required so we are not pass it to Apple server and that field generated once the card already added to wallet. Please help us investigate the issue, thanks! FeedbackId 24065847 (In-App Provisioning 500 Internel Error)

Hi everyone In SwiftUI, are there any good solutions to achieve a layout similar to Android's StaggeredGridLayoutManager for displaying a large amount of data?

Hello everyone, I'm hoping someone from the Apple Developer Support team or the community can help shed some light on my situation, as I seem to be stuck in a verification loop and unable to move my organization's enrollment forward. We are enrolling as an organization (LLC). I received an email from Apple stating they could not verify my identity and association with the enrolling entity, and they requested several specific documents: Applicant's government-issued photo ID Applicant's employment verification Excerpt from the entrepreneurial registry for LLC I successfully submitted all of these documents in English via the secure file-upload portal (https://developer.apple.com/contact/file-upload/) exactly as requested. However, we have not received any response, status update, or further instructions since the upload. The status remains pending. Here are the details for my enrollment: Enrollment ID: 6X23Y99AX3 Country: Georgia Additionally, because we are located in Georgia, the "Call Me" phone support option is not available for our region in the contact portal, which makes it incredibly difficult to get real-time assistance or escalate the issue. I have submitted an email ticket, but given the critical nature of this developer account for our business timelines, being stuck in this silent waiting period is very concerning.

We are implementing In-App Provisioning functionality for our Bank but there is always 500 Internal Server Error respond by Apple server once we tried to add card to apple wallet. Our code let request = PKAddPaymentPassRequest() request.activationData = try decodeBase64(payload.activationDataText, field: "activationDataText") request.encryptedPassData = try decodeBase64(payload.encryptedDataText, field: "encryptedDataText") request.ephemeralPublicKey = try decodeBase64(payload.ephemeralPublicKeyText, field: "ephemeralPublicKeyText") return request Because of fPanId is not required so we are not pass it to Apple server and that field generated once the card already added to wallet. Please help us investigate the issue, thanks! FeedbackId 24065847 (In-App Provisioning 500 Internel Error)

Hello everyone, I'm looking for advice regarding my Apple Developer account. My account was suddenly terminated by Apple, even though I have never knowingly violated any Apple Developer Program policies. None of my apps had been rejected for fraud or policy violations, and I never received any prior warning or notice about suspicious activity. The only explanation I received from Apple was: "Apple has good reason to believe that you violated Section 3.2(f) due to documented indications of fraudulent conduct associated with your account." However, Apple did not explain what specific activity or evidence led to this conclusion. Has anyone experienced a similar situation? Is there any realistic chance of getting a terminated developer account reinstated after an appeal? Also, does Apple ever provide more detailed information about the reason for termination, or do they usually keep the explanation general? I would appreciate any advice or shared experiences. Thank you.

We are implementing In-App Provisioning functionality for our Bank but there is always 500 Internal Server Error respond by Apple server once we tried to add card to apple wallet. Our code let request = PKAddPaymentPassRequest() request.activationData = try decodeBase64(payload.activationDataText, field: "activationDataText") request.encryptedPassData = try decodeBase64(payload.encryptedDataText, field: "encryptedDataText") request.ephemeralPublicKey = try decodeBase64(payload.ephemeralPublicKeyText, field: "ephemeralPublicKeyText") return request Because of fPanId is not required so we are not pass it to Apple server and that field generated once the card already added to wallet. Please help us investigate the issue, thanks! FeedbackId 24065847 (In-App Provisioning 500 Internel Error)

Hello everyone, I'm hoping someone from the Apple Developer Support team or the community can help shed some light on my situation, as I seem to be stuck in a verification loop and unable to move my organization's enrollment forward. We are enrolling as an organization (LLC). I received an email from Apple stating they could not verify my identity and association with the enrolling entity, and they requested several specific documents: Applicant's government-issued photo ID Applicant's employment verification Excerpt from the entrepreneurial registry for LLC I successfully submitted all of these documents in English via the secure file-upload portal (https://developer.apple.com/contact/file-upload/) exactly as requested. However, we have not received any response, status update, or further instructions since the upload. The status remains pending. Here are the details for my enrollment: Enrollment ID: 6X23Y99AX3 Country: Georgia Additionally, because we are located in Georgia, the "Call Me" phone support option is not available for our region in the contact portal, which makes it incredibly difficult to get real-time assistance or escalate the issue. I have submitted an email ticket, but given the critical nature of this developer account for our business timelines, being stuck in this silent waiting period is very concerning.

Hi everyone, My app has been sitting in "Waiting for Review" since July 16 — 18 days now, and it has never moved to "In Review". • App name: Tepa: Remote Reader • Apple ID: 6770857002 • Submission ID: 290281f3-f98c-4bc1-a6d0-07efe16eda39 • Type: new app There's nothing on my end to act on: Resolution Center is empty, no rejection, no requests for more info. I emailed App Review support 5 days ago (case 20000120461790) and haven't heard back. I'd rather not push with expedited review requests - I know the team is swamped and I don't think my case is more urgent than anyone else's here. But we have two large trade shows in September where we planned to present the app, and what worries me isn't approval itself so much as the time after it. If the review comes back with issues, I want enough runway to fix them properly and go through another round, rather than scrambling days before the events. Thanks.

Hi everyone, I'm investigating an issue related to StoreKit 1 receipt validation and would appreciate any insight from Apple engineers or developers who have encountered this before. Environment StoreKit 1 Consumable In-App Purchase iOS 16 / iOS 17 / iOS 18 (observed on multiple versions) Receipt validation performed on our server Receipt is read from the app bundle after the transaction completes Issue Occasionally, after a purchase succeeds and the transaction reaches the SKPaymentTransactionStatePurchased state, the App Receipt exists and can be decoded successfully, but the receipt contains: { "receipt": { ... "in_app": [] } } The in_app array is completely empty. As a result, our server cannot find the purchased product in the receipt and cannot complete receipt validation. Questions I'd like to understand under what circumstances Apple may return an App Receipt where receipt.in_app is empty. Specifically: Is it expected behavior that receipt.in_app can be empty after a successful consumable purchase? Could this happen if the app reads the receipt before the receipt has been updated? Is there any possibility that calling finishTransaction: before reading the receipt could cause the purchase record not to appear in receipt.in_app? If receipt synchronization is delayed, what is Apple's recommended approach? Wait and retry? Issue an SKReceiptRefreshRequest? Or validate using another mechanism? Are there any documented scenarios where Apple intentionally returns an empty in_app array? Additional Information The transaction state is Purchased. The purchase callback is received successfully. We have confirmed that the receipt file exists. The issue occurs only occasionally and cannot be reproduced consistently. Most purchases contain the expected in_app entry. Any clarification about the expected behavior of the App Receipt or recommended best practices would be greatly appreciated. Thank you!

Hello, I’m transferring an app from my individual account to my corporate developer account. I’m the primary owner of both accounts. I’m trying to transfer the users that used Sign In with Apple and this is what I did: I generated the transfer identifier for all the users that used Sign In with Apple from the database (50.000 users → 100% success rate) I’m using the transfer identifier previously generated to create the new Apple ID and private email address of the user. (40% success rate) I successfully generated new Apple ID and private email address for 20.000 users but for the other 30.000 users I cannot generate it because I get { error: 'invalid_request’ } on the migration endpoint (/auth/usermigrationinfo), even though I'm using the same request parameters as the ones that are working. I couldn’t find any difference between users that could be migrated and the users that couldn’t. It doesn’t matter if they are old users or new users. What I found is that I can generate the new Apple ID and private email address if the user signs in with Apple for the first time after the app transfer. Then I can use the “transfer_sub” that I have stored for the user to generate the new user details. The same process worked fine for another app that I transferred. Something seems to be broken only for this app on 60% of the users that used Sign In with Apple. Please let me know if you need further information Best, Cosmin

Subject: Clarification Request – Private Relay and Silent Network Verification (SNV) Hello, Context: our app uses Silent Network Verification (SNV), the standard carrier method where the network recognizes a subscriber's connection to verify their identity without needing an SMS code. When a user has iCloud Private Relay enabled, the request path changes in a way that breaks this recognition, and the user falls back to OTP instead. We're evaluating an approach where the app would handle DNS resolution itself for this specific verification request, so the request stays on a path our network can recognize — without the user having to turn Private Relay off. Before we go further with this, we'd like clarity on two things: Would this kind of app-level DNS handling, used only for this verification step, be acceptable under the App Store Review Guidelines — or would it likely be treated as working around a user's privacy setting (for example under 2.5.1, 2.5.9, or 5.1.1)? If we added an explicit, transparent consent step in the app — telling the user we're bypassing Private Relay for this one request so they can be verified without an SMS code — would that change how this is viewed? We'd rather get this in writing from Apple than build against an assumption, and we'll need to share your response with our internal IT and compliance team, so a written reply would be genuinely helpful. Happy to provide more technical detail if useful. Thank you,