Hello, I’m experiencing an issue with in-app purchases (IAPs) not working in my TestFlight build. Here's the situation: I created several non-consumable IAPs in App Store Connect and added them to my app. All IAPs have been approved by Apple and show the status “Ready to Submit” or “Ready for Sale.” I integrated Unity IAP correctly, and it works on Android. On iOS, however, the IStoreController is not initializing in TestFlight. I suspect the issue might be that I created a new app version before adding the IAPs, and never submitted that version. Later I added IAPs, but they don’t appear to be linked to any build. The In-App Purchases section doesn't appear in the App Store Connect version overview, and I can't find a way to connect them to the current build. What should I do in this situation?

Can Apple Developer relations please reconsider my application to attend the workshop July 29-31 in Cupertino. As someone on the forefront of AI and solo engineer, getting guidance on launching alongside IOS26 would be really helpful. The unknowns of testing and distribution are a bit difficult to overcome. I do not have 2-5 person team. Its just me. Thank you for your attention to this matter.

hello, i am currently trying to add a hardpaywall to my app. When I test in testflight with storekit config set to "none" in scheme. I get an error saying unable to load subscriptions.

Hi guys, I have an app ready for testing/distribution. But when I used Transporter to send the app to Apple Store Connect, I got the following warning. ITMS-90885: 'Cannot be used with TestFlight because the executable “${executable}” in bundle “${bundle}” is missing a provisioning profile but has an application identifier in its signature. Nested executables are expected to have provisioning profiles with application identifiers matching the identifier in the signature in order to be eligible for TestFlight.' The executable and bundle values were missing from this warning message, which does not help find the warning cause. Could someone give me some advice to resolve this issue? Thanks!

Dear Apple Developer Support Team, I recently registered a personal Apple Developer account successfully and submitted an app for TestFlight beta review with the App ID 6748887468. However, the status has remained in "Waiting for Review" for quite a long time. I’ve read that TestFlight beta app reviews are usually completed within 24 hours. Given the extended delay, I’m concerned there might be an issue with my submission, or that my developer account might be missing some required documentation. Could you kindly help me verify if there is any issue preventing the review process from moving forward? Thank you very much for your support.

Hello, i can not instal app from testflight from today. Could you help me with this? It shows: that testflight is not connected to Appstore Conect.

My app only offers consumable in-app purchase products. I can successfully purchase a product once but when I try to purchase it again, a popup "This In-App purchase has already been bought. It will be restored for free." appears and the first transaction is restored: the payment queue delegate is notified that a new transaction (with the same identifier as the successful transaction) is updated to the purchased state. I never get a purchased transaction with a new identifier and hence I consider that the purchase failed. Also, each time the app is put in foreground again or at startup, the payment queue delegate is notified that a transaction has been updated (as if it had never been finished). Even though the app properly finishes the transaction each time.

Beta testers outside the US, for our MacOS App, are being told their ID is not valid in the US Store and that they must switch to a store in their country. Yet the store switch fails Essentially beta testers outside the US cannot do testflight sandbox eCommerce for the Mac version of our app. Note that eCommerce on the Mac works for US based testers and eCommerce for the iOS/iPadOS works for testers in all territories. Many of these testers are in India, the UK and Canada. We believe that this is incorrect, that storeKit is not correctly detecting the AppStore Region for mac based testflight eCommerce. At this point we have 382 testers, most outside the US and we can only Beta Test our app with US users. Attached are images of the messages that are coming from storeKit: Here is a link to a video from a user in Canada who is demonstrating the problem (cut and paste into browser) https://youtu.be/kB818wfVld4 Here is another link to a video from a user in Canada who is demonstrating the problem (cut and paste into browser). https://youtu.be/7uAZKo8wpfU We see that there is another post with a similar problem. Similar eCommerce Problem Because eCommerce works in all territories on iOS/iPadOS but ONLY in the US for Mac we suspect that this is an error that either a DBA or a coder will need to fix. Any insights from anyone would be appreciated.

