Our Testers are unable to access the current TestFlight build, receiving a "Couldn't load app. TestFlight is currently unavailable. Try again" error.
This issue began last night.
The problem affects all builds, including older ones that were previously accessible.
Multiple attempts (4-5) to upload and test a new build (latest: 1.0.0+53, uploaded at 11:44 am IST) have not resolved the issue; in fact, it appears to have exacerbated it, impacting even previously working builds.
This is blocking the release and testing of our new app version.We have already tried refreshing the distribution/development certificates.
macOS version: 14.5 (23F79)
Xcode version: 15.3 (15E204a)
Info.plist entries have been cross-checked and verified.
TestFlight logs show a 500 Internal Server Error for the following request: https://testflight.apple.com/v2/accounts/0b7148c2-759f-4eea-b1e9-9779d2c96c25/apps/6476102474/builds/160325015 The server response includes a 500 status code.
TestFlight
RSS for tagUse TestFlight in App Store Connect to invite and manage beta testers for iOS, iPadOS, tvOS, and watchOS apps. Discuss questions here and share app builds publicly via TestFlight under the Community topic.
Post
Replies
Boosts
Views
Activity
I could use an extra set of eyes on this - I'm totally stuck. Any ideas or thoughts on things to check would be much appreciated.
This problem started on 2025-02-06.
It's a Unity project under active development, but I don't see where that can create a problem when using Transporter.
We have been uploading fine for months.
Now we are seeing errors like this:
<RLT-005> INFO: Upload Failed: (id: 650d9057-eb69-4d32-a765-e53894c332e3 file: myapp.ipa part: 24) ([1/3] will retry): org.apache.http.NoHttpResponseException: The target server failed to respond
<RLT-005> INFO: Starting upload for reservation: (650d9057-eb69-4d32-a765-e53894c332e3) file: (myapp.ipa/24) attempt: 2 size: 5242880
<main> ERROR: myapp.ipa (8) - Bad Status received from server: 400
<main> ERROR: Could not upload 1 file(s):
<main> ERROR: Could not upload file: myapp.ipa 28 parts failed: [10, 24, 5, 14, 7, 2, 16, 19, 25, 1, 21, 9, 3, 6, 8, 15, 12, 27, 18, 26, 11, 20, 17, 4, 23, 28, 13, 22]
<main> ERROR: Please retry your upload later.
That "400" server error has me thinking it could be something on Apple's side. But I've also seen this error:
INFO: Verifying checksums against the previous upload attempt.
<main> ERROR: A file(s) has been modified between the initial upload and restart of the upload. Please retry your upload.
So I don't know what to make of it.
Nothing had changed in how we use Transporter.
Things I've tried:
I have tried the Transporter command using all three "-t" options: Aspera, Signiant, HTTP. Same errors.
I have tried using a new app password.
I have tried upgrading the OS version to Sequoia 15.3.
Xcode 16.0 with iOS 18 stuff
I have tried upgrading Transporter to 3.4.1.
I am running a Mac mini - M1, 2020.
I am working on trying with a different host on a different internet connection. Maybe some network security device is interfering somehow.
I am able to manually use Xcode to archive the project and upload it to TestFlight, so the problem appears to be isolated to Transporter or the servers it talks to.
The only unexpected warning I see when manually archiving and uploading is something about a HelpShiftX.framework dSYM not being included. Could that be a cause of the Transporter issue?
I've been getting this error when opening TestFlight since this morning.
I tried restarting the network, re-install testflight, updating my iPhone, and re-logging with my Apple ID.
This error prevents me from installing or updating all apps linked to my account, so I don't think it's related to a particular app permission.
I am reaching out regarding the ITMS-91061 rejection issue we encountered while submitting our app to the App Store. The rejection is related to missing privacy manifests for Firebase and related SDKs.
Currently, our PrivacyInfo.xcprivacy file is structured as follows:
Could you please confirm whether we can modify this file to include Firebase-related privacy information to resolve the rejection? If so, could you provide guidance on the correct format and the necessary entries we should add?
We appreciate your support and look forward to your response.
Hello everyone,
I am experiencing an issue with the Info.plist file in my app, which prevents me from selecting a build on TestFlight. After several attempts to resolve the issue using Xcode documentation and forums, I contacted Apple Developer Support for assistance.
My Support Journey:
Developer Support Team
They identified that the issue lies with the CFBundleAlternateIcons key in the Info.plist file.
However, they informed me that their scope is limited to administrative support for the Apple Developer Program and redirected me to the Developer Technical Support Team for code-level assistance.
Developer Technical Support Team
After reviewing my case, they advised me to use an alternative approach to the CFBundleAlternateIcons key in the main app bundle (Payload/maxplayer_androidtv.app/Info.plist).
They recommended seeking further guidance on forums or through other technical resources.
Below is the current content of my Info.plist file:
<key>CFBundleIcons</key>
<dict>
<key>CFBundlePrimaryIcon</key>
<string>AppIcon</string>
<key>CFBundleAlternateIcons</key>
<string>AlternateIcon</string>
</dict>
<key>XSAppIconAssets</key>
<string>Images.xcassets/AppIcon.appiconset</string>
<key>TVTopShelfImage</key>
<dict>
<key>TVTopShelfPrimaryImageWide</key>
<string>TopShelfImageWide</string>
<key>TVTopShelfPrimaryImage</key>
<string>TopShelfImage</string>
</dict>
Could anyone provide guidance on how to properly structure this file to resolve the issue? If anyone has an example of a correct Info.plist file supporting alternate icons (CFBundleAlternateIcons), I would greatly appreciate it.
Thank you in advance for your help!
I cannot use the Test Flight app for over 12 hours. This problem seems to have occurred periodically for over a decade, so why hasn't Apple provided any solution?
Ayer invité a un grupo de pruebas en testflight para probar una aplicación y en el email que se envía aparece como asunto:
"Empresa has invited you to test App1" y en el contenido: "App1
By Empresa for iOS".
En mi organización no hay nadie que se llame "Empresa", ni si quiera yo, que fui quien envió la invitación.
"Empresa" es el nombre de un cliente anterior al que le hemos creado otras aplicaciones con anterioridad.
¿Dónde está almacenado ese "Empresa"? ¿Cómo lo puedo cambiar?
How can I handle multiple schemes of the same app on Testflight? Do I have to create separate apps on App Store to handle different schemes?
Currently, I am using different bundle ids for various schemes.
Is there a way to upload the Test Details>"What to Test" information alongside TestFlight builds without using Xcode Cloud?
We'd like to be able to have this be part of our build automation process.
End of last week I found the build on TestFlight marked as expired even if the evaluation period was not ended. I created and uploaded a new build, it is listed in App Store Connect, but I cannot assign tester groups (when I try I get an error message). Also, I'm internal tester but when I try to install the app using TestFlight I got error "Cound not install [app name]. The requested app is not available or doesn't exists".
I mistakenly included iPad support in version 2.0.0 of my application, which has never been released or reviewed. The current state is ‘2.0.0 Prepare for Submission.’
When I try to upload a new build or even a new version, I receive an error message: "This bundle does not support one or more of the devices supported by the previous app version”.
What should I do in this situation? How can I delete this build or the entire version 2.0.0 and start over?
I want to upload the ipa to the TestFlight. For this I created the archive and validated it. Its show validated with below warning. I also clicked on distribute its show uploaded to apple with below warning. But when I checked on TestFlight the app is not showing. Sometimes its show under processing but within few seconds it disappears. My Xcode version is 16.1.
Upload Symbols Failed The archive did not include a dSYM for the Razorpay.framework with the UUIDs [654F4A20-5A85-369B-9211-D98E364FD681]. Ensure that the archive's dSYM folder includes a DWARF file for Razorpay.framework with the expected UUIDs.
Upload Symbols Failed The archive did not include a dSYM for the hermes.framework with the UUIDs [4EAC6EDE-5B89-36B7-8F77-09A0E75C2F4A]. Ensure that the archive's dSYM folder includes a DWARF file for hermes.framework with the expected UUIDs.
My developer posted the latest beta release of our app to test flight. When I went to install it on my Mac - the the progress circle gets about 2/3 of the way to completion, then installation stops - and I see the Install button again. Apple M1 / 16GB ram / Sequoia 15.3
Hello
I'm developing a React Native application and I added IAP (like subscriptions) to my app. For it I user react-native-iap, I suppose It's the most common library to integrate in-app purchases.
So, I created 3 subs on App Store Connect and tested it on the iOS simulator. Firstly I was receiving the empty array instead of subs data, but when I have been add StoreKit to my project I became to receive an appropriate subs data with all corresponding information. Moreover, I could successfully subscribe on them.
But, when I released app on the TestFlight for internal testing I forced with the familiar issue, I received an empty array.
In conclusion, on the debug version everything works (subscriptions data returns), but on the release I can't to receive the same result.
Hello does a flow exist to watch the status of an unlisted app request? I submitted into what seems like a black hole of feedback...thx for any feedback on this.
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.
I've already done my test on development signed app locally, all in-app purchase runs well with sandbox tester Apple ID.
Errors happens when make a purchase in distribution app from TestFlight.
Detail Info:
in Apple Store connect , make app available to China
Electron project, packaging by electron builder using distribution sign
upload to TestFlight, invite myself to test
using my Apple ID(not the sandbox tester) to login and purchase
dialog appears and said "Account not in this store"
VPN is off
Apple Store shows Chinese language and Chinese apps, not llikely to be u.s. store
I'm suspecting that:
Maybe shouldn't use my developer Apple ID to run TestFlight test?
TestFlight locked app to be in u.s. store ?
I'm seeking advice on distributing a beta iOS app to a business partner for internal testing, but we're encountering a challenge due to their organization's use of Managed Apple IDs.
Problem
We are developing an iOS app for B2B use and need to provide our partner organization with a beta version for testing. However, this partner organization strictly utilizes Apple Managed IDs for all their employees. Their devices are configured in a way that employees cannot use personal Apple IDs on their company devices.
This effectively prevents the use of TestFlight, as TestFlight requires personal Apple IDs for testers.
We understand TestFlight is the standard recommendation for beta distribution, but it seems incompatible with organizations heavily invested in Managed Apple IDs and their associated security policies.
Question
What are the recommended alternative methods for distributing our iOS beta app to this organization for testing, considering these constraints? Are there any official Apple-recommended solutions for B2B beta testing in this scenario when TestFlight is not viable due to Managed Apple ID restrictions?
Any insights, suggestions, or alternative approaches would be greatly appreciated. We want to ensure we're following best practices and respecting the partner organization's IT policies while still enabling them to effectively test our application.
Thank you in advance
I've received this email when attempting to upload my app to test flight, but I have a long description like "This app collects motion data to track user activity and provide accurate workout insights. Motion tracking helps improve fitness and health-related features." specified in the project.pbxproj file, which is where all of these parameters are (and where I've specified them in the past).
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.