“We are unable to process your request”

Hi, mine isnt as bad as some of the other cases but it has been over 3 days since the additional information was requested for my app from apple which i have provided and it is still waiting for review. What is a realistic expectation for the time frame to have the app reviewed? Thanks

Dear Sir/Madam, Thank you for your support. I have reviewed the documentation for Local Push Connectivity (see URL below) and, following the instruction in the Important section to Request this entitlement from the Entitlement Request Page, I completed the application process for this Entitlement on March 11, 2026. [Local push connectivity] https://developer.apple.com/documentation/networkextension/local-push-connectivity?language=objc#Supporting-APNs-and-local-push-connectivity-in-one-app Subsequently, on March 13, 2026, I received the following reply from Apple: Sub : Re: Requesting Network Extension App Push Entitlement From: Local Push Review Sent: Friday, March 13, 2026 4:09 AM Hi, Thank you for your interest in the Local Push Connectivity entitlement. Your entitlement request has been approved for: Team ID: NWKYYYYYYY Technical documentation on this API is available here: -(Omission) - Best Regards, Apple Developer Relations My understanding is that upon appr

Hello, I'm getting a persistent error when submitting my TestFlight build: App: Mealog Build: 1.0 (4) Platform: iOS Steps: Go to App Store Connect → My Apps → TestFlight → Builds → select 1.0 (4) Click Submit for Review with plain-text test notes (no special chars/emojis) Error: An error occurred processing your request. Please try again later. Troubleshooting done: Simplified test notes to plain text Tried incognito/private browser + cleared cache Disabled VPN/proxy Waited >1 hour and retried multiple times Confirmed build status is Processed Goal: Submit this build to TestFlight successfully.Attachment: Error screenshot uploaded.

How do we get addPaymentPassViewController response for in app verification without calling that function ? Currently we have working in app provisioning but not in app verification. The apple docs say The process of generating the cryptographic OTP value is the same as for generating activationData for In-App Provisioning.. How is it the same when in in app provisioning we have this button that returns all necessary info and for in app verification there is no clear way of recieving same info.

I've been unable to enroll in the Apple Developer Program and am posting here after exhausting the standard support channels. The situation: When I attempt to enroll in the Apple Developer Program as an individual, I receive the error: Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. No additional explanation is provided. I have contacted Apple Developer Program Support multiple times by both phone and email. Each time, I was told there is nothing they can do. I asked for escalation and was told escalation is not possible. At no point was I given a specific reason for the rejection. One possible cause I identified on my own is that the name on my developer profile may not match my legal name. My Apple ID at appleid.apple.com shows my correct legal name, but I'm unsure whether my developer profile reflects the same. I have not been able to confirm whether this is actually the issue, because support has not told me what the prob

On iOS 26.3.1, deviceactivityd produces zero log output and never wakes a DeviceActivityMonitor extension at the scheduled time, even when the schedule is successfully registered. The extension's intervalDidStart(for:) method is never called. Steps to Reproduce: Create an app with a DeviceActivityMonitor extension subclass Add the com.apple.developer.family-controls entitlement to both the main app and extension targets Add a shared App Group entitlement to both targets In the main app, call: let center = DeviceActivityCenter() center.stopMonitoring([.myActivity]) let schedule = DeviceActivitySchedule( intervalStart: DateComponents(hour: 17, minute: 30), intervalEnd: DateComponents(hour: 17, minute: 45), repeats: true ) try center.startMonitoring(.myActivity, during: schedule) Verify registration succeeds: DeviceActivityCenter().activities.contains(.myActivity) returns true Background the app completely and wait for the intervalStart time (5:30 PM in this example) Expected Result: intervalDidStart(for:) is ca