Overview

Hello, I'm experiencing a persistent issue with TestFlight and app reviews on App Store Connect, and I hope someone else has encountered this before. About a week ago, when trying to add external testers to test the initial TestFlight builds, I received the following error: There was an error processing your request. Please try again later. Since there were no other details, it was impossible to know the source of the problem. After doing some research, I found the root cause of the problem in the browser console; "errors" : [ { "id" : "c7300330-93d7-4aee-af8e-1aeffeff81ae", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] Since then: I've researched everything needed for TestFlight, including contracts, bank details, and so on, but I can't create external TestFlight tests. Internal TestFlight builds appear, but they can't be downloaded ("Requested application not available or present"). My applications just won't get past the review process. I've been trying to find a solution for about 10 days now. I've checked everywhere. We even checked with AI, but there's no reason. Important details: This is an individual developer account. I am the account holder. All contracts appear active and valid. This is my first and only application. I've contacted Apple Developer Support, but unfortunately, I haven't received a real solution yet, which makes it unclear how to proceed. Suggestions include checking forums, etc. Has anyone experienced this problem or found a solution? Any information would be greatly appreciated. What should I do? Please help. Thanks!

Hello, I would like to check the status of my app, as it has been stuck in "waiting for review" for almost a month (ID: 6746933136). Thank you

On my Apple Developer Account, all I see is "Your enrollment is being processed. Your enrollment ID is JYD86Q79DM." This has been ongoing for almost a week now. This is the first time I am enrolling to the program and need to know how much time it takes and if I am missing any steps? Please advise

Hi everyone, I purchased an Apple Developer Program membership about three days ago. The payment has already been successfully charged to my bank account, but my account is still showing the status “Pending” with the message “Subscribe your membership.” I haven’t received any confirmation email or any request for additional information since completing the purchase. I’m curious if others have experienced a similar delay recently, and how long it took before your developer account was fully activated. Any insights or experiences would be greatly appreciated. Thanks in advance!

Hi everyone, We are working on an app that requires access to devices on the local network (Bonjour / LAN discovery + direct socket communication). We are currently struggling with the Local Network privacy permission flow introduced by Apple. From our understanding, there is no dedicated public API to explicitly request Local Network permission or to reliably determine the current authorization state before attempting network activity. We have tried several commonly suggested approaches to trigger the permission dialog, including: Bonjour browsing via NWBrowser Publishing/listening with NetService UDP/TCP socket attempts on local subnet NWConnection / NWListener Triggering discovery after app launch and after foreground transitions We already added the required entries in: NSLocalNetworkUsageDescription NSBonjourServices However, the behavior is inconsistent across devices and OS versions: Sometimes the popup appears immediately Sometimes it never appears Sometimes network operations silently fail without callback clarity In some cases callbacks are delayed or ambiguous Reinstalling/resetting permissions changes behavior unpredictably Our main challenges are: What is currently considered the most reliable Apple-approved method to trigger the Local Network permission prompt? Is there any officially recommended way to determine whether permission is: not determined denied granted Is there any reliable callback or state transition API developers should use? Are there known differences between: NWBrowser NetService BSD sockets NWConnection when it comes to triggering the permission dialog? Are there recommended retry/timing patterns to avoid race conditions during app launch? Is Apple planning to introduce a dedicated authorization API similar to: AVAuthorizationStatus CLAuthorizationStatus PHPhotoLibrary.authorizationStatus() Right now it feels difficult to provide a reliable UX because there is no deterministic way to: proactively request access observe authorization state recover gracefully when the prompt does not appear Any guidance, DTS references, WWDC sessions, or recommended implementation patterns would be greatly appreciated. Thanks!

It has been 6 days since we submitted our app for review, and the status is still showing “Waiting for Review,” even though the guidelines mention reviews are usually completed within 48 hours. We also contacted support but have not received any response yet. Has anyone else experienced similar delays recently? Any advice would be appreciated.

Hi, I submitted my Family Controls entitlement requests on April 15 for my iOS app, but I still haven’t received an approval, rejection, or any status update. This is blocking my ability to properly test and move forward with the app, since it depends on the Screen Time / Family Controls APIs. I've tried contact to apple developer support and filed a code-level support on app connect dashboard. and still nothing received. Here is the request information: code-level support case id: 19834379 apple developer support case id: 102878196850 Family Controls Distribution RequestId: BT4C47F5VB,SLP56WRZ3J,BZ7MF3R4FF,5HAY5UF5X2,P49SM5C859,KG2T2X2L76,N353H759C4 Thanks.

Hello, I submitted an update for my app for review on April 27th. Since then, the app has remained in the “Waiting for Review” status. I contacted support by email after one week and again after two weeks, but both of my messages were left unanswered. Please provide me with an overview of what is going on with my app submission for review. Thank you.

