Few days ago, I can't add my tester to Internal groups. Checked the api returning 500 as the attached image

Hi Team, I am facing an error in submitting the app store-approved build to Test Flight Beta App review i.e., External Beta, I always faced the following error while submitting the build to Beta App Review: "There was an error processing your request. Please try again later." How can I resolve it? Any suggestion?

Is it possible to distribute apps using TestFlight with the distribution profiles created with Apple Developer Enterprise Program. If yes, can anyone provide the reference links. Thanks Abhilash Reddy

We have an App in testFlight on internal testers. An admin user manages to install TestFlight, another Holder and Admin user is unable to install Testflight and has this message (TestFlight is currently unavailable. Please try again later.) Do you have any advice to give? Thank you

How can I get testflight invitation code

Hello i want a TestFlight code can u please send it to me

Hi, There is a status check in XCode Cloud and I've been trying to upload new builds from local machine to testFlight. Archive success Uploading success However TEST FLIGHT is not showing new builds. Do you face such an issue ?

Good afternoon, I have encountered a problem that I do not have the opportunity to select a build for external testing, but I can test the application through internal testing. How can we make testFlight let me choose the build I currently have?

Hi everyone, I'm new here and i'm developing my first mobile application. I'm using react native & expo to develop it and EAS to build it and submit it to Apple. Everything is ok, when i'm running : npx expo-doctor@latest, no issue. The build is ok, and successfuly submited to Apple. When i'm trying it with TestFlight, i can launch the app, but stay stucked on a whitescreen. I'm trying to reproduce it with the following command : npx expo start --minify --no-dev Unfortunately, my app is running good... :) Anyone encountred the same problem ? FYI : SDK EXPO 51.0.22 Thanks in advance for any tips

I can't seem to upload my standalone watchOS app to TestFlight. Xcode never offers me the proper distribution scheme. I only get file-based distribution mechanisms. The metadata in AppStoreConnect are present, the bundle ids are correct, this is a freshly new created project without any custom content. How is this supposed to work?

We are having an issue where all the builds on our App Store Connect account have been suddenly marked as expired. When we try to upload new builds, the upload is successful, the build is in Ready To Submit state in Testflight, the new build appears in Testflight but when we try to install the app we get the message "The requested app is not available or doesn't exist." How can we solve these issues?

This error is reaction on new build created and uploaded to AppStore with new project but same bundleId/displayName/signingInfo. Here is the scenario with symbolic values to explain it better: Build #1 (Version 1.0) project: P1 Bundle id: com.some.app Display name: My App Signing info: TeamX, CertificateX (automatic signing) I had to move the app to new project with completely new targets/configs/sources but same app metadata. Build #2 (Version 1.0) project: P2 (new) Bundle id: com.some.app Display name: My App Signing info: TeamX, CertificateX (automatic signing) So you can see that all is changed but the important app metadata (BundleId, DisplayName, Signing info) remained the same. Yet the upload of build 2 results with: ITMS-90129: The bundle uses a bundle name or display name that is already taken Note that the Build #2 showed in "AppStoreConnect / TestFlight / iOS Builds / Version 1.0" for a few seconds as "Processing" but than disapeared with the error. Thus Apple tries to add the new build #2 it to proper application version but than for some reason it thinks that Build #1 and #2 comes from different applications. Any thoughts why?

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?

This error no solution is available.

Cannot add the internal testers to the newly added build to testflight. Can add external testers, but this might be stuck for waiting in review as well (not certain about this one yet).

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...

I'm trying to distribute our app on TestFlight. Although I have enrolled to the developer program. I get this error: I tried logging off and logging in again in xcode. But it didnt solve the issue. How can I solve this problem?

