Overview

Hi everyone, I’m getting this error in App Store Connect when submitting a build in TestFlight: “There was an error processing your request. Please try again later.” Case information: Case ID: 102871415765 Contacted Apple Developer Support: April 17, 2026 (GMT+7) It has been 3–4 days with no response so far Where it happens: App Store Connect During the “What to Test” step The build is already processed and available What I tried: Retried several times Switched browsers Used Incognito mode Logged out and back in Simplified the “What to Test” text Checked that the build is not expired This issue has been blocking submission for several days now. Has anyone experienced this recently? Is there any workaround, or should I upload a new build? Thank you.

Hi everyone, We are currently facing an issue in our App Store Connect account where all of our production apps are suddenly showing the status “Removed from Sale.” This happened unexpectedly, and: We did NOT make any manual changes to app availability No recent app rejections or guideline violations were received Agreements, Tax & Banking section shows no pending actions TestFlight builds are still working fine We also have not received any clear communication from Apple explaining the reason for this. This is affecting all our live apps and impacting business operations. Has anyone else faced a similar issue recently? Could this be related to account-level restrictions or any recent policy updates? Any guidance or suggestions would be greatly appreciated. Thanks in advance!

Hi everyone, I subscribed to the Apple Developer Program on April 12th, 2026. The payment has already been charged to my bank account, but my account still shows the status “Pending” I think the reason my account is still stuck is because I enrolled in the Apple Developer Program using one Apple ID and completed the payment using a different Apple ID (the subscription is currently active under this account) It’s now been several days, and I haven’t received any confirmation email or any request for additional information. I already contacted Apple Support by email, but I’d like to know if other developers have experienced the same situation and how long it took before their account was activated. Thanks in advance for your help and feedback!

My apps are stucked in „Waiting for revlew” for 6-7 days. What is going on? It’s not only my problem, a lot of users have the same problem, there are many forums with that issue. It’s pretty unbelievable for me, that in 2026 we have to wait about week to approve or reject an app. Ridiculous. Take the example of Google Play…. Regards.

I am unable to update my apps because of Apple Developer License Agreement. I am told that I have to agree, yet I have agreed to every agreement available. When I log in my Developer Account there is no pending agreement either for free apps or Paid apps. The most recent one I agreed on April 6, 2026. I have logged out and in again multiple times. I tried to change the Account Holder to see if I get to agree on the agreement again but that did not help either. I have remained stuck and can't update any one of my apps since I get the error: "The Apple Developer Program License Agreement has been updated and needs to be reviewed. For more information, go to your account on the Apple Developer website." I have tried to reach out to Apple Support but no help was given. Can anyone please help? Much appreciated.

Starting somewhere around macOS 26.3, my sandboxed file manager spontaneously loses access to ~/Library/Mobile Documents mid-session. Setup: at launch, the user grants access to '/', '/Users', or '~' via NSOpenPanel; I store a security-scoped bookmark and call startAccessingSecurityScopedResource(). This works fine - including iCloud Drive - until some point mid-session. When it breaks, two things happen simultaneously: Enumeration fails: NSCocoaErrorDomain Code=257 (NSFileReadNoPermissionError)< NSPOSIXErrorDomain Code=1 (EPERM) Console shows the kernel refusing extension issuance: couldn't issue sandbox extension com.apple.app-sandbox.read for '/Users//Library/Mobile Documents': Operation not permitted And probing NSFileProviderManager confirms the process has been rejected system-wide: NSFileProviderManager.getDomainsWithCompletionHandler > NSFileProviderErrorDomain Code=-2001 "The application cannot be used right now." (underlying Code=-2014) What makes this specific to FP-backed paths: regular paths under the same '/' bookmark (~/Library/Application Support, etc.) stay accessible and recover normally with a fresh startAccessingSecurityScopedResource() call. Only ~/Library/Mobile Documents and its subtree fail - the entire tree, including the parent directory itself. Relaunch always restores access. What I've tried and ruled out: Re-resolving the bookmark + startAccessingSecurityScopedResource() - returns stale=false, granted=true but access is not restored; the kernel still refuses extension issuance for FP-traversing paths. NSFileCoordinator coordinated read - doesn't help; the coordinator depends on the same sandbox extension the kernel is refusing. Instantiating NSFileProviderManager(for: domain) per domain - fails with -2001 for every domain, confirming the rejection is process-wide, not path- or domain-specific. My working theory: when a FileProvider daemon (bird/cloudd/fileproviderd) restarts mid-session, the process's FP-client XPC registration is invalidated, and the kernel subsequently refuses to issue sandbox extensions for any path served by FP - even with a valid bookmark. The process seems to have no API path to re-register its FP-client identity without relaunching. Current workaround: I detect the -2001 response and prompt the user to relaunch, then do a programmatic self-relaunch if they confirm (which is obviously horribly intrusive). Questions: Is there an API that lets a sandboxed consumer app reconnect its FP-client identity mid-session, short of relaunching? Is there an entitlement or capability that would make the kernel's extension issuance resilient to FP daemon restarts? Has anyone else hit this on 26.x and found a workaround? Filed as FB22547671.

