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?

Hello, I created an app using the latest version of Xcode (16.2), and I'm having a problem testing this app on my iPhones. I created this app just like all the others I've made for my clients, including one on (03/24/25), but when I went to upload another App to App Store Connect on (03/26/25) I couldn't test it on my phone. Points to consider: The app runs perfectly on the Emulator. All my terms and agreements with Apple are up to date. I tried to download the apps through Testflight on 2 different devices, iPhone 7 Plus (iOS 15.8.1) and iPhone 15 Pro Max (iOS 18.3.2), and I was unsuccessful in neither attempt. I can send my app to the internal testers, but when I click download, the following message appears: Could not install [APP NAME]. The requested App is not available or doesn't exist. I imagine this problem is with Apple itself, I have already contacted support, but I need to resolve this urgently for my customers. Has anyone experienced this and resolved it?

I am creating an AI powered mobile application for my university dissertation that utilises Google Gemini in order to generate tailored responses with a prerequisite prompt. In order to facilitate this, I use an API key which allows the communication to be made. I received an email upon archiving my application that informed me that: ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “Amrit AI.app” bundle should contain a NSSpeechRecognitionUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required." I have since made the adjustments to my info.plist by adding a description as to why the API key is being used. However, it still has not rectified the issue. I have contacted multiple apple support lines and none of them have been able to help with my error. I am under extreme pressure to upload this application to the App Store before my dissertation deadline as the reviews are critical to my evaluation section. Any help would be much appreciated.

My app crashes immediately when downloaded from TestFlight. When built directly from Xcode it works fine. Xcode version: 16.3 iOs device: iPhone 13, iOs 18.3.2 Error: Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: DYLD 4 Symbol missing Symbol not found: _$s11DappBrowser27WalletConnectCryptoProviderC0cD6Signer0eF0AadEP9keccak256y10Foundation4DataVAJFTW The same source code previously worked fine when using Xcode 15.3 to upload to Test Flight.

After downloading the application from TestFlight and installing it on the iPhone 13 Pro Max, it does not open. The following exception was captured on the phone: Exception Type: EXC_CRASH(SIGABRT) Exception Codes: 0x00000000000000, 0x00000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 There are no errors when compiling in Visual Studio 2022 or when uploading the app to the store for testing via TestFlight.

The internal tester group was added by default, and the status is now "Testing." However, when I click the plus icon to add an external tester group to this build, nothing happens—it just displays the current tester group. How can I start the external testing?

TestFlight Beta Testing You must first remove all builds and testers from the app you want transferred and clear each information field below Test Information. But all of my testflight versions are expired. and therre is no teste member on it.

My Team is not able to receive TestFlight inviation. This started having since last week.

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 experiencing an issue where the official TestFlight app crashes immediately upon launch on a device running iOS 14. Unfortunately, I’m unable to update the system to a newer iOS version, so I need TestFlight to work properly on iOS 14. I’ve attached the crash log for your reference. Could you please help identify the root cause of the crash, or let me know if there’s a workaround? TestFlight-2025-04-11-100957.log

Hi everyone, I’ve been facing an issue with TestFlight external builds that I haven't encountered before, and I’d appreciate any insights. Background: I have an iOS app that was recently approved and released to the App Store. Prior to this, I’ve regularly submitted TestFlight builds (with updated version and build numbers) to both internal and external tester groups. Internal builds would appear instantly, as expected. External builds were also available almost immediately after selecting “Ready to Submit.” This was consistent for many iterations. Current Issue: After pushing the latest version to the App Store (which went through the standard review process and was approved), I prepared a new version for TestFlight testing. Here’s what happened: Uploaded a new build with a new version number and build number. It appeared instantly for internal testing as usual. When I tried adding it to the external tester group, the build got stuck in the “Waiting for Review” state. I uploaded this on Saturday night, and as of Monday noon, the status has not changed. I also cancelled that build and uploaded a fresh one with an incremented build number — still stuck in the same status. Additional Notes: The app’s ITSAppUsesNonExemptEncryption key is set to false in Info.plist. There is no missing export compliance warning on App Store Connect. The changes in the new build are minor — a few small updates, nothing significant. I tried decreasing the build number temporarily (which caused an error), then increased it again. No changes were made to permissions, app capabilities, or metadata that would typically trigger a longer review. Questions: Is this expected after an App Store release? Has anyone else experienced delays like this recently for TestFlight external builds? Is there anything I can do to expedite the review? Thanks in advance for any help!

I submitted an App for TestFlight review in order to undertake a Public Beta program. In the App Review Information I included notes for the review process, including information that may be needed to test your app, such as app-specific settings and test registration or account details. The above link says You must provide the following information to App Review. It isn’t visible to customers. However, the public beta site includes the Review Notes, including test credentials! Is this a bug, or simply a misunderstanding on my part?

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.

Hello. I’m currently using Flutter to develop iOS apps and Watch Apps for Apple Watch. I created an archive in Xcode and tried uploading it to App Store Connect, but I was experiencing multiple validation errors like the one below, which made me unable to proceed. Here is a summary of the error I separate info.plist between iOS and watchOS, but it doesn't reflect even when I set the watch side. I think the settings on the iOS side have been reflected. I'm in a very difficult situation Thank you Prepared archive for uploading Upload failed error: Validation failed Invalid UIDeviceFamily. The Info.plist of Apple Watch application 'Runner.app/Watch/ Watch App.app' contains an invalid UIDeviceFamily value of '1'. (ID: xxx) error: Validation failed Invalid UIDeviceFamily. The Info.plist of Apple Watch application 'Runner.app/Watch/ Watch App.app' contains an invalid UIDeviceFamily value of '2'. (ID: xxx) error: Validation failed Invalid WatchKit App Bundle. The value '16.6' for the MinimumOSVersion key in Info.plist in bundle 'com.example.xxx' is not supported. (ID: xxx) error: Validation failed Invalid Info.plist key. The key 'LSRequiresIPhoneOS' in bundle Runner.app/Watch/ Watch App.app is invalid. (ID: xxx) error: Validation failed Invalid Info.plist key. The key 'WKAppBundleIdentifier' in bundle Runner.app/Watch/ Watch App.app is invalid. (ID: xxx) error: Validation failed Missing Apple Watch Extension. The application 'Runner.app/Watch/ Watch App.app' is missing its corresponding Apple Watch extension. (ID: xxx) error: Validation failed Missing Icons. No icons found for watch application 'Runner.app/Watch/ Watch App.app'. Make sure that its Info.plist file includes entries for CFBundleIconFiles. (ID: xxx) error: Validation failed Missing Info.plist value. A value for the Info.plist key 'CFBundleIconName' is missing in the bundle 'com.example.xxx'. Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key. For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7. (ID: xxx) error: Validation failed Invalid Info.plist value. The value for the key 'DTPlatformName' in bundle Runner.app/Watch/ Watch App.app is invalid. (ID: xxx)

Necesito ayuda Porfavor urgente algún código de invitación para poder entrar a TESTFLIGHT porfavor lo necesito urgente saludos y bendiciones

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 ?

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?

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.

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?

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!