“testflight the requested app is not avaliable”

I wanted to bring to your attention an issue recently identified regarding the accessibility of existing production core data on our TestFlight app. Following the completion of a core data migration process, accessing the aforementioned production data has become temporarily unavailable on the TestFlight platform. If I install the testflight app getting a new instance of core data. whereas in production another instance of core data. respectively after lightweight migration data are not merging.

iPadOS 17 brings HealthKit to the iPad. So I've updated my HealthKit-using app to also run on iPadOS. I can debug it from Xcode on iPad simulators and my iPad, but when I upload a build to AppStoreConnect from Xcode and try to install it on my iPad from TestFlight, the install-button is missing and instead there is a label saying incompatible hardware. The app has no other required device capabilities besides healthkit. It was also updated to at least require iOS/iPadOS 17. I can install it on my iPhone but not on the iPad. I also noticed that in this list https://developer.apple.com/support/required-device-capabilities/#ipad-devices no iPad model has the healthkit device capability. Why? Is there some way to find out why exactly TestFlight thinks the iPad is incompatible hardware? Thanks in advance to anyone who can enlighten me here.

I have a app that uses my old backend. I want to switch to new backend. App is currently live on app store. I want to make a copy of this and replace it with new backend and push to testflight. I want to keep making changes to old app with old backend as well. I want to do this parallel. How do I do this?

Hi! I have a closed alpha app that is distributed among developers. I use TestFlight to deliver new app version to developers. Is it possible for developers: Connect device to MacBook. Open Console.app. Filter logs by app name. Note: all these developers are invited to our AppStoreConnect team.

Hi there,the crashlogs are listed for every build in the organizer of XCode - normally. However, if a build is being tested in TestFlight and selected for a release at the same time, only the release crashes are listed. Even if the release is not made Ready for Sale. In AppStore Connect I can see that the build had some crashes in the TestFlight overview. But inside the organizer I can't access those crashes. Since my app is not made Read for Sale yet, I see no crashes in the Organizer, not even the build number.Is there a way to download the crashlogs somehow directly? Or am I doing something wrong?Kind regards,Eduard

I understand from the Xcode release notes that it is now possible to submit visionOS apps to TestFlight. I'm getting the error Asset validation failed Invalid Provisioning Profile. This provisioning profile is not compatible with visionOS apps. when uploading to TestFlight. I use an Xcode managed profile, and am using the same bundle id as for the iOS and Mac versions of the app. In the Certificates, Identifiers & Profiles -> Edit your App ID Configuration it lists iOS, iPadOS, macOS, tvOS, watchOS, visionOS under Platform. Is there some guidance on submitting visionOS apps to TestFlight? Any ideas on how to regenerate the profile to include visionOS apps? Thanks, Damian

I just finished a app for a company and I am going to use TestFlight to distribute it to employees however when I downloaded the app from TestFlight icloud did not work I don’t know why? Help!!!

A few months ago I uploaded the latest version of my application with xcode 11, everything seems fine to me. But when I updated the xcode, now the new versions that I want to distribute does not come out in the testfligh. (The version comes out for a few seconds on the web, in the testflight but not the package, then it is deleted). When I give it to file in the xcode and the whole process, everything ends successfully. but it does not appear in the testflight to be able to distribute it. I checked my emails in case something arrives, but nothing arrives. I do not know if it is because of xcode or another error in the code that cannot be loaded. Help

Hello i have problem with TestFlight app named TFT / Teamfight Tactics by Riot i had acsess to it for a while , now it is gone when i updated it to normal version but i still get updates on never vesions by Riot on testflight on my primary mail account, is there an option to enable the app again because i cannot get a new code and im still in developer program?

I have created an app that allows access to a url using URLSession and it is working correctly when I launch the app using XCode, but it does not work when I submit the app for testing in testfligh. It seems that something is blocking requests made from URLSession. Is it possible that there is some configuration that you are not taking into account for publishing to testflight

Hi. We've recently submitted our app to TestFlight. We've encountered an issue where our testers are unable to download it from TestFlight. They see the app and can click on the INSTALL button. The button changes into a download progress indicator which stops at around 90% and stays stuck there. This happens for all testers on all devices (iPhones and iPads with various iOS versions ranging from 8.0 to 9.2). We use XCode 7.2.Based on this post:http://www.jhreview.com/tech-stack/questions/26346779/testflight-app-version-download-internal-test-does-not-finishwe included the Info.plist file to the Copy Bundle Resources build phase of the app. To our surprise this fixed the issue of testers getting stuck at 90% download but now XCode produces the following warning during the build:Warning: The Copy Bundle Resources build phase contains this target's Info.plist file ...Is it a requirement that the Info.plist be included in the bundle resources

When I uploaded app to TestFlight to test, it shows missing compliance. And I tried this way: https://stackoverflow.com/questions/35841117/missing-compliance-status-in-testflight It used to work. But now it is not. May I ask what should I do to solve the missing compliance problem?