Good morning. I have an APPLE DEVELOPER ACCOUNT. I am inquiring about Distributing In House Apps using my own website. All the links so far do not help. They all seem to be relevant to the Apple Store and not In House apps. I have my apps ready for evaluation. I understand you need to evaluate them. I want to apply for a certificate that will allow me to put the apps on my OWN website and have users download these and install to their Apple devices. So far I have been testing using own devices but every build I create does NOT create a manifest file. They do work but obviously I need a manifest for the website. I assume a relevant certificate would provide that. Can you please let me know of any and all information that applies on how to apply for an In House Distribution Certificate and how and where I should upload my apps for evaluation. Thank you so much. John

Hi everyone, We are currently facing an issue in our App Store Connect account where all of our production apps are suddenly showing the status “Removed from Sale.” This happened unexpectedly, and: We did NOT make any manual changes to app availability No recent app rejections or guideline violations were received Agreements, Tax & Banking section shows no pending actions TestFlight builds are still working fine We also have not received any clear communication from Apple explaining the reason for this. This is affecting all our live apps and impacting business operations. Has anyone else faced a similar issue recently? Could this be related to account-level restrictions or any recent policy updates? Any guidance or suggestions would be greatly appreciated. Thanks in advance!

Hello, I have a problem where my macOS (Sequoia) Spritekit game spikes delta during the first press of an arrow key. I've test this with a small program, code below: // // GameScene.swift import SpriteKit import GameplayKit class GameScene: SKScene { var lastTime: TimeInterval = 0 override func keyDown(with event: NSEvent) { print("---------------> delta keyDown: \(event.characters!) keyCode: \(event.keyCode)") } override func update(_ currentTime: TimeInterval) { // Called before each frame is rendered print("update begins") let dt: CGFloat if lastTime > 0 { dt = (CGFloat(currentTime - lastTime)) } else { dt = 1.0 / 60.0 } if dt > (1/30) { print("************************************ delta spike ", dt) } lastTime = currentTime print("dt: ", dt) print("update ends") } } Example output: update begins ************************************ delta spike 0.03381687504588626 dt: 0.03381687504588626 update ends update begins dt: 0.016670208307914436 update ends As you can see, when I press left arrow key in this case I get a big delta spike. There's no spike with further presses of the arrow key. Other keys, such as the common W A S D controls for games, do not cause this delta spike.

I’m looking for guidance on a notarization submission that has been stuck in In Progress for over 24 hours. Details: Team ID: 94B7AVM73F Certificate: Developer ID Application: Bilal Ahmed Qureshi (94B7AVM73F) Tool: xcrun notarytool File: FlashcardGeneratorTrial-AppleSilicon.dmg Submission ID: 7817f9d0-32da-452f-9e2d-fff43478ccf6 Submission created: 2026-04-17T22:10:01.402Z Current status: xcrun notarytool info still reports In Progress This has now been ongoing for more than 24 hours The submission uploaded successfully and received a valid submission ID The Developer ID certificate is valid and correctly paired with the private key in Keychain security find-identity -v -p codesigning returns 1 valid identity Environment: First-time notarization on this developer account macOS direct distribution outside the Mac App Store DMG signed with Developer ID Application certificate Hardened runtime and timestamp enabled during signing I’ve seen some other recent reports of long notarization delays, especially for first-time submissions, so I’m trying to understand whether this is expected queueing / in-depth analysis, or whether there may be an issue with this specific submission. Questions: Is this normal for a first notarization on a new Developer ID account? Is there anything I should do besides wait? Can Apple check whether this submission is stuck in the queue? Thanks.

