Overview

Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds

We have a group of Macs that mount SMB shares over 10 GbE with jumbo frames (MTU 9000). Since late June, they have been kernel panicking several times a day with the same assertion: panic(cpu N caller ...): assertion failed: m->m_flags & M_PKTHDR, file: .../xnu/bsd/kern/uipc_mbuf.c, line: 4839 @uipc_socket.c:8260 Panicked thread: dlil_input_en0 Last started kext: com.apple.filesystems.smbfs 6.0.1 Environment Clients: Mac Studio (M1 Max and M1 Ultra) and Mac Pro (2019, Intel with T2), using the built-in 10GBASE-T at MTU 9000 macOS 26.5.1 (25F80), 26.6.2 (25G83) and 26.7 (25G229); it panics on all three Servers: Samba-based NAS, SMB 3.1.1, signing on, encryption off Filed as FB24912731 What we've found It still panics with our third-party EDR fully uninstalled. The Mac that panics needs an active SMB session. A Mac left on the network without a share mounted stayed up through several events that took down the others. Panics are often simultaneous across machines: two to six Macs, with different hardware and different macOS builds, within the same minute. It doesn't need sustained heavy throughput. Some panics came within minutes of reconnecting, during light editing. Setting kern.skywalk.flowswitch.rx_agg_tcp_host=0 did not help. The switch and server links stay up, and spanning tree doesn't change during these events. Only the Macs' ports drop. In one server-side capture, the client stopped sending within about 0.2 ms of receiving a READ response made of 8948-byte frames. That fits the panicked thread being dlil_input. Two existing threads look related Kernel panic using Vagrant synced folders via NFS beginning with macOS 15.4 (FB17853906). A DTS reply there said the issue is in kernel mbuf management and that SMB "is very likely to experience a similar panic." Incorrect packet handling in SMBClient MacOS 26, which describes a race in SMBClient under heavy load above about 10 Gbps. Questions Is this the same underlying issue as FB17853906, and is a fix planned for macOS 26? Our 2019 Mac Pros can't move to a later major release. Is there a known workaround, such as a sysctl, an nsmb.conf option, or a change to MTU or offload settings? Is there logging or a diagnostic we can leave enabled to capture more state at panic time? We can't reproduce this on demand, but between several machines we see it multiple times a day. We can provide full panic reports, sysdiagnoses, and packet captures from both client and server sides.

Circling back on the LocalLM Lab arc. With v0.7, we've moved from prompt experimentation into real app development on Apple's Foundation Models local AI. The LocalLM Lab SDK lets you build that same on-device model and MCP client this thread has covered directly into your own app, with real tool and data access (Slack, Todoist, GitHub, Notion, Linear, plus Calendar, Reminders, Contacts and Location). And you can ship your app including through the Mac App Store. This is a big improvement over version 0.6, where the localai-cli toolkit needed LocalLM Lab installed and running. On the other hand, the SDK (LocalLMLabSDKCore) doesn't relay through anything; it links FoundationModels and a real MCP client directly into your own binary and is totally self-contained. The example included in the SDK, Plate Today, has actually been built into a sandboxed test app and verified working, with a signed path to a Mac App Store .pkg (Apple Distribution signing + provisioning profile pipeline). That's "verified signable and sandbox-compatible," to be precise. Entitlements (from personal experience: always a complicated topic): com.apple.security.app-sandbox + com.apple.security.network.client for the app itself, plus the standard personal-information entitlements per connector used (com.apple.security.personal-information.calendars, .addressbook, .location) and matching NS*UsageDescription strings in Info.plist. The one worth flagging specifically: the network entitlement is easy to miss and fails silently rather than throwing. Without it, MCP connections and Weather calls just hang with no error surfaced. OAuth handling requires the app delegate callback (application(_:open:)), not SwiftUI's .onOpenURL. Worth knowing before wiring it up if you're SwiftUI-only. Full entitlements list + SDK guide: https://github.com/ancientcomputing/locallm/blob/main/docs/sdk-guide.md Feature page: thisbrain.ai/locallm/sdk.html I hope the availability of the SDK (free, Apache 2.0 license) will give folks further incentive to explore local AI-enabled applications on the Mac. What else would you want to do that the SDK doesn't currently support? File picker? Calendar/Reminders/Contacts edits & writes?

