“testflight the requested app is not avaliable”

I have submitted a new version of an app to Testflight and completed all of the meta-data and invited all required (external testers).When one of the external testers attempts to launch the app from Testflight, they are receiving an old version of the app - even though the new version of the app is listed in Testflight. I know this because they are seeing a splash-screen which, in fact, is removed from the new version. In addition, their old version shows the splash-screen and immediately crashes.I have compelted a number of steps to solve the problem, but to no avail. The tester has uninstalled Testflight and the old app, and attempted to reinstall - still the old version. I have set up a test account which I have used to launch the app from Testflight, on my own device. This works - I see the new version (and it runs). When the external uses this test Apple ID (same username/password) they still get t

If I try to run Instrument's logger for an app downloaded from TestFlight it says Permission to debug app name was denied. Recover Suggestion: The app must be debuggable and signed with 'get-task-allow'. How do you make the app debuggable? (I tried creating an archive with the scheme set to Debug, but after uploading that to TestFlight, it doesn't appear. So presumably its not possible to upload an app built with debug scheme builds to TF?). Therefore how can I make a TF build debuggable?, and how to sign it with get-task-allow? Does it have to be a developer distribution .ipa rather than a TestFlight build to enable Instruments/Logger to run it?

After uploading the Application on testflight it is not able to login inside my application as it says internal server error, while in debug or in release mode or in physical device it is running even getting logged in also, i don't know what is the excat issue is going. Is it of testflight issue or my application? i have checked for my API it is working fine even my website is logged in using same API but here it is not happening.

Hi, I have a .NET MAUI app running on .NET 9. When I test locally in debug or release mode it works perfectly fine, but when testing from TestFlight it crashes almost immediately every time. I have sent the crash report to TestFlight and produced the symbolicated.crash file (attached), but I'm not sure it's helpful for understanding how to fix the issue. If anyone can help me understand what the issue might be and any possible fixes it'd be very much appreciated. I'm developing using Visual Studio 2022 paired to my Mac. I have distributed previously without issue, but now can't seem to, even after reverting recent code. net9.0-ios 15.0 symbolicated.crash

Guten Tag, ich würde gerne ein Übungsprojekt im TestFlight bereitstellen, so dass man es in TestFlight nutzen kann aber eben nur im TestFlight. Es sollte nicht im regulären AppStore verfügbar sein. Kann mir jemand sagen, welche Option ich dann auswählen muss? Vielen Dank für die Hilfe! Thorsten Freimann

We have well over 100 apps in the iOS AppStore, and use TestFlight extensively. We are running into a problem, though, because we have run up against the 10 app limit for testing in TestFlight, but there seems to be no way to remove older apps from TF since they've been Submitted for Review. When we click on the Prerelease tab for a submitted app, nothing is available, so we can't turn TF off for that app.Are we just missing something, or is this a known issue?

I had built an app which is already available in the app store with version 1.0. This app has Local database i.e(SQLITE). Now I am working on next Version i.e 1.1 And in this Version, I have added a new table to my local DB. With this the development is complete.Now, using test flight I am performing Internal Testing.Let's Consider two Scenarios:Case 1:On my device, I had freshly installed the beta build version 1.1 from testFlight. Once installed, I checked my local DB & found that my local DB is updated with the newly added table.So this is working fine.Case 2:Let's consider a scenario Wherein on my device I am running my app store build i.e version 1.0 and now I am installing the beta build from Testflight. Once clicked on install button I get a message Do you want to update the existing app and by clicking on the ok button the beta build which is version 1.1 is installed on the app.But when I checked my local DB I found that the Database i

Hi everyone, I've uploaded the app on TestFlight and try to configure the experience but when I launch the App Clip experience from TestFlight it crashes, instead if I run from Xcode with the same link everything works. Are you experiencing the same problem? Do you know how to solve?

Could not install Your request could not be completed. Try again. Nothing has changed from our side, other than we uploaded and submitted a new build. Anyone else having these issues?

Hi, We are developing react native app, and we are having issue with ATS policy in production build distributed to TestFlight internal testing, requests to https are being killed. The preview build ad-hoc distribution is working fine. (I am testing the app on physical device) I will described what I've tried and supply you with logs from different tools. I tried to disable ATS - requests are working enable ATS (no change to default config) - requests are failing with following error Task <55618987-64A8-4C04-9B00-2EFF074D796C>.<1> finished with error [-1022] Error Domain=NSURLErrorDomain Code=-1022 The resource could not be loaded because the App Transport Security policy requires the use of a secure connection. UserInfo={NSLocalizedDescription=The resource could not be loaded because the App Transport Security policy requires the use of a secure connection., NSErrorFailingURLStringKey=, NSErrorFailin

I'm a little confused as to whether TestFlight is a mandatory step to publish an application to the store. If my build in TestFlight is waiting for Review, does this mean that I can't publish the application in the store either?

Hi, yesterday when I was trying to release the TestFlight build of my app the xcode said that it could not authenticate my apple ID. I then came to know that it actually wanted me to complete and aggrement which was Paid Apps Agreement. This agreeemnet is to be made if one has to sell their app on AppStore or make in-app-purchases. I want to ask if it was mandatory for me to sign that agreement? As the solution which I could come across suggested that xcode blocks the distribution if there is a pending agreement.

I have an iOS 9/watchOS 2 app approved for external TestFlight distribution. External beta testers are able to install and use the iPhone app fine, but cannot install the watch app. Within the TestFlight app, they toggle the Install on Apple Watch switch. After about a second, the switch toggles back to off and the watch app is not installed. I can reproduce this assing myself as a TestFlight external user, and do not see anything written to the iPhone or Apple Watch log in the Devices window in Xcode with the switch is toggled. The watch app runs fine when deployed to the phone via Xcode. Has anyone else seen a similar issue and/pr have a workaround? I thought perhaps it was related to this thread, but since a fix is now in place, I no longer think that's the case. FWIW, the same build of this app (Apple ID: 591671468) has been In Review since the 14th, while most of the other iOS 9 u