“testflight the requested app is not avaliable”

I currently have an app waiting for review on testflight, but I want to try to send it to the store already anyway.Will doing that cancel my testflight submission or it's possible to have the same app on review on both places?

After I entered the beta testing program and installed version 14.5, tracking requests by applications became unavailable. They are permanently off and cannot be turned on. I exited the program and rolled back to 14.4, but the problem persists. I need tracking access to work. I am a game developer. Please help as soon as possible. It is desirable to give the answer in Russian.

Hi, i'm about to submit my app to Testflight review team. My app requires sign in. But I only allow sign in from Apple and Facebook. There is no way I can provide a username / password. Can the review team sign in from Apple directly?

I'm not able to submit an app to TestFlight because the Apple service is considering that I'm using a beta version of Toolchain. This started to happen after upgrading to the latest version of Xcode 10.1 (10B61).[18:07:19]: iTunes Transporter output above ^[18:07:19]: ERROR ITMS-90534: Invalid Toolchain. New apps and app updates must be built with the public (GM) versions of Xcode 9 or later, macOS, and iOS SDK or later. Don't submit apps built with beta software including beta macOS builds.Return status of iTunes Transporter was 1: ERROR ITMS-90534: Invalid Toolchain. New apps and app updates must be built with the public (GM) versions of Xcode 9 or later, macOS, and iOS SDK or later. Don't submit apps built with beta software including beta macOS builds.The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.Anyone else with this problem?

Hi Eskimo, My app getting crashed when launching. App running smoothly on Iphone simulator but trying it on actual device via testflight is no luck. Thanks in advance Symbolicated - https://developer.apple.com/forums/content/attachment/aa821a29-fb6e-412d-ae90-180137550724

Hello Running my Ionic 7 app from Xcode works ok in simulators. I have uploaded to AppStore to test in real devices with Testflight. In an Iphone 8 runs ok, but trying in an Iphone 14 says No se ha podido instalar XXXX.... Vuelve a intentarlo (Couldn't install the app. Try it again)

I have an iPad with iOS 9, I uninstalled TestFlight and when I installed it again it says Unable to Purchase / TestFlight is not compatible with this iPad. And it does not show up on the Purchased tab.

If I install and then click 'open' from Testflight - the app cannot get the userid stored in the iCloud 'ubiquitous' keystore - so it sets up a new id for the user - WRONG If i use testflight to install the app.. but then close testflight and open the app directly by clicking on it - then the app gets the userid from the iCloud keystore and uses that CORRECT Any ideas why this would be happening? It also works correctly if I run in debug mode on xcode Thanks

Hello Apple Team We are integrating App Attest with our backend and seeing a 400 Bad Request response when calling the attestation endpoint. The issue is that the response does not include an X-Request-ID or JSON error payload with id and code, which makes it hard to diagnose. Instead, it only returns a receipt blob. Request Details URL: https://data-development.appattest.apple.com/v1/attestationData Request Headers: Authorization: eyJraWQiOiI0RjVLSzRGV1JaIiwidHlwIjoiSldUIiwiYWxnIjoiRVMyNTYifQ.eyJpc3MiOiJOOVNVR1pNNjdRIiwiZXhwIjoxNzU3MDUxNTYwLCJpYXQiOjE3NTcwNDc5NjB9.MEQCIF236MqPCl6Vexg7RcPUMK8XQeACXogldnpuiNnGQnzgAiBQqASdbJ64g58xfWGpbzY3iohvxBSO5U5ZE3l87JjfmQ Content-Type: application/octet-stream Request Body: (Binary data, logged as [B@59fd7d35) Response Status: 400 Bad Request Response Headers: Date: Fri, 05 Sep 2025 04:52:40 GMT x-b3-traceid: 4c42e18094022424 x-b3-spanid: 4c42e18094022424 Response Body (truncated): receipt: h'

Hello Apple experts. Yesterday all was fine with each Dashboard-App in my developer account. But today, suddenly, the Dashboard-App does not show the TestFlight tab-link. It is not a problem for one specific app, the problem is for all the apps inside my account. Only I can see the App Store - Services- Xcode Cloud tab-links. Why the TestFlight tab-link is missing? Anyone else experience this?. Thanks in advance.

Any ideas, why macOS build in TestFlight are not available for testing. I follow all requirements, but still they are not avaiable. App is builded with Xcode 13.2.1, macOS SDK 12.1. Provisioning and certificate are totally new and all needed entitlements are there?

Hi, I'm building a simple App which uses Backgroundaudio, -refresh and local notifications. If I install the App on my iPhone 6S through Xcode, it works fine, but if I try to send it through TestFlight to either my test iPhone 5c or my friends 6S, it's behavior is strange. The App opens, closes again, asks for the permission to send notifications (with the springboard, not the App behind the alert window). After confirming the notification, the app stays closed. Reopening will directly close it again. I've already deleted all provisioning profiles and signing certificates, created a new Xcode Project with the same source code. Created a new App ID within iTunes Connect. I've put the signing for the project and the target to 'iPhone Distribution'. Nothing is solving the issue. Sometimes Xcode says my App ID or my profiles don't include notifications. If I turn them of, it doesn't solve it. I don't get any crash reports in the orga

I have a completed app that connects to a python API I set up and some NodeJs servers, and I am trying to upload my app to TestFlight to test it. It archives fine and uploads to App Store connect, but it doesn't pass the review saying My app crashes on launch so they are unable to test anything. It still works fine on my real device when I plug my iPhone XR into my Mac. I do have the crash logs from the submission but I honestly don't know how to read them. It says that the crash reports are fully symbolicate but I don't know if they really are or not. I haven't attached them since I don't really know what important information to block out or not. But they do not fully specify the problem. It is hard to debug this issue since the app works fine on my side so I do not know what is happening once it gets to the review side. Also if anything else is needed to help figure this out, like parts of my projects build settings o