(I don't follow the AI stuff here, so sorry if this is a stupid question. Or the wrong category.) There is a new fangled AI mode called JEV. Can the current Apple Intelligence libraries do something like it, or is this a WWDC27 thing?

Since 23 September 2026, TestFlight has stopped working for our app, and nothing on our side fixes it. It looks like the same beta contract problem described in threads 814565 and 821498. App Obaloot: Apple ID 6815224192, bundle ID com.ossaritas.obaloot Version 1.0.0, not released yet (Prepare for Submission) What happened On 23 Sep 2026 at 17:29:53 UTC, builds 1.0.0 (56), (57) and (59) all expired at the same second. Nobody on our team expired them. Builds 56 and 57 had been approved in Beta App Review that same day. Since then, no tester can install any build, internal or external. Builds 60, 94 and 148 process as Valid and are available to our internal group, but tapping Install in TestFlight shows: "Could not install Obaloot. The requested app is not available or doesn't exist." Submitting a build for Beta App Review through the App Store Connect API returns 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING: "Beta contract is missing for the app." This happened for build 60 on 23 Sep and build 94 on 24 Sep. Already checked All agreements under Business are Active, nothing is pending, and the membership is active. Test Information (description, feedback email, review contact) and the beta license agreement are filled in. Export compliance is set (no non-exempt encryption). New builds fail the same way. Deleting the app from the device before installing gives the same error. Apple Developer System Status shows no outage. Support Developer Support case: 102974806458 Could someone from the TestFlight team check our team's beta contract and restore it? I'm happy to share any details privately.

Posting here to see if anyone has found a workaround and/or to get Apple employees' eyes on it. I'm not sure when this bug was introduced but I've found that in Safari on iOS 27, I'm unable to download API keys from App Store Connect. Reported as a Safari bug in Feedback Assistant (FB24994724). I checked web inspector's console and network logs for both my iPad and iPhone; no JS errors and a nondescript network error for the key's fetch request. Google Chrome for iPad/iPhone downloads the .p8 key file without issue, so this feels more like a Safari bug than an App Store Connect bug.

Removed.

ZBTEXT <u>ZBTEXTU</u>

Removed.

Removed.

Removed.

Hi there, I am working on a (Mac Catalyst) HomeKit my own private application, which observes different characteristics of different accessories. This works (also thanks to the advice here, thanks again to all who helped!) like a charm. Now I've found that one of my outlets which is connected through Matter supports power consumption (in Home.app), but there is no characteristic for that, all I can see is its power state. Self-evidently, access to the consumption would be something Matter-specific. At this moment, to save time, I'd rather not study the complete Matter kit in detail if it can be dodged for this particular very limited goal. Is it possible just as simply as possible to read in (if readable) and observe (if observable) those extra Matter characteristics (if any) for an HMAccessory, presumably through its matterNodeID somehow? I'd be grateful for a sample code, if some is available (preferably ObjC, but of course Swift better'n nothing). Thanks a lot!

After about effort of 40 days I got my DUNs number today, and email says that I must register with Apple after 24-48 hours. But on Apple developers page when I try to enroll it throws me error "Your enrollment in the Apple Developer Program could not be completed at this time." and I could not fill basic forms there. I'm in quite big trouble if it delays DUNs will be expired not sure how log it will take again.

Hi, I’m trying to enroll in the Apple Developer Program, but for some reason I’m unable to complete the payment. Initially, my enrollment status remained pending, nothing happened fo weeks so I tried again, but now I’m getting an error saying that the payment could not be processed. My payment method is valid and works without issues on other platforms. Could you please check if there is any issue with my Apple Developer account or if you need any additional information from me to complete the enrollment? Thank you.

Posting this partly to ask for help and partly because I can't believe it's real. The 8 week wait I started an organization enrollment through the web. Document verification took 8 weeks — business registry, translated records, signed authorization letter from our Managing Director, my photo ID, a selfie holding the ID, VAT certificate. Eventually: approved. Contract signed. All that was left was paying the $99. The payment that never happened My Kosovo business card wouldn't go through. Tried my US card — the order was accepted and showed as pending, but no money was ever actually taken. No charge, no decline, nothing on the statement. Waited the 2 business days Apple's confirmation email promised. Then another 4 days. Nothing. No notification, no error, no status. Support's fix: delete the approval I contacted Developer Support — and anything else I could find. An advisor told me to enroll through the Apple Developer app instead, because alternate payment options are only available there. I downloaded it, signed in, and it wouldn't let me enroll. So support reset my approved organization enrollment — the one that took 8 weeks — so that I could "now enroll through the app." I emailed back immediately to confirm they understood my enrollment had already been approved, and to ask whether re-enrolling would mean waiting another 8 weeks. No reply. Point zero I tried the app anyway. It asks for a government ID or passport. Open camera, take the photo, it loads, then fails: Document is not available for this region. Same for the passport. Same for the ID. So here's where I am: My approved enrollment is gone The app can't verify me — my country's documents aren't supported The web billing form doesn't work for my country's address I can't request phone support — the callback form doesn't accept Kosovo (+383) numbers No reply to my emails Kosovo is a supported App Store territory. But apparently developers here can't actually enroll. Our app is already live on Google Play in 177 countries. We just want to pay Apple $99 and ship on iOS. Has anyone from a smaller/unsupported market dealt with this? Specifically: is there any way to get a human at Developer Support to reinstate an enrollment they cancelled, or to pay by invoice/bank transfer? Or is registering a US entity the only real answer here?