Hi everyone, I'm dealing with a critical issue regarding the Screen Time API and hoping someone here has experienced something similar. We recently completed an app transfer to a new developer account. Upon successful transfer, the app completely lost its previously approved "Family Controls" entitlement. We immediately submitted a new request for the entitlement on the new account, but it has now been stuck on "Pending Approval" for over 12 days. We haven't received any feedback, emails, or status changes, and Developer Support has been unresponsive so far. This is completely blocking our production updates. Has anyone successfully transferred a parental control / Screen Time app recently? Is it normal to lose the entitlement during a transfer? For those who had to reapply, how long did the approval take? Are there any effective ways to escalate this to get an actual human review? Any advice, workarounds, or shared experiences would be hugely appreciated. Thanks in advance!

Hi, I submitted my Family Controls entitlement requests on April 21 for my iOS app, but I still haven’t received an approval, rejection, or any status update. This is blocking my ability to properly test and move forward with the app, since it depends on the Screen Time / Family Controls APIs. Has anyone had a similar delay recently? Is the recommended next step to file a code-level support request with my Team ID, or should I continue waiting? Thanks.

Issue: Sandbox test account stuck in a loop when trying to access account management Environment: iOS version: [iOS 26.4.2] Device: iPhone 12 Steps to Reproduce: Created sandbox test credentials on Apple Developer site (App Store Connect → Users and Access → Sandbox → Testers) On iPhone, navigated to Settings → Developer → Sandbox Apple Account Clicked "Sign In" and entered sandbox test email and password Successfully verified using verification codes (both email and phone number) Clicked on the signed-in sandbox account A popup appears with "Manage" option Clicked "Manage" Expected Behavior:- Should open sandbox account management interface Actual Behavior:- Popup immediately closes and the same popup reappears. Clicking "Manage" again produces the same result - an endless loop preventing access to account management. Has anyone encountered this issue with sandbox test accounts? Is there a known workaround or fix for this behavior?

I'm implementing EU external purchase using ExternalPurchaseCustomLink. No IAP transactions are offered on EU storefronts — payment happens entirely on our external website. I want to call Product.products(for:) on EU storefronts solely to fetch localized product metadata (displayName, displayPrice, currency formatting) for display. Product.purchase() will never be called. Is it acceptable to use Product.products(for:) for read-only product info display on EU storefronts where only external purchase is offered?

Does anyone know if there will be a Swift 6 version of "The Swift Programming Language" book and if so, when it will be released for Apple Books?

Hi everyon. I‘d like to ask If there’s a way of including info.plist into swift playground on the iPad. I’m currently developing a daw on the iPad, I can see and use Apple’s auv3 plugins but can’t see third party apps like fab filter etc installed on the iPad. I think it’s needs inter app or auv3 entitlement. Is there a work around? I have attached my code for auv3 section. if anyone is interested , here is a video of my progress so far https://youtu.be/_2-L3oowfd0?si=cbr_9vYc3DOXV3R1 AUV3Diagnostic.swift

I understand that with the 26.4.2 patch, when you click on a notification preview to check a text message, the saved preview data is deleted. So, what should I do to delete the preview data that was left over from clicking on notification previews before the 26.4.2 patch? First of all, I don't want to do a factory reset. So I'm just want to know about this.

We are seeing trial conversions for our auto-renewable monthly subscription wingman_monthly (App ID 6758346525) land in a persistent "Pending" state in users' iOS Purchase History after the 3-day free trial ends, with no debit reaching the user's payment method. App Store Server Notifications V2 indicate the renewals succeeded — each affected transaction is delivered as DID_RENEW (subType BILLING_RECOVERY not present) with is_trial_conversion: true, period_type: NORMAL, a new expires_date set 31 days in the future, AUD 19.99 attributed, no expirationIntent, no is_in_billing_retry_period, and no cancellation_reason. So Apple's billing layer reports the renewals as successful, but settlement does not appear to complete. The same trial-to-paid flow on our yearly product wingman_yearly in the same subscription group converts and debits cleanly. The pattern is specific to wingman_monthly.

