This is a bit of a headscratcher. Xcode 16 fyi. I've written a standalone watchos app (with a stub ios app). Distributes and works perfectly over Testflight. I've submitted for app store and it passed the checks an I've released it for sale. Told my brother to use a promo code to download it and show me how it looks and report me any nuisances. He tells me there's no app neither on phone (expected) nor in watch. And he checked both the Watch ios app list and the watch. I've gone through various GPTs and they've all told me the basic troubleshooting. That his watch might not be supported (wrong, it's a watch 10 ultra with latest updates and my min supported versions are hilariously low). They've suggested that I might not have the right keys for making it standalone set, also no. They suggested that skip_install shouldn't be set to no; also wrong I think they're thinking xcode 13 and below. The stub ios app has a dependency on watchos app and also has an embed directive. I also checked the archive and saw the watchos app embedded indeed. Again, the app works perfectly fine when distributed over testflight. And AFAIK that's a release build which I know for a fact because I had a problem with not giving healthkit entitlements to release (that was another but minor headscratcher at the time, when it was working over direct xcode upload). Minor detail, I've written, test(flight)ed the app in UK and in English, my brother is in Turkey. Of course now I immediately pulled the app out of sale because I don't want people paying and getting nothing, that's gonna cause a lot of trouble. So I need any help I can get to How to debug this without exposing the app and myself: is it possible to limit the release? Obviously: what could be going wrong? How the hell did I even pass app review? Is this maybe isolated to my brother's watch? I'm more than happy to share project files and/or info.plist files(end products of them, because my plists are generated from project file).

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.

Hello, I archive my macOS app and Xcode can create it successfully, however when I validate the archive there are 2 errors: Cloud signing permission error (You haven't been given access to cloud-managed distribution certificates. Please contact ...). No profiles for 'my app-bundle-identifier' were found (Xcode couldn't find any Mac App Store provisioning profiles matching 'my app-bundle-identifier'.). I have added my Apple ID account in Xcode and enable "Automatically manage signing" option for signing my app target, and Xcode can build the target successfully without any problem with certificates or provisioning profiles when archive. I have some components (frameworks, daemon, xpc services, share extension) which are put in Frameworks, Resources, XPCServices, PlugIns folders in app's Content, and use post build script to manually code sign for all of these components by ${CODE_SIGN_IDENTITY}, and Xcode can sign those components without any problems when building for archive. I already created Mac App Distribution and Mac Installer Distribution, and macOS App Store profile for my app-bundle-identifier. I don't understand why Xcode still reports the error regarding Mac App Store provisioning profiles when I validate the archive and can't figure out how to fix the issue because I have enabled "Automatically manage signing" so that Xcode can automatically select the appropriate profiles when it archives the app. Any suggestion for how to fix the issue?

My NFC tag for default app clip link (https://appclip.apple.com/id?p= xxxxxx) can work when I distribute to App Store. But NFC tag fail when I want to test in TestFlight. I already set the title and the url (the default app clip link such as https://appclip.apple.com/id?p= xxxxxx )in the TestFlight. Why did this happen?

Hello Apple Developer Support, I've been waiting for my app to become available on TestFlight for testing for around three weeks now. Despite deleting and re-uploading the build multiple times, I continue to face the same issue. I've attached a screenshot of the problem for your reference. Could you please help me understand how to resolve this? It's becoming quite frustrating. Looking forward to your guidance.

I have not been able to update the TestFlight Test Information. I keep getting the error "Make sure the contact phone number only contains numbers and try again" even when only number are entered. I've tried on Safari, Chrome and from the Connect App and all give the same error. I would like to push my App for testing to some external beta testers but can't since Contact Information is required for this.

We have a rather complex network of dependencies for our application stack and, from it, we create multiple unique executables that are placed into the Contents/MacOS directory of our bundle. MyApp.app `- Contents/ `- Frameworks/... `- MacOS/ `- exec_a `- exec_b `- Resources/... Both executables require the same dependencies (and use the same shared .dylib files built as targets in the same project) so it makes sense for them to be in the same place rather than in their own .app folder as I understand it. Qt Libs -> core_lib.dylib -> gui_lib.dylib -> exec_a `-> exec_b etc. We've confirmed build artifacts are correct and the rpath/dependencies are all clean. When in development, all executables run as expected and we can command exec_a (the executable we're listing in the primary Info.plist) to launch exec_b at any time. Once the bundle is signed, however, we cannot get exec_b to launch in any capacity. Even lldb dies right away because it can't attach to anything. We assume this is something in the gatekeeper area of blocking these additional executables. We get the following when trying to run those additional exes in any way: Trace/BPT trap: 5 We're using macdeployqt to finalize the bundle and bring in the correct packages - perhaps something it's doing is causing the additional executables to fail or we're missing an entitlement. We've submitted the app to TestFlights successfully even with these invalid executables to see if there was something the processing of the app would find but so far nothing. We've seen other example of applications with multiple executables in the same MacOS directory and are wondering what the difference is. Any hints or guidance would be great. Thank you!

Hi - I've added in-app purchases (Quarterly and Yearly ) to my app and submitted it for TestFlight. The app is available, but in my Developer account, the in-app purchases section still shows the products as 'Waiting for Review.' When I test the app for in-app purchase, the dialog does not appear. Is this issue of "Approval" of the in-app purchase product? If YES, how can I get approval for these in-app purchase products? FYI: I have attached a screenshot of the in-app purchase products. Please suggest Thanks, Sushil

We are received the following error while uploading the application into TestFlight. **ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit. ** After sometimes we submit the same application without changing the configurations application submitted successfully into the App Store. We are using the Xcode 15.3 version.

Hi everyone, We’ve developed an iOS app that is working perfectly across our internal testing environments including: TestFlight iOS simulators Physical iPhones and iPads within our organization However, during App Store review, the build gets marked as incomplete, and the review team reports the following issues: Issues Reported by App Review: Login error message: "device token must be string" Sign In With Apple: Reviewers are redirected back to the login screen after authentication. No error message is shown, but the user isn't logged in. Account creation: The team is unable to create a new account using the provided credentials. Everything functions correctly in TestFlight, simulators, and local builds. The issue only seems to happen in the App Review environment, making it difficult for us to reproduce. We suspect that push notification permission might not be granted or the token is not being generated in the App Review sandbox environment — leading to a null/undefined value that breaks login. The "device token must be string" message likely appears when our backend validation expects a string, but receives a different type or undefined. Also, the Apple Sign In redirect and account creation failures may be related to Keychain, token handling, or review sandbox behaviors.

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 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!

Hello, my app address: https://apps.apple.com/cn/app/%E4%B8%89%E5%9B%BD%E6%88%98%E4%BA%89%E7%AD%96%E7%95%A5slg/id6741073714?ct=Tap725796 I submitted a version update request for version 1.23.1 on April 10, and submitted an accelerated review application, but it has not been reviewed yet. Today, I have updated the new version to 1.23.2, and submitted an accelerated application request, but it has not been reviewed yet. Maybe because the online version review is stricter, I also submitted a review request for the TestFlight version, which has also been stuck waiting for review. This is an online battle SLG game, which has been updating its version every week for half a year. Because the Android version has been updating steadily, the Apple version has suddenly been unable to update in the past two weeks, resulting in the unusable networking function. Currently, there are a large number of complaints from Apple players. I really don’t know if there is any suitable solution. I will try my best to cooperate as long as I can. I hope that Apple’s official reviewers can provide timely help to developers and Apple players.

Hi everyone, I’m hoping to get advice or hear from anyone with similar experiences. Our app Pixllove was originally rejected under Guideline 4.3 (“Spam”). We were later invited to an App Review call with Erica, who reviewed everything and confirmed verbally and in writing (April 8, 2025) that the spam classification was removed. She acknowledged that our app uses a unique concept and only required us to implement a pre-chat consent popup. We implemented exactly that: • A popup appears before any chat starts, displaying the match’s name, age, and distance. • Users must actively accept before the chat begins. • We show this clearly in our new demo video. • Full reporting/blocking/moderation is in place. However, after submitting the updated build, we were again rejected under a different interpretation of 1.2, with the reasoning that our app “connects users randomly.” This appears to be a misunderstanding, since no match occurred during their test – and it takes at least 2 users online for a match to happen. We explained this and even submitted a screenshot of the consent popup, which had been explicitly requested by Erica. Sadly, the reviewer ignored our message and Erica’s previous confirmation and labeled us as spam again. We replied and asked them to please review Erica’s note from April 8, but we haven’t received a response yet. We’re lucky to have a second review meeting scheduled for Tuesday, but this experience has been extremely frustrating and honestly, quite unprofessional — especially after being told the issue had been resolved. Has anyone experienced something similar? What can be done to ensure prior Apple Review decisions are respected by future reviewers? Thanks so much in advance, Emilija Pixllove Team

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

I integrated an Advanced App Clip Experience to my app. In trying to test the App Clip Card, the card does not appear when I tap the link on my device that is associated to the Advanced App Clip Experience. Listed are some contextual information: Testing on device running on iOS 18.3.1 Associated Domains: Main target app: applinks: App clips target app: applinks: and appclips: Archived and uploaded build to App Store Connect. Green "Testing" status via Testflight. On Distribution tab, green "Valid" status for build domain. Advanced App Clip Experience green "Received" status. Developer App Clip Testing Diagnostics: Green "Register Advanced Experience" status Green "App Clip Code" status Warning "App Clip Published on App Store" Orange Circle "Associated Domains" After looking at countless threads, I still cannot for the life of me find a solution to test the App Clip. Any guidance would be extremely appreciated. I had also submitted a support ticket with case ID #102552504973.

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.

Hi all, I am dealing with a confusing issue relating to a beta build that I am trying to share over TestFlight. I have followed all steps and managed to upload a build to App Store Connect, but I mistakenly selected "Internal Only" when submitting from XCode. This build was accepted (See image), but then when I submitted a build that would be shareable externally, it was rejected under Guideline 4.3(a). I am unsure what had changed between the first and second build I submitted, and I have since updated the app page with more information and screenshots clearly explaining how this is different to other items available on the app store with no luck. Does anyone have any clue what I could do? Signed hopefully, Luke

I have an app that unlocks content based on in-app purchases, both one-time payments and subscriptions. Recently, I added new subscription products, both for distribution in App Store Connect and in the configuration file in XCode to be able to test it, declaring it in the scheme. Since the beginning of development, I have had issues with subscriptions. Every time I close the app and reopen it, in order for the app to recover which subscription is active, I have to run the purchase function. This doesn’t happen with purchases or in the production environment, where it works fine. I’ve now implemented SubscriptionStoreView, so I don’t depend on my business logic, in case I’m doing something wrong in the code. This view never remembers which product I’ve already purchased. Currently, in a version deployed to my phone from XCode, it doesn't even process the payment. On macOS, the experience is even worse. On iPad, through TestFlight, I haven’t even been able to test payments at all.

For my app Find Any File, of which both releases and TestFlight betas were released many times, the TestFlight page tells me that several users have submitted crash reports. And I'm sure the same is true for the MAS releases: (Yes, this shows quite recent ones, but I've seen similar supposed crash report submits in this list before.) However, the actual "Crashes" listing on the appstoreconnect sites hasn't show any new crash reports for many months now: (This is the entirety of crash reports I can get listed, even when removing all filters.) Something appears to be stuck, on Apple's end. The same issue is with Xcode's Organanizer window, for "Crashes": It also used to list only the same very old reports and nothing since May 2024. And just now, when I retried this in Xcode, I'm shown a weird error message I never saw before: Error Downloading Crashes List An error occurred… Access Restricted with adam id: 1207815783 And yes, I'm logged in just fine, under Prefs / Accounts. How am I going to get this investigated? I had already sent an email about this to the Review team, who didn't react to it at all. DTS is only for Code level support, which this isn't. Any help?