I'm experiencing a persistent issue where my app uploads successfully to TestFlight and appears in App Store Connect, but internal testers (including myself) receive the following error when attempting to install: "Could not install xxxxxxxxx. The requested app is not available or doesn't exist." What works: The build archives and exports successfully via Xcode (local build, Release configuration) The IPA uploads to App Store Connect without errors via eas submit The build appears in TestFlight and passes processing I can add the build to my Internal Testing group Testers receive the TestFlight notification and can see the app What fails: When any tester taps "Install" or "Update," the download begins briefly, then fails with the "not available or doesn't exist" error This affects all internal testers on the account, not just one device Troubleshooting already completed: Verified code signing is correct: Release configuration uses CODE_SIGN_STYLE = Manual, CODE_SIGN_IDENTITY = "iPhone Distribution", with a valid App Store distribution provisioning profile (UUID: 39bc4c63-bc64-403a-a2a6-6737b3d33115) 2. Distribution certificate is valid: Serial 4838CD7571DE5361B98A5FB2F769F74D, not expired (expires 2027-04-16) 3. Regenerated provisioning profile via EAS credentials, removed stale profiles, and rebuilt — same result 4. Incremented build numbers correctly across multiple submissions (3004 → 3005 → 3006) 5. Previously resolved a signing misconfiguration (build 3005 was incorrectly signed with "Apple Development" instead of "iPhone Distribution" due to expo prebuild reverting settings) — this was corrected for build 3006, but the install error persists 6. Confirmed the build is not stuck in processing — it shows as ready for testing in App Store Connect 7. Tested on multiple devices running current iOS versions 8. Cleared TestFlight app cache and reinstalled TestFlight on test devices Why I believe this is a server-side issue: Multiple developers in the Apple Developer Forums have reported the identical symptom — valid builds that upload and process correctly but fail to install with this exact error message. In those cases, Apple Support resolved the issue on their end within 48 hours with no action required from the developer. The signing, provisioning, and build configuration were not the cause. This one is very specific to what I am dealing with https://developer.apple.com/forums/thread/778597 One developer stated you fixed it on your side, without any real reasoning which also leads me to believe this is not something I can fix on my end https://developer.apple.com/forums/thread/778597?answerId=884241022#884241022 I've exhausted all client-side troubleshooting and believe this may require intervention on Apple's side. Has anyone been able to fix this on their end and not only when App Development called? I went through tons of the feedback and tried it all and it doesn't seem to be fixed. It's been a month or so like this. I can't get any info on who to call. I sent in a report to feedback assistant and through app developer support

Hello, I'm submitting my first macOS app for notarization from a new Developer ID team. All three submissions have been stuck at "In Progress" for several hours now. notarytool log returns "Submission log is not yet available" for all of them. Submission IDs: 39856e43-46ee-45ed-b1c7-771fb6603258 (submitted 2026-04-18T10:00 UTC) 3edf2f4f-cbaf-4e14-ba3b-c1b4e111827e (submitted 2026-04-18T10:03 UTC) 858c52e7-3386-41a8-8fee-a31c49980319 (submitted 2026-04-18T10:25 UTC) Details: This is the first notarization attempt for this Developer ID team App is signed with Developer ID Application certificate, hardened runtime enabled codesign --verify --deep --strict passes All nested code (including Sparkle framework helpers) is properly signed Only public system frameworks are linked (IOKit, AppKit, Foundation, etc.) Entitlements: app-sandbox + Sparkle mach-lookup exceptions only No private API usage Is this expected for first-time submissions, or could someone check the backend queue status for these submissions? Any guidance appreciated.

Hi, I'm trying to build an App Store IPA for my Flutter app on Mac M4 without a physical iPhone connected. STEP 1 - I tried Automatic Signing in Xcode but got: "Communication with Apple failed. Your team has no devices from which to generate a provisioning profile." "Xcode couldn't find any iOS App Development provisioning profiles matching my bundle ID." STEP 2 - I switched to Manual Signing in Xcode. No warnings or errors shown in Xcode UI. Everything looks fine in Signing & Capabilities. But when I run this command in terminal: flutter build ipa I get this error: Building App Store IPA... Encountered error while creating the IPA: error: exportArchive "Runner.app" requires a provisioning profile. My Setup: Mac M4 Flutter (flutter build ipa) Paid Apple Developer account No physical iPhone connected Building for App Store distribution Question: How do I successfully export an IPA for App Store distribution without a physical device on Mac M4? Any help appreciated. Thank you.