The epic saga of registering an Apple Developer Account for my company seems to have been successfully resolved. The full story can be read here My account has been approved, I've paid the membership fee, and everything appears to be in order. Huge thanks to everyone, especially the Apple staff members who didn't stay indifferent and went out of their way to help. Current status: My developer account is active. I can sign in to https://developer.apple.com/account and see that everything looks fine - there are no pending actions on my side (no agreements to sign, etc.), and the account appears completely normal. However, when I try to sign in to App Store Connect, I get the following error: To access App Store Connect, you must be an individual or team member in the Apple Developer Program, or invited by an individual to access their content in App Store Connect. (https://appstoreconnect.apple.com/login?errorKey=ITC.signin.error.invalidUser.asc) I'm attaching a screenshot. What I've already tried: Clearing browser cache, trying different browsers and devices, and waiting for some time — none of this helped. On May 9, I submitted a support request (Case ID: 20000112974233), but I still haven't received a response. My guess is that my account may have exhausted its Apple Developer Support request limit, since during the original issue I sent dozens of messages and may have used up my quota. This is just a hypothesis, but if I'm right, I would be very grateful if my ability to receive Apple Developer Support could be restored. Thank you in advance. For reference: similar case: I also did some research and found that another forum user had the same issue, which was resolved through Apple Developer Support (hopefully this helps point in the right direction): https://discussions.apple.com/thread/255265181 Thanks in advance for any help!

Hello Apple Developer Support, My app has been stuck in “Waiting for Review” since February 7, and I have submitted multiple inquiries without receiving any response. This delay has now become extremely concerning. Missing a planned launch due to an indefinite review timeline is very difficult for independent developers. If there is an issue with the submission, I would appreciate clear communication. If there are review delays, transparency would help us plan accordingly. I respect the review process, but the lack of updates after this amount of time is frustrating. I would sincerely appreciate clarification on the status. I kindly ask for a specific and personalized response regarding my case, as my previous inquiries received only general or automated replies without addressing the actual issue. Thank you.

As part of the OpenJDK testing we run several regression tests, including for Java SE networking APIs. These APIs ultimately end up calling BSD socket functions. On macos, starting macos 26, including on recent 26.2 version, we have started seeing some unexplained but consistent exception from one of these BSD socket APIs. We receive a "ENOBUFS" errno (No buffer space available) when trying to construct a socket(). These exact same tests continue to pass on many other older versions of macos (including 15.7.x). After looking into this more, we have been able to narrow this down to a very trivial C code which is as follows (also attached): #include <stdio.h> #include <sys/socket.h> #include <string.h> #include <unistd.h> #include <sys/errno.h> static int create_socket(const int attempt_number) { const int fd = socket(AF_INET6, SOCK_STREAM, 0); if (fd < 0) { fprintf(stderr, "socket creation failed on attempt %d," " due to: %s\n", attempt_number, strerror(errno)); return fd; } return fd; } int main() { const unsigned int num_times = 250000; for (unsigned int i = 1; i <= num_times; i++) { const int fd = create_socket(i); if (fd < 0) { return -1; } close(fd); } fprintf(stderr, "successfully created and closed %d sockets\n", num_times); } The code very trivially creates a socket() and close()s it. It does this repeatedly in a loop for a certain number of iterations. Compiling this as: clang sockbufspaceerr.c -o sockbufspaceerr.o and running it as: ./sockbufspaceerr.o consistently generates an error as follows on macos 26.x: socket creation failed on attempt 160995, due to: No buffer space available The iteration number on which the socket() creation fails varies, but the issue does reproduce. Running the same on older versions of macos doesn't reproduce the issue and the program terminates normally after those many iterations. Looking at the xnu source that is made available for each macos release here https://opensource.apple.com/releases/, I see that for macos 26.x there have been changes in this kernel code and there appears to be some kind of memory accountability code introduced in this code path. However, looking at the reproducer/application code in question, I believe it uses the right set of functions to both create as well as release the resources, so I can't see why this should cause the above error in macos 26.x. Does this look like some issue that needs attention in the macos kernel and should I report it through feedback assitant tool?

We have been having unexplained failures with the codesign tool recently on macosx aarch64 and x64 hosts. Every once in a while when signing an app locally using the following command: /usr/bin/codesign -s - -vvvv --force /home/me/FooBarCalculator.app results in the following error: /home/me/FooBarCalculator.app: timestamps differ by 185 seconds - check your system clock The number of seconds reported in the error message keeps varying (but usually in that range). We have checked the system clock but there isn't anything wrong (from what we can see) with the host. In fact, we have been seeing this error on several hosts now, so it isn't specific to one host. While looking into this issue, we even printed the details of an already signed binary using the following command: codesign -dvvv HelloWorld.app and that prints among other things, similar warning message: ... Timestamp=12 May 2026 at 5:36:0 AM HelloWorld.app: timestamp mismatch: internal time 12 May 2026 at 5:32:59 AM (184 seconds apart) I'm looking for inputs on how we go about debugging this issue and where/how the codesign tool sources these timestamps from (any specific API?) and what value is it comparing against to notice a difference. These affected hosts have different operating system versions some 15.x and some 26.x.