Hello, I am unable to install my app from TestFlight even though the build appears valid and is in internal beta testing. The build was uploaded successfully to App Store Connect and shows as Testing / Internal Testing. The build metadata looks valid: processingState: VALID internalBuildState: IN_BETA_TESTING qcState: BETA_INTERNAL_TESTING usesNonExemptEncryption: false minOsVersion: 15.0 deviceFamilies: IPHONE supportedArchitectures: arm64 However, TestFlight installation fails, and the App Store Connect API returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta contract is missing for the app. My App Store Connect agreements are all active. I checked Business > Agreements and both Paid Apps Agreement and Free Apps Agreement are Active. Bank accounts, tax forms, and compliance also appear Active. This also happens with a newly created app and a fresh build, so it looks like the TestFlight beta contract may be missing or detached on Apple’s backend. Has anyone seen this before, or is there a way to force App Store Connect to refresh the TestFlight beta contract state?

On https://developer.apple.com/documentation/AppIntentsTesting/testing-your-app-intents-code Apple showcases the following example using AppIntentsTesting to query entities indexed in spotlight. For me, calling .spotlightQuery on any entity definition causes a crash. func testAllEventsIndexed() async throws { let eventDef = definitions.entities["EventEntity"] let allIndexed = try await eventDef .spotlightQuery(nil) XCTAssertGreaterThanOrEqual(allIndexed.count, 3) } Crash: expression unexpectedly raised an error: Failed to obtain the result of the distributed invocation after it was executed. Remote threw executionPermissionDenied(requestBundleID: Is anyone else seeing this crash, or is it just me? Thanks!

We are facing an issue with Apple Pay address details while customers are placing orders on our production site. By default, the following values are being passed during checkout: First Name: ApplePay Last Name: Express Address: ApplePay Street When we manually enter these same details, our validation correctly prevents the order from being placed and displays an appropriate error message. However, on our production site, real customers are still able to successfully place orders with these exact details. Could you please help us understand: How these orders are being allowed to proceed despite the validation? Is this behaviour expected from Apple Pay ? How can we prevent orders from being placed with such placeholder address details? Please let us know if you need any additional information from our side. We have also attached an image showing the address details and the corresponding order number for reference. Thanks in advance for your support.

Hi, I am unable to receive any tesflight invite email in order to test on my end, can anyone assist with this issue.

Summary While parallel testing Core Location on the new iOS 26.1 beta (23B5044i), I observed what I believe to be a regression of the issue described here: https://developer.apple.com/forums/thread/779192 Specifically, user positioning underground subway stations is noticeably inaccurate on the beta, whereas the same scenarios remain accurate on the unupgraded device below. I work with the MTA (New York City) and work with the OP of that thread. Happy to provide additional testing or details if helpful. Please let me know what else you need. Test Info Riding NYCT from Wall St to 34th St Penn Station on the 2 train carrying two iphones Recording: https://limewire.com/d/dpTWi#pDC3GRYIdE Expected: Consistent underground positioning comparable to prior releases. Actual: Degraded/inaccurate underground positioning on iOS 26.1 beta. Test Devices Left Screen: iPhone 15 Pro Max - iOS 26.1 beta (23B5044i) Right Screen: iPhone 11 - iOS 18.6.2 (22G100) Blue dots show location set by CoreLocation. Red dot on iphone 11 shows the actual location of both devices as I was able to manually place while travelling through a station. Placement through tunnels is not easy to verify and not usually indicated. Timestamps Comparison of when train was actually observed in a station vs when 26.1 and 18.6.2 CoreLocation updated to the station Fulton St 1:48 iOS 26.1 correctly updates (correctly) 2:16 iOS 18.6.2 updates (28sec late) Park Place 4:12 train arrives 4:15 iOS 18.6.2 updates to ~near Park Place 5:04 iOS 18.6.2 updates to Park Place (correctly) 6:07 iOS 26.1 update to ~near Park Place (over 2 mins late) Chambers St 6:02 train arrives / iOS 18.6.2 updates (correctly) 6:14 iOS 26.1 updates to ~near Chambers 6:18 iOS 26.1 update to Chambers (correctly) Franklin St 6:52 train arrives 6:55 iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update Canal St: 7:16 train arrives 7:18 iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update Houston St 7:54 train arrives 8:00 iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update Christopher St 8:37 iOS 26.1 presumably between Houston St and Christopher St 8:40 train arrives / iOS 18.6.2 updates (correctly) x:xx iOS 26.1 does not update 14 St 9:22 train arrives 9:28 iOS 18.6.2 updates (correctly) 11:01 as train departs station iOS 26.1 updates (1.5 mins late)

Hello to the community. I’m hoping someone here can help me. we have been developing our mobile app with a 3rd party contractor. I used to provide feedback through TestFlight screen shot program and it was great. Straight from my iPhone to the dev team. Screen shots with descriptions of the problem. they recently transferred the app to our account and I think since then we can no longer receive the feedback. in fact, last week I spent 2 hours reviewing the app. Sending tons of screen shot feedback with comments. Thinking they were receiving them. But nothing. when we log into our feedback portal I only see feedback from 70 days ago. And nothing from recent. I made sure that feedback is welcome ( see screen shot ) i tested individual feedback test and got nothing. here are my questions. Is there a way to recover that feedback. Where is it going ? How can I get this feature working properly again so I can effectively and efficiently review the app and provide feedback to the developers.

