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

Can you help me how to upload it to TestFlight setting and distribution. I have try it but got this error. I have setting profile for camera access to but it still like this.

I managed to enter the beta program of WhatsApp during my vacation in Cyprus. I installed the app from the TestFlight app, and everything was ok. Now, when I am in my home country (Israel) - I can't see the WhatsApp app in the TestFlight (for example for updating it). I don't know what to do, and there is no information online 😕 Some screenshots to support my problem: This is the app itself in my home screen. It has the orange dot, indicating it is from TestFlight: This is my TestFlight app home screen - no sign for WhatsApp app: This is the WhatsApp app from the App Store app. We can clearly see that it is being recognized that the WhatsApp app is installed through the TestFlight app: When trying to "View in TestFlight" from the App Store, this is the screen in TestFlight I am seeing:

We have an existing app - "Pluralsight: Learn Tech Skills" which is built for mac using mac catalyst. The latest version here is 3.59.0. We are shifting to "Mac (Designed for iPad)" destination instead of catalyst. The build with this change, uploaded from xcode with version 3.60.0, is not visible under macOS/iOS tab under macOS testflight app. Also we are not able to see "iPhone and iPad Apps on Apple Silicon Macs" section under "Pricing and Availability" page. We believe that this needs to be enabled for the mac app built with "Mac (Designed for iPad)". Please help out.

My company has been sharing the redeem code to the company domain email address and allow staff to redeem the app with their personal Apple ID. However, we found that the redeem code is failing and claiming the Apple ID doesn't match the one associated with the invitation. I cannot find the documentation for this change, may I know if this is something permanent?

"Hello everyone, I'm experiencing an issue with App Store Connect and Xcode. My client has granted me admin access to upload an app to TestFlight. However, while I can see the account in App Store Connect, it's not visible in Xcode. I suspect the client's account might be a personal account rather than an organizational one. Can anyone suggest what I might be missing or what additional steps need to be taken? For context, I can see all other teams, but this particular team is not appearing in Xcode. Any help would be appreciated!"

Getting Same Error and App Rejection With XCode 14.2. we have pushed a successful build a week ago and there was no major change in code level and have not added and lib after that but now getting error and app rejected, stuck in this issue from last 1 day. anyone found any solution to this

Let's say my app has two versions: 1.x is the main version 2.x is the beta version - still in testing Is it possible to maintain both of them in parallel on TestFlight ? In the first phase, main version will still receive updates, which are released to the market. Beta version only receives updates for testing purposes. In the second phase, beta version will be published to the market and main version will stop receiving updates. Imagine the following scenario of uploads. Is it possible on TestFlight? version = versionName (buildNumber) upload main version - 1.10.0 (10) upload beta version - 2.0.0 (0) upload fix for main version - 1.10.0 (11) release main version - 1.10.0 (11) to the market upload beta version - 2.0.0 (1) upload beta version - 2.0.0 (2) upload main version - 1.11.0 (12) release main version - 1.11.0 (12) to the market upload beta version - 2.0.0 (13) release beta version - 2.0.0 (13) to the market

My app works fine from Xcode but once installed via TestFlight it drops out immediately without any explanation. It sits in the background with the launch screen showing. I not sure it is getting to run at all. Where can I find reports on what is happening or what could be the issue here? I am new to all this so any help would be appreciated.

I'm confused, and I can't find instructions. I have a build for internal testers. That works great! I created an external group, "Beta". I click Beta. I can set up testers. But when I go to builds, it says "No Builds Available" I filled out the test information form. I don't see any buttons like submit for review. What am I missing? Thanks in advance!

I'm encountering an issue when trying to submit a new build of my iOS app to the App Store. The app launches from TestFlight without any problems, but when attempting to submit it for App Review, I get the following error: "This build is using a beta version of Xcode and can’t be submitted." However, I'm not using a beta version of Xcode. I've tested this with both the public releases of Xcode 16.3 and 16.2. The build logs show no issues with the SDK or Platform versions, but in App Store Connect, the metadata is displaying the following: Build SDK: $(SDK_PRODUCT_BUILD_VERSION) Build Platform: $(PLATFORM_PRODUCT_BUILD_VERSION) Have anyone else experienced this? Any insights on resolving it? Thanks in advance.