The answer to my question is probably very simple but I've spent twelve hours trying to find it myself and I am at my wit's end. Searching the web shows multiple sufferers from, and multiple answers to, this same problem from at least ten years ago. I've a SwiftUI macOS/iOS app that is not finished but at a stage where I want to get it ready for TestFlight. I set it up on App State Connect and set Xcode Cloud to build it on GitHub commits. The first build revealed some obvious omissions, easily fixed, then I hit this one, for macOS: Missing required icon. The application bundle does not contain an icon in ICNS format, containing both a 512x512 and a 512x512@2x image. [In passing, I'll note the app, passes muster for the iOS platform] I make a 1024x1024 PNG .. convert it to ICNS with GraphicConverter .. convert it again with iconutil to a iconset and add it to my app. I do a regular build in Xcode and, there it is, my .icns file in the app bundle. I commit to fire off another Xcode Cloud build, but get the same error. Especially frustrating because I can see the ".. application bundle does contain an icon in ICNS format, containing both a 512x512 and a 512x512@2x image". It's hard to debug from an abundantly obvious incorrect diagnostic, but I do have to get past this and start fiddling with assorted settings .. ten builds later, still no joy. I did notice that my Info.plist file (autogenerated) doesn't contain the string "icon" and that, for example, Mail.app has: <key>CFBundleIconFile</key> <string>ApplicationIcon</string> <key>CFBundleIconName</key> <string>ApplicationIcon</string> If the build process checks for an icon based on the Info.plist contents then the reported error could be more correct, ".. application bundle's Info.plist file makes no reference to an icon in ICNS format .." One possible complication is that my app includes embedded custom fonts and so it need a Fonts.plist file for them. I set that file as my INFOPLIST_FILE <key>UIAppFonts</key> <array> <string>Zerlina.otf</string> <string>Gorton-Condensed.otf</string> <string>Gorton-Normal-180.otf</string> <string>Gorton-Normal-120.otf</string> </array> <key>ATSApplicationFontsPath</key> <string>.</string> The contents of Fonts.plist are copied to the final Info.plist. Maybe that defeated some of the Info autogeneration? I see no setting for CFBundleIconFile so can't add it myself. I'm confident pressing "Submit" on this will suddenly clear my mental murk but, for now, I need help .. thanks for any ..

Beta testers outside the US, for our MacOS App, are being told their ID is not valid in the US Store and that they must switch to a store in their country. Yet the store switch fails Essentially beta testers outside the US cannot do testflight sandbox eCommerce for the Mac version of our app. Note that eCommerce on the Mac works for US based testers and eCommerce for the iOS/iPadOS works for testers in all territories. Many of these testers are in India, the UK and Canada. We believe that this is incorrect, that storeKit is not correctly detecting the AppStore Region for mac based testflight eCommerce. At this point we have 382 testers, most outside the US and we can only Beta Test our app with US users. Attached are images of the messages that are coming from storeKit: Here is a link to a video from a user in Canada who is demonstrating the problem (cut and paste into browser) https://youtu.be/kB818wfVld4 Here is another link to a video from a user in Canada who is demonstrating the problem (cut and paste into browser). https://youtu.be/7uAZKo8wpfU We see that there is another post with a similar problem. Similar eCommerce Problem Because eCommerce works in all territories on iOS/iPadOS but ONLY in the US for Mac we suspect that this is an error that either a DBA or a coder will need to fix. Any insights from anyone would be appreciated.

We encountered a weird situation recently. Our daily build process upload an app with a daily incremental 4-digit build number, e.g. 4000, 4001, 4002, etc. Our release build number has a specific requirement to use the date, such as 20240719. In the past I have learned that in order to upload a new build for the same version number, the new build number needs to be greater than the old one. Thus, if I have uploaded 200.1.0 (20240719), I cannot upload 200.1.0 (4001) anymore, because the daily build's build number is smaller than the release build. I have to expire the 20240719 build in order for the daily build to continue, which is fine. The problem is, yesterday I submitted 200.1.0 (20240719) for App Store review then got approved. While today's daily build is 200.2.0 (4001) and when it is uploaded, it got rejected for the following error message: This bundle is invalid. The value for key CFBundleVersion [4001] in the Info.plist file must contain a higher version than that of the previously uploaded version [20240719]. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion With error code STATE_ERROR.VALIDATION_ERROR.90061 for id [redacted] Asset validation failed (-19208) This befuddles me, because the 20240719 build submitted for review is in an older release version, while the daily build 4001 is using the newer release version number. It seems that TestFlight decided to compare build numbers while ignoring the version numbers?! Furthermore, after I canceled my approved submission for 200.1.0 (20240719), surprisingly the 200.2.0 (4001) can be uploaded without an error! 😲 It seems that the only factor is whether the build is submitted or not. If an older version number higher build (200.1.0 (20240719)) is not submitted, then TestFlight happily allows newer version number lower build (200.2.0 (4001)) to be uploaded. In contrast, if submitted, then 4001 is not allowed to be uploaded! Is it an expected behavior? Thank you for the patience.