“testflight the requested app is not avaliable”

There is one app in testFlight uploaded and released on 7/11. Up to 14/11, it was installing and working fine, but from today when we try to install the app from TestFlight on all iPhones it is showing Could Not Install APP TestFlight couldn't connect to App Store Connect issue. Try again later. I have attached the screenshot of that.

Hello, does anyone have any info/insight when we will be able to test app version that contains the Family Controls entitlement to TestFlight? iOS 16 is getting really close.. When we try to upload the build, Xcode shows the entitlements error and the Apple Developer portal shows that Family Controls is still available only for Development profile. Thanks!

HI I wonder if some one can help me please, I have been developing my app with a team of developers in India. it's been a long srtruggle but that is another story. Basically the builds they send me to tset crash randomly I could be using a feature and the app will just close. I have experienced this on all 3 of my devices and some of my users have reported this as well (on live previous builds). The annoying thing is that my developers always argue that they are not experiencing any crashes. The only solution I can think of is that they need to know what is going on on my devices when crashes happen. So we have submitted the app through TestFlight and I downloaded. I experienced 4 crashes on my different devices, 4 days later TestFlight is still showing crashes as 0. I spoke to Apple and was told about Xcode I have since spoken to my developers and they have said they are using this. Basically I need my developers to be able to see what is happening on my

I am using an iPhone 14, with IOS 18 on a managed account and keep getting Temporarily Unavailable error when trying to launch TestFlight. This app worked on another organization managed device (same device, IOS) but several others are giving temp unavailable errors. Can anyone help guide me on how to fix this error? I have tried uninstalling, restarting, reinstalling several times with no luck.

After using a build for App App Store Release, my new builds don't seem to be available to test in testflight. I can only use the new builds for App Store release. Any ideas?

Hi everyone, I'm following up on this post I made earlier about an issue I'm having with FamilyControls and the DeviceActivityMonitor extension not working for external TestFlight testers. To briefly recap: I have official Apple approval for the com.apple.developer.family-controls entitlement (distribution) The entitlement is added to both my main app and the DeviceActivityMonitor extension The App Group is correctly configured for both targets On internal TestFlight builds, everything works as expected: app blocking works, the extension runs, and selected apps are shielded. On external TestFlight builds, users get the Screen Time permission prompt, can select apps to block, but nothing is blocked. Since that post, I submitted a Code Level Support request, and Apple asked me to file a bug report via Feedback Assistant. I did that almost a month ago. The only reply I’ve received since is that they can’t give a timeframe o

After upgrading to macOS 26, I cannot install or update my app from either the App Store or TestFlight. Other apps update and install normally. Steps: Before upgrading, the app was installed via TestFlight and worked fine. After upgrading, I tried to update the app from the App Store: The update stalls at ~90% and never completes. Other apps update successfully. I launched the already-installed TestFlight version — it worked. After deleting the app, I tried reinstalling from TestFlight and got the error: “The app couldn’t be downloaded. Try again.” I tried rebooting, logging out/in of my Apple ID, and submitting a new TestFlight build — same issue. Environment: Originally built with Xcode 14 Also tried a new build with Xcode 16 App is compatible with macOS 26. Distribution outside the App Store (Developer ID signed and notarized build) runs fine

I am trying to test an app with InApp purchase in TestFlight. I have also been testing in the Sandbox. In either environment I can not see purchases made on one machine, on a second machine. In TestFlight I am using my real Apple ID in the Test Flight app. In the Sandbox I am using a Sandbox user set up in AppStoreConnect. Should purchases be recognised on two machines? I am trying to test functionality or purchasing a non-consumable on one machine and then also having access to it on a second. This is just extra functionality enabled on time only. Should I be able to see purchases across the machines in SandBox or TestFlight or are they just simulating locally? I have the same problem with Key values in iCloud which I can not see between two machines with the same user.

Hello, Our team are encountering a strange crash that seems to be occurring after the app is updated automatically through TestFlight. The crash is not easily reproducible and seems to be happening intermittently whenever a build is pushed out to TestFlight. We have determined that the app needs to be in the background when the auto-update occurs From the logs it looks like TestFlight is killing the backgrounded app, installing the updated version and then trying to start it in the background. We have tried using appcenter to catch the exception but it seems like it won't allow any data to be written at the time which means we have struggled to collect logs for the issue. We have managed to collect some logs streamed from the device during the process if they are of any help as well. Streamed logs: streamedlogs.log Symbolicated Crash log 11-11_crash.log

We're developing an Electron app for MacOS App Store. When updating our app through TestFlight, TestFlight prompts Close This App to Update, and when I click Continue our app would be Terminated for update. Now this is where things go wrong. On MacOS 15 our app seems to be gracefully terminating (We attached it with lldb and it shows that our app returns with 0 when we click Continue) which is fine. However for MacOS 26 though, it seems that TestFlight just directly SIGKILLs our app (indicated by lldb), which means that all of our app's child processes are left orphaned. Even worse, our app is singleton, which means that when the app relaunches it fails, because the leftover child processes from the previously SIGKILLed session is still alive, and even if we want to kill those orphaned child processes we can't because our app is sandboxed thus cannot kill processes ou

Good day, please send the code for your application to TestFlight. Rudolf Chejn

The content filtering functionality works perfectly when I install the app directly on my mobile device from Xcode. However, when the app is distributed via TestFlight, the app does not prompt users to save configurations, which causes the configuration-saving process to fail. This app is meant for public use. As per my understanding from TN3134, content filter apps can be shipped for devices running iOS 16 and later. iOS app extension 9.0. supervised devices only iOS app extension 15.0. apps using Screen Time API iOS app extension 16.0. per app on managed devices

My app works fine when run from Xcode on iPhone but crashes when run from TestFlight. The Build Configuration for Run & Archive is Release. The log from my iPhone is below. Please help. Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Triggered by Thread: 0 Application Specific Information: abort() called Kernel Triage: VM - Compressor failed a blocking pager_get VM - Compressor failed a blocking pager_get VM - Compressor failed a blocking pager_get VM - Compressor failed a blocking pager_get VM - Compressor failed a blocking pager_get Thread 0 Crashed: 0 libsystem_kernel.dylib 0x1bbd9fbbc __pthread_kill + 8 Thread 1 name: com.apple.uikit.eventfetch-thread Thread 1: 0 libsystem_kernel.dylib 0x1bbd99aac mach_msg_trap + 8 Thread 2 name: com.apple.coremedia.rootQueue.47 Thread 2: 0 libsystem_kernel.dylib 0x1bbd99b00 semaphore_timedwait_trap + 8 Thread 3 name: com.apple.coremedia.rootQueue.47 Thread 3: 0 li