Hi, I have an app in the App Store and I have a build in TestFlight with around 400 public testers who were added by public link. I started getting reports from some testers recently that they were removed as testers from TestFlight. It just says "Tester removed" for them in TestFlight. The build also didn't expire. Nobody else has access to my developer account, so I'm sure that no testers were removed manually. There are plenty free slots for public testers and those testers are also quite active. So I don't see why TestFlight keeps seemingly randomly removing testers. I already have around 5 reports of this where testers complained that I removed them from testing for reporting bugs. Does this happen to anyone else? Is there any reason for this or is it just a bug? Thanks!

Hello, today I can't add external testers, nor add build to actual external testers to use in testflight. I think this happen with the change made yesterday in the website of Apple. (Yesterday it was impossible to upload build) Is it same for you ? Yes I have developers' rights.

The current state of testing promotional codes in IOS is not developer friendly in the slightest. I have been trying to implement and test promo codes for a couple months now, while having the store kit integration helps slightly to mimic offer code redemption there is no friendly way of testing offer codes in test flight. I have it implemented with presentCodeRedemptionSheet() it seems the easiest way to test the codes is release my app to production create a 3-day promo which is the minimum amount of days that can be set, then wait 3 days before I can test again in different ways. One of my colleagues who is not a developer also wanted to test this feature and it did not work for her. Unfortunately it was a month long promo code she had redeemed so will have to wait till September to see if this is fixed for her now. I have also must note the fact the code redemption sheet and setting up payments in apple all together is a buggy mess. Starting out I added my card via apple pay thinking this would be enough to go through the redeem code process. Then upon entering my code it would show the dialog to verify with touch ID along with my payment details and even a picture of my card. After verifying, it then kept showing a pop up that I must include payment information which I already had added via apple pay. In the end to fix this I had to remove the payment method restart the device, add the payment method again then restart the device again. Another issue I bumped into is when you press redeem the "redeem offer" button is disabled but nothing happens for a while until it appears to timeout and you have to try again until it eventually works. The final annoyance I experienced was creating the offer code for my subscription and immediately trying to redeem it apple said the offer expired even though i set it to the 31st of August and the date was the 2nd. Only way to fix this was once waited and keep trying banging your head against the wall until it eventually works. In summary, I hope apple have a review of their offer code redemption process and make it more developer friendly and implement a way of testing within test flight whether it use live offer through test flight or include a new section to add test offer codes for subscriptions.

Hello, I have an app built with flutter. This app uses phone number authentication. When I test it in the simulator, it sends the SMS with the security code, and also reCaptcha works. When I use testFlight on the real device, it doesn't send the sms and neither does reCaptcha work. can you help me?

Some time ago I forwarded the invite to TestFlight from my work Apple ID to my personal Apple ID (email addresses) and was testing on a personal iPhone device. I want to stop testing on my iPhone and move testing to my work iPad. Therefore, I removed the app in TestFlight from my personal device (selecting "Stop Testing") and app is no longer available. I also removed the work Apple ID from the list of all testers for the app, as well as from the internal tester list. I then added it back, sent the invitation, but it will not work on the iPad. Subsequent builds generated new invitation codes and none of those work either. I tried three so far. It appears my personal Apple ID is somehow permanently connected to TestFlight, even though there is no reference to my personal Apple ID in the work account. I see no references in my personal Apple ID account to the app either. Any suggestions to get the invite to work? I don't know what else to do other than create a new Apple ID, but would rather not for a variety of reasons.

Been happening for about 3 weeks. Cleared cache and cookies. I've logged out and back in and rebooted my laptop. Also tried both safari and chrome. My coworkers had the same problem a couple of months ago, and it just resolved itself. Repro steps Login to app store connect tap on testflight tap on any screenshot feedback. With feedback open, I can only see Open in Xcode and OK buttons. Expected behavior :to have access to a delete button. Actual : nly see Open in Xcode and OK buttons.

From past 2 days we are not seeing any build on Testflight. Though while uploading it says sucessfully, but when we see it in testflight, it shows us error " Sorry, something went wrong. Try your request again. If the problem continues, contact us."

Hi. I’m developing an application for a client and I’m in his team in the AppStore. Since October 5, 2022, we have encountered such a problem in TestFlight, for all versions of applications the testing period has expired, although some were uploaded only that day. On October 6, I uploaded a new build of the application to TestFlight in hope that the whole will be available for downloading. But that did not happen. It is visible in TestFlight and it has not expired for testing, but when I try to download it on a mobile device through the TestFlight application, I get error that “Could not install App - The request app is not available or doesn’t exist”. Is there a solution to this problem?

Getting issue in. uploading build from Xcode 14.1. My OS is Ventura 13.0. I am getting following error wile uploading app. Metadata/Info.plist Mismatch. The value for bundle_version in the metadata.xml file does not match the value for CFBundleVersion in Corey Health [Payload/Corey.app]. (ID: 9726552c-a8a0-4e23-aec7-a5e20ac2ce1f). Please help

suddenly getting this message for test flight installs what is going on?