My app is waiting for review for more than 48 hrs since Wednesday at 5:57 PM. It has been rejected, and errors were fixed with an updated new build. Is this normal?

Hello, My app "Tall - App de rencontre" (App ID: 6761081326) has been rejected 4 times under Guideline 4.3(b) Design Spam. The App Review Board also upheld the rejection (Appeal Ticket APL411770). I fully understand the dating category is saturated. However, my app has unique mechanical features that do not exist on any other dating app on the App Store: MANDATORY HEIGHT GATE: During registration, women below 1.75m and men below 1.80m are blocked and CANNOT complete registration. This is hard-coded into the onboarding. It is not an optional filter. Users who do not meet the height criteria simply cannot use the app. DOOR-FRAME HEIGHT VERIFICATION: Users must submit a full-body photo standing barefoot under a standard door frame to verify their height. Unverified users see all other profiles blurred. This trust-and-safety mechanism is entirely unique. "THE BAKERY": A curated, time-limited daily drop of compatible profiles replacing infinite swipe. This is an anti-swipe paradigm designed to prioritize quality over quantity. I also have an existing community of over 1,000 people across multiple WhatsApp groups TALL FRANCE, 10K Instagram followers, and 44K TikTok followers — all specifically for tall people looking to connect. This proves real demand for this niche. I also noticed that the app "Score Dating" is currently live on the App Store in the Lifestyle category. Score blocks users who do not have a credit score of 675 or above. My app uses the same concept — a mandatory gate based on a specific criteria (height instead of credit score). If Score is accepted, I believe Tall should be evaluated with the same standard. I have responded to every rejection with detailed explanations and visual evidence, but received the same copy-paste response each time. I have a Meet with Apple consultation scheduled to discuss this further. Has anyone successfully overcome a 4.3(b) rejection for a niche app with genuinely unique features? Any guidance from Apple or the community would be greatly appreciated. Thank you, Frankie Babet

I am porting a macOS app to SwiftUI Catalyst and have run into a usability issue. On macOS, presented sheets are user resizable. On SwiftUI macOS, they are also resizable, but on Catalyst, they are not. Does anyone have a good reference on how to make a sheet resizable under SwiftUI Catalyst?

Title: iOS Local Network Discovery (UDP Multicast / SSDP) Not Working – Works on Android Hi everyone, I’m facing an issue with local network device discovery on iOS. The same implementation works perfectly on Android, but fails (or behaves inconsistently) on iOS. What I’m trying to do I am building a React Native app that discovers Wi-Fi audio devices (Arylic / Linkplay-based speakers) on the same local network. The discovery flow: Send SSDP (UDP multicast) M-SEARCH request to 239.255.255.250:1900 Listen for device responses Fetch device description via HTTP (LOCATION header) Parse and store discovered devices What works ✅ Android: Device discovery works reliably (multiple devices detected) ❌ iOS: No devices are discovered (or discovery is very inconsistent) iOS Configuration I have already added the required permissions in Info.plist: NSLocalNetworkUsageDescription NSBonjourServices (including _http._tcp, _airplay._tcp, _spotify-connect._tcp, etc.) NSAppTransportSecurity with local network exceptions The app correctly prompts for Local Network permission, and permission is granted. Implementation Details Using UDP sockets (react-native-udp) Joining multicast group: 239.255.255.250 Sending SSDP M-SEARCH requests every few seconds Listening for responses via socket on('message') Observed Behavior on iOS UDP socket initializes successfully No errors thrown No SSDP responses received devices array remains empty HTTP-based direct calls to known device IPs work fine Additional Notes The same network, same devices, same code works on Android iOS device is on the same Wi-Fi network Tried both real device and simulator (expected simulator limitations) Questions Is UDP multicast (SSDP) restricted or unreliable on iOS for third-party apps? Are there additional entitlements required to receive multicast responses? Is there any official Apple-recommended approach for discovering LAN devices (other than Bonjour)? Is this a known limitation of iOS networking stack? As a fallback, I’m considering scanning the local subnet via HTTP requests, but that’s less efficient compared to SSDP. Any guidance or clarification from Apple engineers or others who have faced similar issues would be greatly appreciated. Thanks in advance.