Hi everyone, I’m currently developing an iOS app using the latest Xcode Beta and targeting the new iOS SDK (still in beta). I would like to share my app with external testers, but I’m facing several issues: • When trying to upload a build to TestFlight via App Store Connect, I get validation errors saying that builds from beta versions of Xcode or the iOS SDK are not accepted. • I am aware that Apple generally restricts beta builds from being distributed via TestFlight, but I was hoping to find a workaround or an official statement regarding timelines for RC or final support. • Are there any recommended methods for sharing my app with external testers while still using Xcode Beta? • Is Ad Hoc distribution still a valid approach for this scenario, or are there other alternatives I should consider (e.g., Enterprise, third-party platforms)? • Any tips on best practices for managing testers, provisioning profiles, or planning for the transition once the Release Candidate becomes available? Any advice or recent experiences would be greatly appreciated! Thanks in advance.

I have an approved public link to our app in Test Flight. We have provided that public link to our testers. For us it works just fine, but for multiple of our testers, their access is requiring either an invitation code or requiring them to "redeem", neither of which occurred during our internal testing nor which should be required for a public link. Help!

‏Hello, ‏I would like to join the testing of your app on TestFlight, but I need an invitation code. Kindly please send me the TestFlight invitation code if possible. ‏Thank you very much!

Hi there! I've been getting this error when I've checked multiple times that I've included the right entitlements as well as provisiong profile. My one concern is that perhaps I'm unable to submit to internal or external TestFlight with Family Controls (Development) and need the one for distrubution, but have yet to submit my appplication for this ability. If anyone has any inisght into this issue lmk!

I have hosted the AASA file in our server and added the App associated domain and have added the local Appclip experience in Device settings with the same URL which i create Appclip QR. But when i install build from testflight i dont see the Appclip card coming up.Its working if i directly load it from xcode My associated domain - appclips:acviss.com (configured from main and appclip target) Qr code generated like this AppClipCodeGenerator generate --url https://acviss.com/restaurant1 --foreground 33AA22 --background FFFFFF --output myclip.svg In Device Setting>Developer>Local Experience URL Prefix - https://acviss.com/restaurant1 Bundle Id - com.acviss.RestApp.Clip AASA file hosted at https://acviss.com/.well-known/apple-app-site-association

Hi! I am currently in the process of having my app reviewed by apple so it can be distributed on TestFlight. However, apple keeps on rejecting my build because "The UIRequiredDeviceCapabilities key in the Info.plist is set up in such a way that the app will not install on the device used in review." I am very confused on how to solve this problem as I have tried many different solutions, including removing UIRequiredDeviceCapabilities entirely, or giving it the value 'arm64'. I just wanted to know if anyone has encountered this same problem and could maybe point me in the right direction. I have attached the full error message below. Thank you! The UIRequiredDeviceCapabilities key in the Info.plist is set up in such a way that the app will not install on the device used in review. Review device details: Device type: iPhone 14 Pro and iPad Air (5th generation) OS version: iOS 18.5 and iPadOS 18.5 Next Steps To resolve this issue, check the UIRequiredDeviceCapabilities key to verify that it contains only the attributes required for the app features or the attributes that must not be present on the device. Attributes specified by a dictionary should be set to true if they are required and false if they must not be present on the device.

My app has been approved on tesflight for Internal and external testers, but when I click on the public link that the external link is a part of, I get "This beta isn't accepting any new testers right now." I haven't hit the maximum because there are 0 testers right now. Please Help!