We test Apple Pay in the sandbox on supervised iPhones in a device lab (Apple Configurator supervision, no MDM enrollment, no SIM, iOS 26.x). Since late September two of the test cards from the Sandbox Testing page no longer add to Wallet. Discover test cards still add fine on the same devices and accounts. Filed as FB24994276 (Visa) and FB24994258 (Mastercard), with device logs and timestamps. Visa 4622 9431 2318 9285 (FB24994276), only on our lab devices: eligibility → 412 → TSM sync → 200, "received eligibility status: 1" terms shown and accepted provision → HTTP 403 → PKProvisioningErrorDomain Code=3 → "Invalid Card" Same result on two different lab iPhones, including one signed in to a brand-new sandbox account. The same new account and the same card add successfully on an unsupervised iPhone on a home network (iOS 18.2.1). Neither side sends location data. Mastercard 5204 2452 5046 0049 (FB24994258), on every device we tried, lab and home, iOS 18.2.1 and 26.x: eligibility → 412 → TSM sync → retry → HTTP 500 → PKProvisioningErrorDomain Code=5 Questions: What does the 403 at the provisioning step mean for the Visa card? Does supervision, the iOS version, our network egress, or the fact that our devices re-provision cards every test session play a role? Is the Mastercard sandbox environment currently broken, or is there a Mastercard test card that works? Happy to capture a sysdiagnose with the Wallet logging profile if that helps.

Hi, I am still unable to complete my Apple Developer Program enrollment. My Apple Developer Support case number is 102973696378. Developer Support previously informed me that the issue appeared to be caused by a mismatch between the trusted phone numbers on my Apple Account and my enrollment region. At that time, my account had both a Pakistan (+92) number and a UK (+44) number. Following Apple Support’s instructions, I removed the UK (+44) number several days ago. My Apple Account now only has my Pakistan (+92) trusted phone number, and I am enrolling using Pakistan as my country/region with my Pakistani identification details. However, I am still receiving the same error: “Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time.” Since the phone number mismatch has already been corrected, I believe the previous enrollment attempt or old region information may still be associated with my account. Could Apple Developer Support please manually reset or clear my Apple Developer Program enrollment so I can submit a fresh enrollment? Case ID: 102973696378 I would appreciate any help in getting the enrollment reset. Thank you.

Hi everyone, This is my first time enrolling in the Apple Developer Program as an individual, so I’d appreciate some guidance. On Saturday, September 26, I went through the membership purchase process and reached the order acknowledgement page. My account still shows “Pending” and “Purchase your membership.” As of September 28, the $99 transaction was still marked as pending in the cardholder’s bank. I’ve contacted Apple Developer Support and am waiting for a reply. I live in Russia and cannot make this payment with any of my own Russian-issued bank cards. With my friend’s permission, I used their card. I understand that Apple may need additional verification, and I’m happy to provide it privately to Support. Has anyone experienced something similar? Should I continue waiting for the order to be processed, or is there another step I should take? I’d like to avoid placing a duplicate order. Thank you for your help.

My app was rejected under Guideline 1.1 - Safety - Objectionable Content, flagged in the app metadata (not a binary issue). I updated the public App Store Description to remove wording that seemed like the most likely trigger, then asked App Review for confirmation before resubmitting, but the response was a boilerplate message that didn't confirm whether the edit addressed the issue. Has anyone had success getting App Review to confirm which specific text in the metadata triggered a Guideline 1.1 flag, or is it trial-and-error on the wording? Any tips on how to get more targeted feedback in this situation would be appreciated. Thanks!

I've been working on an app. It uses iCloud syncing. 48 hours ago everything was working 100%. Make a change on the iPhone it immediately changed on the Mac. Change on the Mac, it immediately changed on the iPhone. I didn't work on it yesterday. I updated to iOS26.4 on the iPhone and 26.4 on the Mac yesterday instead. Today, I pull up the project again. I made NO changes to the code or settings. Make a change on the iPhone it immediately updates on the Mac. Make a change on the Mac, nothing happens on the iPhone. I've waited an hour, and the change never happens. If you leave the iPhone app, then return, it updates as it should. It appears that iCloud's silent notification is to being received by the iPhone. Anyone else having the issue? Is there something new with iOS 26.4 that needs to be adjusted to get this to work? Again, works flawlessly with the Mac, just not with the iPhone.