We are seeing a CloudKit private database failure for this specific container: iCloud.com.matrixqlc.photodiet.sync Failure pattern: accountStatus succeeds in some cases ensure/create custom zone succeeds but record/database-level operations consistently fail with: CKErrorDomain code = 15 CKInternalErrorDomain code = 2000 HTTP 500 Failing operations include: allRecordZones() databaseChanges(since:nil) allSubscriptions() fetch record zone metadata save record fetch record query records What makes this unusual is that the issue follows the container, not the app. On the same physical device, same Apple ID, same developer team: PhotoDiet + iCloud.com.matrixqlc.photodiet.sync => fails RepaymentCalculator + iCloud.com.matrixqlc.photodiet.sync => fails PhotoDiet + iCloud.com.matrixqlc.repaymentcalculator.sync2 => succeeds RepaymentCalculator + iCloud.com.matrixqlc.repaymentcalculator.sync2 => succeeds So this does not currently look like: app-specific entitlement/provisioning issues device/account issues CloudKit API misuse in one app record schema or app business logic issues It currently looks like the container iCloud.com.matrixqlc.photodiet.sync itself may be in a bad backend state. Sample request identifiers: RequestUUID: C8403047-0037-4D36-A7A7-CF3C83584A42 RequestUUID: 04437D9D-115E-45F5-87B5-A8CD146AE705 RequestUUID: C924B620-BAEE-403D-B944-151ADCF3419F RequestUUID: A54E79E1-6037-4533-BA09-18FBC436851C RequestUUID: 3EFD8913-3781-47CF-A48C-B651BF38EA50 RequestUUID: 2677A991-40B3-42AB-9CE5-3C4F1288EE08 Feedback Assistant ID: FB22539748 Has anyone seen a container-specific CloudKit private database failure like this, where multiple apps under the same team can access one container normally but consistently fail on another container with CKError 15 / HTTP 500?

I’m trying to find out whether anyone has seen this kind of App Store Connect issue remain unresolved for this long. This is for a first auto-renewable subscription. Timeline: Original support case opened: Feb 27, 2026 Support initially repeated the normal guidance that the first subscription must be submitted with the app version I explained that the issue was not the process itself, but a stuck review state On Mar 25, 2026, I was told the case had been escalated to the appropriate internal team Since then, I have sent follow-up emails asking for status / owner / ETA As of Apr 12, 2026 (KST), there has still been no meaningful update Current state in App Store Connect: App version 1.0.10 is still “Prepare for Submission” Previous 1.0.10 submissions show as “Deleted” There is no active app review submission for 1.0.10 The subscription previously showed “Waiting for Review” Now the subscription itself shows “In Review” But its localization still shows “Waiting for Review” So the state looks inconsistent: no active app review submission app version still draft subscription partially moved into review anyway At this point I’m not asking about the normal first-subscription submission flow. I already understand that. What I’m trying to understand is: Has anyone seen a case like this stay stuck for 6+ weeks? Has anyone had Apple say it was escalated internally and then go silent for weeks? Did Apple eventually fix it manually? Is this something that can remain stuck indefinitely unless the internal team intervenes? Any comparable experience would be helpful. Apple Support keeps saying that the internal team will follow up with me directly if they need anything. Is there anything I can do, or is all I can do just wait? Here are the relevant screenshots. App Review history: no active review for version 1.0.10, previous submissions are deleted Subscription page: the subscription itself is now “In Review” Localization on the same subscription page still shows “Waiting for Review” App version page: 1.0.10 is still “Prepare for Submission” There’s no subscription check.

I enrolled in the Apple Developer Program on April 15th and the $99 payment was successfully charged to my card (confirmed completed in my bank, not pending). However, 3 days later my account at developer.apple.com/account still shows the "Purchase your membership" banner asking me to pay again. Apple's own page says "Your purchase may take up to 48 hours to process" but it has been well past that. When I try to access Certificates, Identifiers & Profiles, I get this error: "Unable to find a team with the given Team ID S3v98Z34Dh to which you belong. Please contact Apple Developer Program Support." I already submitted a support case via the "Send us a message" form under Membership and Account > Program Purchase and Renewal, but haven't received any response yet. Has anyone experienced this? Is there another way to escalate this or get it resolved faster? I need the account for Sign in with Apple integration and I'm blocked on this. Thanks for any help.