I've been using TestFlight with my app for weeks. I just uploaded a new update to App Store Connect and got the email that the new version is available for TestFlight. I open TestFlight and can see the new version of the app with "Update" next to it. At first, I got an error that said "Beta Expired". Now, test flight says "Install" next to the app and it if pressed it runs like it installing, but nothing happens, it then returns to the "Install" status. I've tried removing and re-inviting the user, delete and reinstall the app from app store, and deleting and reinstalling TestFlight. Nothing works. Can anyone help?

Hello guys, I have an Electron app build with electron forge (v6.0.4). I was able to pass the verification via Transporter and able to install it from TestFilght. but the app was not able to run. I have tried to run the app from Terminal, I got the following error message: FATAL:mach_port_rendezvous.cc(142)] Check failed: kr == KERN_SUCCESS. bootstrap_check_in com.xxxx.yyyyy.MachPortRendezvousServer.39844: Permission denied (1100) Then I looked into the system logs, I found: 2022-12-17 22:03:10.473560 (gui/501 [100006]) : denied lookup: name = com.apple.CoreLocation.agent, flags = 0x1, requestor = AppName[39844], error = 159: Sandbox restriction 2022-12-17 22:03:10.473654 (system) : denied lookup: name = com.apple.locationd.desktop.registration, flags = 0x8, requestor = AppName[39844], error = 159: Sandbox restriction 2022-12-17 22:03:10.482191 (system) : failed lookup: name = com.epsecurity.bdconnectorservice, requestor = BDCoreIssues[162], error = 3: No such process 2022-12-17 22:03:10.537167 (gui/501/com.apple.xpc.launchd.unmanaged.AppName.39844 [39844]) : added unmanaged active 2022-12-17 22:03:10.537647 (gui/501 [100006]) : failed activation: name = com.xxxx.yyyy.MachPortRendezvousServer.39844, flags = 0x1, requestor = AppName[39844], error = 1: Operation not permitted I have tried with/without com.apple.security.personal-information.location in my entitlements file, but looks like no difference. I have spent many days on it, anyone can help?

Initially I removed the macOS support for my iPhone app. Now I want to enable it, so I enabled macOS Designed for iPad in Xcode, and also enabled macOS in App Store Connect for the app. In TestFlight on macOS it shows "Requires macOS and a Mac with Apple Silicon chip" but still lists it under IOS only Apps. (My Mac is Mac Book Air M1, macOS 13.1). I have another simple app which I created and it works just fine and I can't find any difference in the build setup between the two. I have verified the App works well with Mac (Designed for iPad) simulator so the App do work on macOS that much is certain. So my question is how can I enable macOS for an IOS app that previously was only built for iPhone/iPad. Either I'm missing a step or there is a bug lurking here. As it is now I am not able to install the app on macOS from TestFlight. Thanks, Marcus

I do the following steps: Connects to the sandbox account through the settings Installing the app from a test flight Trying to subscribe to the app payment pop-up opens with my Apple ID and not with the sandbox account

Any one has previously faced the below issue am facing it today not able to move on from terms and condition page in test flight app.iOS version : 15.0.2 iPad Pro 3 rd generation.could some please help me out on this.

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?

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.

I have a managed workflow expo app which I am trying to submit to App Store. The build was successful but the submission from project directory (cannot use xCode due to managed workflow) fails with the error " Asset validation failed The app references non-public selectors in Payload/{appName}.app/{appName}: _isKeyDown, _modifiedInput, _modifierFlags My eas.json looks like this: { "cli": { "version": ">= 3.7.2" }, "build": { "development": { "distribution": "internal", "ios": { "resourceClass": "m1-medium" }, "developmentClient": true, "android": { "buildType": "apk", "gradleCommand": ":app:assembleRelease" } }, "preview": { "distribution": "internal", "ios": { "resourceClass": "m1-medium" }, "developmentClient": true, "android": { "buildType": "apk", "gradleCommand": ":app:assembleRelease" } }, "production": { "ios": { "resourceClass": "m1-medium" }, "developmentClient": true, "android": { "buildType": "apk", "gradleCommand": ":app:assembleRelease" } } }, "submit": { "production": { "ios": { "appleId": "******", "ascAppId": "******", "appleTeamId": "******", } } } } And my app.json like this: { "expo": { "name": "******", "slug": "******", "version": "1.0.1", "orientation": "portrait", "icon": "./assets/icon.png", "userInterfaceStyle": "light", "splash": { "image": "./assets/splash.png", "resizeMode": "contain", "backgroundColor": "#ffffff" }, "assetBundlePatterns": [ "**/*" ], "ios": { "supportsTablet": true, "bundleIdentifier": "******", }, "android": { "adaptiveIcon": { "foregroundImage": "./assets/adaptive-icon.png", "backgroundColor": "#ffffff" }, "package": "******", }, "web": { "favicon": "./assets/favicon.png" }, "extra": { "eas": { "projectId": "******", } }, "plugins": [ [ "expo-image-picker", { "photosPermission": "The app accesses your videos to let you share them with your friends." } ] ] } } I have no clue as to what goes wrong here and unfortunately all other solutions referencing this error refer to xCode settings which can be altered, but again not an option here since I am using the managed workflow of expo... Any help would be much appreciated!