I'm repeatedly hitting an issue when deploying Xcode Cloud builds to macOS from TestFlight. Once the build appears in TestFlight I hit the "Install" or "Update" button in TestFlight and after a couple of seconds of spinning-wheel the button goes back to it's original state and the app fails to install. There's no error pop-up but I've noticed an Error Domain=ASDErrorDomain Code=710 "Invalid hash 'xxx' expected 'yyy'" error in console each time it happens. My project needs to deploy 2 different macOS/Catalyst apps (actually they are 2 different targets in the same project) and it seems completely random as to which will actually successfully install on which machine. For my last build, one of the 2 binaries was failing to install on a Mac Studio on 15.5, but the other was fine. All were fine on 3 other machines I tried. For my latest build, both binaries are fine on the Mac Studio but both now fail to install on an M2 Air on macOS 26 beta 2. I'm now extremely nervous about deploying to my TestFlight beta group in case users have similar problems.

Hello, I'm trying to test an app clip in TestFlight with a Local Experience. Is there any way to test app clips "end to end" from a local experence? The clip I'm developing uses Apple Pay, so we'd like to be able to test the full experience using sandbox accounts. The documentation indicates that this is possible: documentation link Testers can also configure a local experience to launch the App Clip you distribute with TestFlight. However, you must still associate your App Clip with your website so testers can launch it from the TestFlight app. In addition, testers must launch the App Clip from an App Clip experience you configure for testing in App Store Connect at least once to ensure that the App Clip is cached on the device. I've had some success with running the clip from a local Xcode build, then installing a TestFlight build "over top" of the Xcode build, e.g. I can scan a QR code with a URL configured for a local experience and the card will show and launch the clip, but that seems to "expire" after a period of time. More information: App (but not App Clip) is currently live in the app store. App Clip is in TestFlight and launches using TestFlight experiences App Clip and App are associated with our website Am able to launch the app via QR code with a full installation from TestFlight Am able to see Local Experiences when the clip has been built locally and run on my device using Xcode Local Experience does not show when using a fresh install from TestFlight even when configured with the same values Local Expereince does show and work when using a TestFlight build installed over top of an Xcode build

I can't download my app via TestFlight in macOS Tahoe. Earlier versions work. Some other apps can be downloaded via TestFlight on Tahoe. The app is a MacCatalyst app that's not yet released on the App Store. The console prints the error: Download failed with error: Error Domain=ASDErrorDomain Code=710 "Invalid hash 'XXX' expected 'XXX'" But no error is displayed. Is there a solution?

I built a new version to TestFlight on June 27th, but it still hasn't been displayed yet.

Hi developers. I've been working on a Watch companion app for my product these past few days, and I'm currently trying to push it to TestFlight. I get stuck at the validation step with endless errors. The first one typically is missing WKApplication in Info.plist. That's fine, I'll add the field in Watch target > Info. Now more errors appear: Invalid UIDeviceFamily value of '1' and '2' Unsupported key UIRequiredDeviceCapabilities DTPlatformName value invalid Missing architecture, the bundle must contain arm64_32 because it's built with watchOS SDK 5+ I never set these values in the Info tab, so my guess is they're being overwritten by the Runner Build Settings, even though watch target build settings are correct (for example, Targeted Device Family is set to Apple Watch). What I've tried so far: Disabling auto generation of the Info.plist, and manually setting UIDeviceFamily to '4', but that doesn't help, unless I do it after creating the archive by editing the archive files and resending it to validation. I also tried a bunch of other post-build modifications to try and fix all the errors but new ones kept popping up. Cleaning Build Folder and DerivedData, restarting XCode, rebooting the computer... no effect, which is expected given that the building process doesn't return any errors Validating just the app without the apple watch (so from my main branch), still works as expected. Recreating a blank watchOS target and trying to validate just that, I get stuck in the same way. Project details: XCode Version 16.3 (16E140) Flutter 3.27.3 Targeting latest watchOS and iOS 16+ Do you have an idea what could be the problem here ? I'm sure it's just a missing or invalid property in some configuration file, but I can't figure it out and there are no resources online documenting the issue, and no "tutorials" on how to properly set up a watch target from Apple. Thank you for your time. A.H.