I’m getting an error message that’s blocking me from using TestFlight. Once I log out of my account and log back in, it disappears - but then it pops up again after a few days. If anyone knows a long-term solution, I’d really appreciate it!

I get "No Builds Available" when adding new external testers to a build that has already been distributed to 100+ external testers. This happens for all external testers I try to add today: Existing testers still have access to the build. Creating a new group of external testers doesn't help. The issue happens with both new and existing groups. The build was previously approved by Apple Beta Review and expires in 36 days. What am I missing?

Hi all, I’ve run into a frustrating issue with the FamilyControls and DeviceActivityMonitor APIs. I’ve received official approval from Apple to use the com.apple.developer.family-controls entitlement (distribution), and I’ve added the entitlement to both my main app and the DeviceActivityMonitor extension. I’ve also ensured the correct App Group is configured for both targets. Everything works perfectly when I install the app on my own device as an internal TestFlight tester. App blocking works, the DeviceActivityMonitor extension runs as expected, and the apps selected by the user are correctly shielded. However, for external TestFlight testers, while they do receive the Screen Time permission prompt, and can select apps to block, nothing actually gets blocked. It appears that the DeviceActivityMonitor extension is not being triggered at all on their devices. I’ve verified the following: The entitlement is approved and visible in App Store Connect The build is approved for external testing Testers are running iOS 16+ Shielding logic works properly on internal tester devices Clean installs have been tested on external devices Has anyone gotten FamilyControls + DeviceActivityMonitor working successfully for external testers via TestFlight? If this is a known limitation or if there are any additional steps required to enable extension execution for external users, I’d really appreciate any clarification. Thanks in advance for your help.

After I uploaded my app to testflight, the MinimumOSVersion was set to 14.0, and TestFlight showed MinimumOSVersion=14.0. However, after I distributed it, if the user's device is iOS 14, then the MinimumOSVersion in Info.plist=14.0, and if it is an iOS 15 or higher device, the MinimumOSVersion in Info.plist=15.0 will be changed. Because my app will detect this value, I had to change my code, but this is too strange, at least there will be no problem before April 27, 2025, because I checked my distribution records.

When I uploaded app to TestFlight to test, it shows missing compliance. And I tried this way: https://stackoverflow.com/questions/35841117/missing-compliance-status-in-testflight It used to work. But now it is not. May I ask what should I do to solve the missing compliance problem?

I’ve been waiting for a response from TestFlight for an app since yesterday early afternoon how long does it normally take to get a response?

I'm trying to make my app ready for testing in Testflight. I have several apps developed, and it seems the App I'm developing now (BalloonFollow), is ending up linked to a previous app (BalloonNavi) when archiving product. Even though they have different identifiers. The App I'm trying to upload is named "BalloonFollow" but it ends up being archived under "BalloonNavi" which is another "old" App I'm developing. I'm having trouble understanding how they are linked together - the App and the archive. How do I create a new app name (BalloonFollow - for the drop down in organizer) and have the app archived / linked under this new app ?

As I've more verbosely asked at apple.stackexchange.com/revisions/479121/1#:~:text=Screenshot-,Screenshot,-I%20am%20able, when reporting feedback for an application installed via TestFlight, which of Feedback Assistant's "Third-Party Apps"'s "Something else not on this list" or "TestFlight" categories are superior? I ask primarily because applications installed via TestFlight are not enumerated there. However, also because via Feedback Assistant, I can provide significantly better feedback than I can on TestFlight, because of its undermentioned attributes: I can provide follow-up information as I gain more, and correct old information. It provides draft functionality, in case I need to take some time to create an actionable report. I can upload more information, like multiple screenshots and other file types.

So I submitted my app for TestFlight external testing and got this email: ITMS-90078: Missing potentially required entitlement - Your app, or a library that’s included in your app, uses Apple Push Notification service (APNs) registration APIs, but the APS Environment Entitlement isn’t included in the app signature’s entitlements. If your app uses APNs, make sure the App ID is enabled for push notifications in Certificates, Identifiers & Profiles, sign the app with a distribution provisioning profile that includes the APS Environment Entitlement, and upload a new build to ensure that push notifications function as intended. For details, visit: https://developer.apple.com/documentation/usernotifications/registering-your-app-with-apns. But here's the thing: everything this says is 100% bogus. My app uses no libraries and no push notification service registration APIs. The term register is used in my app, because I use table view cell registrations. Could that be the cause of this bogus warning?