There is a field "Feedback Email" on the TestFlight and we are expecting to receive an email when a tester submits feedback. Is there any configuration that I need to check to be able to receive emails when a tester submits feedback?

I've published my app on TestFlight and enabled the public beta link, allowing users to try out the app and provide feedback. I'm considering creating a custom TestFlight badge (Like this - https://askyourself.app/assets/testflight.png) for my app, linking it to the public beta link, and embedding it on my website. Is this an acceptable practice?

I am unable to view my app in testflight. i can see in apple connect but not in testflight. when i try to click the email link for update on in the app, I get the error that "cannot load app"

My WatchOS sometimes just freeze and then I got this error message: "<BLSBacklightSceneUpdateAction: 0x18e539c0; info: <BSSettings: 0x18e70f40> {\n (1) = No;\n (2) = No;\n (3) = Yes;\n}; responder: <_BSActionResponder: 0xc0084f00; active: YES; waiting: YES> clientInvalidated = NO;\nclientEncoded = NO;\nclientResponded = NO;\nreply = <BSMachPortSendOnceRight: 0xc008ca60; usable: NO; (496:aa9f:send-once xpcCode) from (34:59d07:send-once take)>;\nannulled = NO;>" Does anyone have this issue? What is the reason and any solution for this? Thanks!

A month ago, I released a new version for open testers on Testflight. After one week, I found that the number of installs was much lower than the previous version(10 vs 50+). So I check with our testers' latest version on their device. I count how many people updated the latest version by myself. The exact number was much higher than the number shown in the account (50 vs 10). Then I asked Apple support, he said one possible reason is the number of installs referenced is the number of new installs of the beta build. I searched the official definition of the number of installs, it means the number of installations on devices. And my previous version has very stable numbers except this new one. I am confused about this issue and what is the exact definition of the number of installs. I would appreciate it if someone can help me. Thanks!

I recently switched from Admob to Applovin. It worked well in device but when I tried to deploy via Testflight, it failed with following error: Missing Info.plist value. A value for the key “WKApplication”, or “WKWatchKitApp” if your project has a WatchKit App Extension target, is required in “MyApp.app/AppLovinQualityServicePlugin.app” bundle. For details, see: https://developer.apple.com/documentation/watchkit/creating_independent_watchos_apps/setting_up_a_watchos_project (ID: 6caee3d2-4c60-4410-8d68-d0b3b68e1b53) My app is native iOS only and not watchOS app. What did I missing?

Unable to install app. The requested app is either unavailable or does not exist. I encountered this issue when using the upload store, which was not present before (only in testFlight).

We have a use case where we want to have two different builds of our app in TestFlight: one for the test environment and another for production. Each build has a different .env file associated with it, containing different values based on the environment. The test build will only be used by internal testers, whereas the production build will be used by both internal and external testers. I know there was a way years ago to append a suffix to the build number, something like 0.18.1-test, so we could specify which build specifically uses the test environment variables. However, when I try to submit a build to TestFlight with any alpha characters in the build number, App Store Connect rejects it with the error message: '0.18.1-test' is not a valid value for the attribute 'cfBundleShortVersionString'. Are there any current best practices or official guidelines from Apple on handling a scenario like this? What's the recommended approach for differentiating between test and production builds in TestFlight? Our first solution was to place all our test builds in VS App Center and production builds in TestFlight. However, Microsoft recently announced that VS App Center is being retired next year and recommends using TestFlight instead for iOS builds. So, we're looking for a solution that will work with TestFlight going forward.

When we try to add a tester or a group and submit for review, we get the error "There was an error processing your request. Please try again later."

What if I already have an app named "A" but want to upload a new application named "A" The same thing where the old app and can still be used and the new app can still be displayed? **If there are details showing that duplicate names cannot exist, please attach them to me. thank you.

I'm about to submit a react native expo app to the ios app store. Locally the app seems to be fine but when I try testing it with test flight, it crashes on start up. Please see the attached crash log. Crash Log Any help would be greatly appreciated.

In TestFlight I have the problem that I only get crash information from a small fraction of testers. I assume this is because when the application crashes, it responds "No Thanks" when asked to share information with the developer. Is this really the case? What's the point of testing if all I see is the crash counter popping up and I'm not getting any error reports? Installation can be conditioned on acceptance with a "Term of service" that says crash reports will be shared. Without accepting the conditions, the application cannot be installed. But I don't know if this consent has any effect on sending error reports. Does it have any effect on sending error messages? Can anyone advise me what I should set to get such a prompt before installation. Alternatively, how can I arrange to receive more crash reports? Or should I use another service that will give me reports of all errors? Maybe Crashlytics?

In https://developer.apple.com/news/?id=x60uzbu9, it is stated that: "You’ll need to let us know whether or not you’re a trader to submit new apps to the App Store." Currently, I have an app that I submitted for Testflight beta review that is still waiting for review since 20 Mar 2024, 00:00 GMT. I have not submitted the DSA compliance since my company still need to align for the documents. Does not complying yet with the DSA affect Testflight submission?

Hello, everyone, I have been having problems with builds uploaded to TestFlight for a couple of weeks now. These , from the app (iPhone, iPad, Mac), are not downloading. If I try I get an error message saying the app is unavailable or does not exist. If I try to add a build to an external tester group I get the warning : There was an error while processing your request. Please try again later. Checking in the browser termianel I noticed the error : Failed to load resource: the server responded with a status of 422 () with in : message: "API Response Error: TF_BETA_APP_REVIEW_RESPONSE" I've tried everything but can't figure out how to fix it. Can anyone. give me a hand? Do you know what is going on?

I received an email that says, although submission for TestFlight review was successful, you may want to correct the following issues in your next submission for TestFlight review. Once you've corrected the issues, upload a new binary to App Store Connect. I am aware of the one minor issue that needs to be corrected. Which we will upload soon. What I don't understand is that the email says that the Test review was successful but yet My status is still saying waiting for review. Can I get some clarification please....

My archived xcode builds show that they have been successfully uploaded to testflight but once in the appstore they do not appear. Is there anyone else with the same problem?

rt thanks

Hello, We're having a problem from the past week with installing / updating all our apps from Testflight. All the testers get this error message after tapping the "Install" or "Update" button: "Could not install . The requested app is not available or doesn't exist". Can you please help investigate and let us know why this issue occurs? Thank you! Note: We're using Xcode 15.2 both locally and on CI through Xcode Cloud

Does anyone know how TestFlight counts the number of installs, sessions and crashes? I'm seeing totally insane numbers. I don't understand. Right now for the latest beta it shows me: number of installs "-", number of sessions 19 and number of crashes 36. What's that supposed to mean? When I look at the individual testers, sometimes there's already complete crap there. For example, there is a user who has reached 1180 crashes in 13 runs. What? Can you imagine a person who runs an application 1180 times and it crashes? I don't. What's really best, TestFlight gives me almost no crash logs. There were a few from the early betas, but none the last few days. Do you know of any other tool from which I get consistent information on absolutely all crashes?

The app was uploaded correctly in previous versions and suddenly stopped working in Test flight. There is no warning in Xcode when archiving, I use to verify (xcode option) the app before uploading, and upload only for Testing. The owner of the developer account enrollment already asked on last friday and there is no response at all.