Hello, My Apple ID 6766831703 My case ID102894773917 I have sent an email to Apple support to report that my app cannot be installed in TestFlight for 4 days. The app build has been successfully uploaded and processed in App Store Connect. The build status currently shows "Ready to Submit" ‘Testing’. I have uploaded 2 versions, 0.1.0 0.1.1, but both show this requested app isn't available or doesn't exist. I have tried to click stop testing, re-invited tester, re-download TestFlight app, and check all agreements, All export compliance questionnaires have been completed. There is no problem. The developer account has also been registered recently. Because the inability to test has seriously delayed our project timeline and business launch in Global. Could Apple team escalate this case for me right now please?

I am trying to create a test case in XCTest using the UI Test target. I have a use case where I use a SwiftUI Canvas to draw a network graph; and the user can drag the graph on the Canvas. After the drag, the user may click on a node. The application presents a popup with the information about the network node clicked. SwiftUI provides the information required for the application to translate the location of the tap into the original location prior to the drag; and so the logic behind the popup can determine which node the network graph was tapped by the user. It appears that the distance of the drag operation performed does not match distance that the image actually moved. The drag distance is always larger than the actual distance dragged. I can observe this during the test execution. The arrow starts at the correct spot but then goes further than the object being dragged. I also observe this when I am driving the application. Is there some standard and supported way to determine the distance that the image on the screen was moved given a specific distance of the "thenDragTo:" coordinate?

