“testflight the requested app is not avaliable”

Hi. I’m developing an application for a client and I’m in his team in the AppStore. Since October 5, 2022, we have encountered such a problem in TestFlight, for all versions of applications the testing period has expired, although some were uploaded only that day. On October 6, I uploaded a new build of the application to TestFlight in hope that the whole will be available for downloading. But that did not happen. It is visible in TestFlight and it has not expired for testing, but when I try to download it on a mobile device through the TestFlight application, I get error that “Could not install App - The request app is not available or doesn’t exist”. Is there a solution to this problem?

Hey guys. We uploaded the app in Testflight but the upload just keeps processing. (Image here: Itunes Testflight..the app upload just keeps processing. (Image here: http://prnt.sc/ekmvwpHas this happened to you before? If so how did you fix this? (It's been over 24 hours now)Best Regards,

In the final page of submit my app for TestFlight, i get the error sayin 'app information could not be saved, try again. if this problem persists then contact us'.

Beginner here. I'm looking to deploy my app on TestFlight and have a few questions: My app has a messaging feature that connects 2 users in-app to chat: is that possible in TestFlight to send a pairing code to connect 2 devices in the app? Can users pay for to unlock premium features? If build only lasts 90 days, what happens if a user pays to unlock premium for a whole year? If so, what happens to the premium account once we launch in app store? Thanks!

Hi, Got this message when i try to test new version of my App with testFlight: The requested app is not available or does not exist. Look on many post, but app is active on Store, last version is 2 month ago. Any idea ? Regards.

I develop games on my M1 Mac Mini using Unity. I then export the build right there into Xcode, and later to App Store Connect. DESCRIPTION OF PROBLEM: I have an issue with a few of my newest builds on TestFlight and now on the App Store. This issue only happens on certain devices. While playing the build in TestFlight (and now the App Store) on an iPad (I will call this iPad 1), the screen bloomed drastically on certain scenes. On the other hand, on a different iPad (I will call this iPad 2) with a different Apple ID, the game was completely fine when it played the build on TestFlight and now on the App Store. Also, when testing on an iPhone which has the same Apple ID as iPad 2, the build on the iPhone blooms unlike the iPad, concluding that this is not an Apple ID issue. This App is made with Unity, and I tried to trace the issue there, although it was not blooming in Unity (Also I never added a post-processing feature

We are experiencing widespread issues (on all versions of iOS) with Testflight In-App purchases failing. Purchases are working as expected in Sandbox environment with Sandbox testers created in iTunes Connect.Normally what used to happen is that we could send a build to our Testflight group and they could use a production App Store account to make purchases (The Apple prompt already says that the purchase is in Beta and they will not be charged. However, now whats happening is the purchase fails with a Cannot connect to iTunes error. To confirm, the SKProducts are loaded perfectly, even a Restore purchase seems to work. Its just buying anything that fails.We have tested using a Sandbox account in TestFlight and this actually works which is not what we expect since Sandbox testers shouldnt work in Testflight?Anyone else experiencing this

I'm experiencing an issue where in-app purchases work correctly in both profile and debug modes. However, when I upload the app to TestFlight, the in-app purchases are not functioning as expected. How can I resolve this issue?

Hello, Implemented MXMetricManagerSubscriber and didReceive(_ payloads: [MXMetricPayload]) gets called with Debug > Simulate MetricKit Payloads. Submitted app to TestFlight (internal testing). However, the app is yet to receive an MXMetricPayload several days after installing the app from TestFlight. Any idea why? Thanks.

My App has published to App Store Connect for test on TestFlight. However, when I click the Install button, TestFlight will cancel installation and the button come back to Install status after the progress ring being 100 precent without any errors. How to fix this problem, I need help...

Is TestFlight down? I can't seem to get the install going. It just stuck at Waiting

I have an app that is publically available for iPad. We also have a beta version that is distributed through TestFlight. Both are nearly identical and both offer in-app purchases.The TestFlight version continuously pops a system dialog whenever the app is launched or comes out of the background. The message is:***************Sign In to iTunes StoreEnter the password for your Apple ID.....***************I don't get this message with the public version of the app.There is something different going on with TestFlight apps or is it expected behavior for a TestFlight app to continuously ask for a sign-in? I can eithe sign in or tap Cancel. Either way, the result is the same.I should mention that I am signed into iTunes & App Store in Settings with the same Apple ID that is requested by the dialog.Thanks,George

Is is ok to sumbit my app to be evaluated for submission to the App Store while I am TestFlighting it?If there are issues that will block submission I'd like to know before I complete beta test.

I get this message in Xcode 11.6 when I try to 'Distribute App' with an archive selected in the Organizer... No suitable application records were found. Verify your bundle identifier ‘com.revware.fincrazy’ is correct. the bundle identifier is correct. I'm trying to submit an archive for distribution so I can test them using TestFlight. I am able to install this app manually on an iPhone connected to my MacBook, but want to use TestFlight. I'm using an Apple Distribution profile and certificate with the Archive Build. I've tried Transporter, and get the same message