“We are unable to process your request”

I represent a business who is trying to enroll into the Apple Developer Program. We already have a business account with Apple. Through our business account I have signed up for and provided all of the requested documentation for the Apple Developer Program. I am not the owner of the business, but I am qualified to take these actions on behalf of the business. The enrollment is pending verification since Friday. Just curious if there is anything I can do to move this along? Thank you.

I’m working toward an official release of our application. The app is designed to interface with peripheral devices, which means users need both the mobile app and the peripheral devices to log in and use it. Because of that, how would the review process work when I get to that point?

Hello everyone, I recently submitted my iOS app for review, but it was unfortunately rejected under Guideline 2.1(a) - Performance - App Completeness. For context, my app is a healthcare application built with Ionic. According to the App Review team's message, they found the app to be incomplete. They stated they were unable to review the app because they couldn't get past the login screen. The Root Cause: Upon investigating, we discovered the issue is related to IP Geo-blocking. Because the app handles sensitive healthcare data, our API provider strictly blocks all network traffic originating from outside of Italy to legally comply with European GDPR regulations. Since the App Review team tests from the US, their requests are being entirely blocked by the firewall, causing the login to fail and the app to look broken on their end. What I have verified so far: I have provided valid demo account credentials in the App Store Connect App Review Information section. I have tested the app thoroug

Hello, I'm unable to kick off builds in Xcode Cloud today due to an error connecting to our SCM repo. Repository Issue Xcode Cloud is unable to connect to the repository “”. Reconnect the repository to resume builds. I can see that this is due to an HTTP 500 error on the /scm-repositories endpoint, which would normally indicate an issue in Xcode Cloud. If on the contrary this indicates an issue on my side, I'd like to hear details and what the resolution might be. Filed an issue here: FB22314855 (Xcode Cloud: HTTP 500 when connecting to SCM provider)

I'm building a hybrid iOS app using Capacitor with a native Swift IAP bridge (StoreKit 1). My SKProductsRequest consistently returns 0 products, and all product identifiers appear in response.invalidProductIdentifiers. Setup: Capacitor app with custom CAPBridgeViewController subclass handling IAP via SKPaymentQueue and WKScriptMessageHandler 5 products configured in App Store Connect (3 consumables, 2 auto-renewable subscriptions), all Ready to Submit Bundle ID matches between Xcode and App Store Connect In-App Purchase capability enabled Paid Apps agreement active Testing on physical iPad Air M3 with Sandbox Tester Products created over 48 hours ago Clean Build Folder performed before each test Product IDs: com.opencompass.basic.monthly com.opencompass.premium.monthly com.opencompass.tokens.50 com.opencompass.tokens.150 com.opencompass.tokens.500 Code snippet: let request = SKProductsRequest(productIdentifiers: Set(productIdentifiers)) request.delegate = self request.start() // Delegate fires, but:

Hi Apple Developer Support, We are reaching out to request guidance on a testing constraint we have encountered related to iOS Universal Links and Associated Domains entitlements. As part of aligning with updated recommendations from our authentication provider, we have transitioned our mobile apps to use HTTPS redirect callbacks (Universal Links) instead of custom URI schemes. This works as expected in production and on real physical devices. However, we are encountering a significant issue in our cloud-based device testing environment. When our testing platform re-signs the app to run it on their infrastructure, the re-signing process strips the Associated Domains entitlement from the app bundle. As a result, iOS no longer honors our Universal Links, which breaks the authentication redirect flow — the callback cannot route back into the app after the user authenticates. We have identified a potential workaround that would involve disabling app re-signing in the testing platform, but this r

I am implementing an Unwanted Communication Reporting Extension (IdentityLookupUI) to allow users to report spam messages to our backend. The extension works perfectly in terms of data collection and network reporting (using ILClassificationExtensionNetworkReportDestination). However, I’ve encountered an issue with the message lifecycle: whenever the user taps Done and I return a response, the system automatically moves the reported message to the Recently Deleted folder. I want to report the data but keep the message in its current folder (especially when the user classifies it as Safe). I have tried varying the ILClassificationAction, but it seems the system ignores the action in favor of cleaning up the thread. Example of my current implementation: override func classificationResponse(for request: ILClassificationRequest) -> ILClassificationResponse { // Even when returning .none or .reportNotJunk let action: ILClassificationAction = (self.type == spam) ? .reportJunk : .none let response = ILCl

I created two sample apps — one sandboxed and one non‑sandboxed. I tested reading Managed Preferences using bash commands, CFPreferencesCopyValue for a domain, and defaults read. Everything works correctly only when the sandbox is disabled in the entitlements. When the sandbox is enabled, I’m unable to read values from /Library/Managed Preferences/. Is there any supported way for a sandboxed macOS app to read an MDM-delivered preference plist under /Library/Managed Preferences/? Any guidance on the correct and Apple‑supported method would be appreciated.

Summary Since macOS 26, our Core ML / MPS inference pipeline produces incorrect results on Mac mini M1 (Macmini9,1, A14-class SoC). The same model and code runs correctly on M2 and newer (A15-class and up). The regression appears to be in the Scaled Dot-Product Attention (SDPA) kernel path in the MPS backend. Environment Affected Mac mini M1 — Macmini9,1 (A14-class) Not affected M2 and newer (A15-class and up) Last known good macOS Sequoia First broken macOS 26 (Tahoe) ? Confirmed broken on macOS 26.3.1 Framework Core ML + MPS backend Language C++ (via CoreML C++ API) Description We ship an audio processing application (VoiceAssist by NoiseWorks) that runs a deep learning model (based on Demucs architecture) via Core ML with the MPS compute unit. On macOS Sequoia this works correctly on all Apple Silicon Macs including M1. After updating to macOS 26 (Tahoe), inference on M1 Macs fails — either producing garbage output or crashing. The same binary, same .mlpackage, same inputs work correctly on M2+. O

I have a question regarding Platform SSO and the use of Secure Enclave–backed keys with biometric policies. If we configure userSecureEnclaveKeyBiometricPolicy with userSecureEnclaveKey, my understanding is that the Secure Enclave key is protected by biometric authentication (e.g., Face ID / Touch ID). In this setup, during a login request that also refreshes the id_token and refresh_token, the assertion is signed using the userSecureEnclaveKey. My question is: Will this signing operation trigger a biometric prompt every time the assertion is generated (i.e., during login/token refresh) ?