We’re unable to add external testing groups to our new builds for our app, Nox AI Wingman (https://apps.apple.com/in/app/nox-ai-wingman/id6753078092), because we keep facing a persistent, unexplained error. Some details: 3 calls + email updates with the team so far, we received no explanation other than directions to wait 48 hours and try again. We’re still unable to submit builds, with no word of any escalation or explanation for where the problem’s coming from. All agreements are signed, the build says “Ready to Submit”, all privacy related and other necessary fields have been filled out properly Browser Console shows the following error on submission: "errors" : [ { "id" : "112b2d19-6105-45c3-b941-3217d905fafc", "status" : "400", "code" : "PARAMETER_ERROR.REQUIRED", "title" : "A required parameter was not provided", "detail" : "The parameter 'filter[build]' is required but was not provided", "source" : { "parameter" : "filter[build]" } } ] } Direct beta review submission gives us the following API error from apple: { "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." } We're helpless. Dev support has no idea what's causing this or how we can prevent this in the future even if they do fix it. We’re in the middle of a crucial launch week, and cannot afford 48 hour windows with no response or communication. Any help at all would be clutch.

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 juice community. firts of all, i'm brazilian dev, soo this conversation will be a lot errors of english. but i'm think is a nice to prove is not a AI generate post here. hehe I want a big tip, how i integrate my app in the fruit ecosystem. Soo, i launch a AI prompt plataform, the idea is make users your own prompt, you make a context for him, like " you are a food master chief", and configure the inputs, like a photo of your freezer, to the AI take the ingredients e make a recipe with AI. The aplication is infinite! The integration, now, is with AI provider. the idea is not make a context with complex Skills.sh, but the common user create your own Prompt/AI and feel a prompt engineer master. i'm think the is a powerful plataform for native apple system. the plataform has url, and if any one has interesting a will chat in the comments the name for see how beaut is.

When running parallel Swift Testing tests that each create their own in-memory ModelContainer, the first xcodebuild test run succeeds but all subsequent runs fail with DefaultStore save failed validation errors — unless DerivedData is deleted between runs. Setup Each test suite creates an isolated in-memory container with a unique name: ModelConfiguration(UUID().uuidString, schema: schema, isStoredInMemoryOnly: true) The @Model class has non-optional properties (e.g. var v: String, var entityDicMoveNr: Int) that are always set in init. Symptoms on second run SwiftData.DefaultStore save failed with error: Error Domain=NSCocoaErrorDomain Code=1560 "Multiple validation errors occurred." NSValidationErrorKey=v, NSValidationErrorValue=null NSValidationErrorKey=entityDicMoveNr, NSValidationErrorValue=null NSValidationErrorKey=historyBackup, NSValidationErrorValue=null The errors appear before test code executes — during SwiftData's internal DefaultStore auto-save. Properties that are always initialized in Swift show as nil in the Core Data layer. What we verified Each run uses a fresh xctest process (different PIDs) Container creation succeeds (no errors in our ModelContainer init) The @Model init always sets all fields — confirmed with debug prints Deleting DerivedData before each run fixes it (but forces a full rebuild) What didn't help Using ModelContext(container) instead of container.mainContext Setting autosaveEnabled = false on both mainContext and custom contexts Using /dev/null URL instead of isStoredInMemoryOnly: true build-for-testing + test-without-building Clearing only Logs/Test or TestResults subdirectories Why not run via swift test? We can't fall back to swift test because our project uses RealityKit custom components, which silently fail to decode in CLI swift test. So xcodebuild test is our only option, making the DerivedData workaround especially costly. Workaround Delete DerivedData before each xcodebuild test invocation. Environment macOS 15.5, Xcode 16.4, Swift Testing with @Suite @MainActor parallel test suites. Question Is there a way to fully isolate in-memory ModelContainer instances so that no metadata leaks between xcodebuild test runs without requiring a full DerivedData clean?

Hi, We have implemented Age Verification in iOS and wanted to test the workflow before releasing the app. How do we test the app before releasing it in production. We currently use Test Flight for testing. We created users in Sandbox but that shows just Texas in Age Assurance.

I am unable to receive an invite email on my apple account in order to accept and get access to testflight for testing apps

Hi everyone, I’m an indie iOS developer working on Kleio, an AI voice keyboard extension that lets you dictate text quickly anywhere you can type. I’m looking for a small group of beta testers who are willing to try it through TestFlight and share feedback about stability, UX, and accessibility. What Kleio does Adds a custom keyboard so you can press the mic button and dictate instead of typing. Uses AI to turn rough speech into cleaned‑up, properly punctuated text. Lets you pick different writing styles (e.g. more formal vs more casual) for how your dictation should read. Supports a personal dictionary for custom words and names. Keeps transcript history on‑device by default, with optional cloud sync and improvement sharing. Includes a “Privacy Mode” toggle when you don’t want anything uploaded. What I’d love feedback on Onboarding flow for first‑time setup and keyboard enabling. The dictation experience inside real apps (Messages, Notes, Mail, social apps, etc.). Latency, accuracy, and how well the edited text matches what you meant to say. Keyboard layout, button placement, and any confusing interactions. Accessibility and inclusion: How well it works with VoiceOver / Switch Control. Any issues with contrast, touch targets, or labels. Any specific needs for users who rely on voice input more than typing. TestFlight link You can join the beta here: https://testflight.apple.com/join/jGY1fZ7S External group: “Twitter” (currently around 9 testers). No login is required for basic dictation; some settings sync features use account sign‑in. How to send feedback Through TestFlight’s built‑in feedback / screenshots. If you run into crashes, unexpected latency, or accessibility problems, details like device model, iOS version, and what app you were dictating into are extremely helpful. Thanks in advance to anyone who’s willing to try Kleio and help me make the keyboard more reliable and accessible.

Hi, I’m experiencing a server-side error in App Store Connect when trying to submit a TestFlight build for review. Details: App: Ngoc Rong 2 Platform: iOS Build status: Complete Distribution: External Testing App Store Connect Web (Safari / Chrome both tested) Steps: Go to TestFlight → Select build Click “Submit for Review” Fill in “What to Test” Click Submit Result: Popup shows: "There was an error processing your request. Please try again later." Notes: Build processing completed successfully Internal testing works External group already created Issue happens consistently Tried different browsers and cleared cache Same issue across multiple builds Is this a known App Store Connect issue? Is there any workaround? Additional information: I have already contacted Apple Developer Support. Case ID: 102871190604 If needed, I can provide further details or logs. Thank you.

I am using Maestro framework for testing iOS. For our tests we need to save pdf's to files. When opening the 'QLOverlayDefaultActionButtonAccessibilityIdentifier' the buttons on the overlay are way off, the coordinates got corrupted. When opening the files app, the next screen has no coordinates for testing. I checked with xcode inspector and the same issue persists.

I have sent an invite to a user for internal testing. They have received the email and clicked the accept test link. It takes them to App Store Connect web login screen. I do not see that they have accepted the role on my dashboard and they do not have access to my app on Testflight. Has anyone had this/similar issue and resolved it?

Hi everyone, I’m facing an issue with my iOS app review. Apple rejected it saying the Support URL is not functional, but the page is accessible and shows contact details (email, phone, address). Also, the app login works fine in TestFlight, but Apple seems unable to log in during review. Has anyone faced similar issues with Support URL validation or login during review? Any suggestions on what might be causing this? Thanks in advance.

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 requires provisioning under an Apple Enterprise Developer account. This introduces considerable operational complexity, as it would require us to maintain separate signing and distribution paths alongside our existing Apple Developer Program membership. Before pursuing that path, we wanted to understand Apple's perspective on the following: Is there a supported or recommended approach for preserving Associated Domains entitlements when an app is re-signed by a third party (e.g., a cloud testing platform)? Are there any provisioning or entitlement configurations that would allow Universal Links to function correctly in re-signed builds without requiring an Enterprise Developer account? Does Apple have documented best practices for validating Universal Link–based flows in automated or cloud-based testing environments? Are there any alternative deep linking patterns that would be more resilient to re-signing while still meeting App Store and platform security requirements? Any guidance or recommendations from Apple on how to handle this within the bounds of the standard Apple Developer Program would be greatly appreciated. Thank you for your time.