Post not yet marked as solved
I'm encountering an issue with my TestFlight builds that were uploaded and submitted for App Store review. After uploading my application to TestFlight, it was working fine for 10 days. However, one day after submitting the app for review, all the versions of my builds changed to expired.
I'm unsure why this is happening, as the expiration date shown in my developer panel indicates that my builds should be valid for 80 days. I've also checked my distribution certificate and provisioning profile, and they are both still valid.
This issue is concerning as I'm not sure if it will affect the App Store review process, and I have not received any feedback from the App Store review team yet. I'm also unsure if this issue is related to the expiration date shown in my developer panel or if there is some other underlying issue.
Has anyone else experienced this issue with TestFlight builds expiring prematurely after submitting for App Store review? Is there anything I can do to resolve this issue and ensure that my app remains accessible on TestFlight? Any help or advice would be greatly appreciated.
Thank you in advance for your assistance.
Post not yet marked as solved
This seems kind of odd. I am preparing a quick review of TestFlight setups for a testing group using my second apple ID. Everything works as expected on an iPhone. However, when I download TestFlight on an iPad with the same Apple ID, it only shows me macOS Only Apps and not iOS Apps.
I must have some setting wrong somewhere but for the life of me I can't find it. Any ideas?
Post not yet marked as solved
Hello,
I am a contract developer who works for a client that owns two apps, one is an App Store customer app. The other is for internal use only.
The client had two accounts, one a regular account for our customer app. The other account was an Enterprise account for the internal app.
The Enterprise account expired, and on renewal the client selected the wrong number of employees so they can no longer use that account to host the internal app (apparently a minimum number of internal employees is required?).
What is the best solution moving forward?
At the moment we're thinking about leveraging TestFlight, putting the internal users themselves on an external testers list, and pushing up "test" builds which the internal users would use like normal.
Is there a preferred/suggested alternative? I've read that it's a misuse of TestFlight and possibly goes against Apple policy.
Any help greatly appreciated.
Hi, thereI sent a testflight invitation to testers and they had successfully received the invitation mail.The mail includes a button of which name is "View in Testflight".As I remember, when the button is clicked on desktop, the redeem code should be shown. But it wasn't.(*I checked that on iOS device, the button opens Testflight app)So, my question is.. how can I get the redeem code?FYI, the URL is like:https://beta.itunes.apple.com/v1/invite/XXXXXXX?ct=XXXXX&advp=10000&platform=iosBest
Post not yet marked as solved
According to this WWDC video: https://developer.apple.com/videos/play/wwdc2021/10203/
Beta Apps delivered via TestFlight App to testers will automatically and nearly instantly send 🤣 Crash Reports to Xcode Organizer. And the documentation states that this will happen REGARDLESS of the device Send Diagnostic Data setting.
We have been using TestFlight for the last week and NOT ONE Crash report has been sent to either Organizer OR App Store Connect Test Flight dashboard. All we get are "Screenshots" with some typed feedback.
What is going on APPLE?!
Post not yet marked as solved
I've had TestFlight installed for a while, and am running a beta version of one app. Recently, I've been getting a notification, maybe once a day, asking me to sign in to get the latest versions of apps.
But so far as I can tell, I'm already signed in. If I click on the notification, it takes me to TestFlight, but there is no option to sign in. It just shows me the one app I'm beta testing, which appears to be active.
In fact, I can't even see any option to sign out, so this notification is really confusing me.
Am I signed in? Am I not? Am I actually receiving new versions of apps in TestFlight? How do I sign in (or even sign out)?
Post not yet marked as solved
Hi,
I'm getting this error while pushing my app for testflight
Dear Developer,
We identified one or more issues with a recent delivery for your app, "MyAppName" 1.4.24 (1). Please correct the following issues, then upload again.
ITMS-90129: The bundle uses a bundle name or display name that is already taken.
Best regards,
The App Store Team
I've been abled to push version 1.4.16, 1.4.17, 1.4.19, 1.4.20 successfully before with no issues, and I'm sure I'm still holding the bundle identifier but yet this error is still appearing everytime I try to upload a new build. I'm wondering if anyone else having the same problem?
Post not yet marked as solved
mencantaria probar las aplicaciones y juegos atraves de esta progrrama TestFlight pero no se como se obtine el acceso
Post not yet marked as solved
Hello developers ! It's my first app I add in Apple Store Connect. I want to test my app with testflight. But i have this error when i try to download the app. "The Requested App is not available or doesn't exist".
I tried multiple things :
Rebuild
Use other device with new mail
Correct all warning in my apps
and more (don't remember :O)
Actually i still not submit my to review to Apple. Maybe i have to do a first submit with success to have access to TestFlight ?
If you have any solutions or anythings i'm open to try . I tried to find a solution for 3 days but without success ...
Thank you very much !
Post not yet marked as solved
Hi all! I'm facing an issue with new update of TestFlight, 3.3.0, where the TestFlight app itself crashed when trying to install the companion Apple Watch app. When "Show app on apple watch" is switched on in the TestFlight app, TestFlight crashes. App cannot be installed through the Watch app either. Anyone else facing this issue??
Prior to the update the same version of my app was able to be installed easily.
Post not yet marked as solved
I'm trying to upload an app to TestFlight with the Xcode 14.2, and I get this error on validation. The app has an action extension and a dynamic framework that's shared between the extension and the app itself.
I'm really not sure what this is supposed to mean. Has anyone gotten this issue or have any ideas?
Post not yet marked as solved
I've submitted a testflight version last night and received some crash by testers. But when I going to download the crash report in https://appstoreconnect.apple.com/apps/1550921126/testflight/crashes, the download failed with a server error.
I am sure my network is good. Can somebody check this?
Post not yet marked as solved
We have an app that will ultimately deploy the app store build via MDM. We're currently not in the app store but are in Testflight and would like to deploy via MDM.Is that possible?How does Testflight restrict what users can run the app?
Post not yet marked as solved
hey there - suddenly all my testflights are crashing instantly.
Built the app with a no-code tool (adalo.com) which, to this moment, served perfectly.
Anyone struggling with the same issue?
Note: as the app is developed in adalo, i don't have any crashing report..
Post not yet marked as solved
Our releases are being blocked due to a bug when testing in Sandbox/Testflight.
We have confirmed pricing is correctly configured in App Store Connect, and out production/live app is working as expected.
In Sandbox/Testflight our prices display in the app as expected, but when purchasing the purchase UI displays Starting Prices instead of Current Prices.
This is causing our release to get rejected even though this is a bug on the Apple side.
We have submitted to Feedback assistant twice without any reply. Anyone have any experience with this or getting Apple dev support's attention to fix?
Post not yet marked as solved
Hi I can't find this clarified anywhere--I see the note that APP STORE SUBMISSION will require Xcode 14.1 (https://developer.apple.com/news/?id=z1erkhzr#) starting in April, but it's unclear whether you can still submit Testflight external test builds that were created with a lower version of Xcode. Will Testflight still accept Xcode 13 .ipas? Thank you!
Post not yet marked as solved
We've recently (since yesterday) have been experiencing an issue where builds submitted to TestFlight via Xcode Cloud get queued for ~3 hours.
Here's an example:
The build itself takes ~20 mins:
Is anyone experiencing such issue?
Hi,
I have submitted my app to TestFlight but I did receive a warning message:
The app references non-public selectors in Payload/AppNAME: dataChanged
I tried to investigate the issue but can't find a solution 🤨
Any idea?
Post not yet marked as solved
We got this message after publishing our app to test flight:
ITMS-90725: SDK Version Issue - This app was built with the iOS 16.0 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later.
I'm no math genius but am pretty sure that 16 is greater than 15.
Why did I get this messages? Can I ignore it? will it prevent my app from being able to be submitted to the app store?
Post not yet marked as solved
I've previously used Testflight to install new app builds for myself and a small group of trusted testers prior to releasing to everyone on the public app store.
A couple months ago Testflight installs randomly just stopped working and I get the error message on in the TestFlight app when trying to install
Could not install "App Name"
The requested app is not available or doesn't exist
Does anyone have any ideas what might be wrong?
Note: My app is currently in the app store and available for anyone to download. I read that some people have seen this issue because they're apps weren't published, but I don't believe that's my issue since it's marked as "For sale" and is displayed in the public app store.