In this case, I used my project project to export the ipa to testflght. The tester installed the app on the test device, started the app, and received the payment voucher information pushed by storekit. At this time, the test device did not log in to the sandbox account. Of course, The test device has previously logged into the sandbox account and successfully paid for the subscription. When I used the same test device, connected to Xcode, clicked run, and ran the app, I did not receive the payment voucher information pushed by storekit. I am very confused, why does testflight receive the certificate information pushed by storekit?

I am using an iPhone 14, with IOS 18 on a managed account and keep getting "Temporarily Unavailable" error when trying to launch TestFlight. This app worked on another organization managed device (same device, IOS) but several others are giving temp unavailable errors. Can anyone help guide me on how to fix this error? I have tried uninstalling, restarting, reinstalling several times with no luck.

Can someone tell me how to fix the TestFlight “temporarily unavailable” error? I am using an iPhone 14 with IOS 18 and the device is under an organized managed account TestFlight works on another phone on the same account but gives error on others.

Hi guys, I’m writing an app that integrates Screen Time API more specifically one that has only DeviceActivityReport. The app runs as expected but I have an issue when pushing it to AppStoreConnect: Provisioning profile failed qualification: Profile doesn't support Family Controls (Development). Provisioning profile failed qualification: Profile doesn't include the com.apple.developer.family-controls entitlement. Provisioning profile failed qualification: Profile doesn't support Family Controls (Development). Provisioning profile failed qualification: Profile doesn't include the com.apple.developer.family-controls entitlement. My app has Family Controls (Development) set in Capabilities, entitlement file, provisioning profile and distribution certificates. I have already requested Apple for the entitlement key for Family Controls (I’m waiting for them to reply). So, I have few questions now: Can I distribute a build for internal testers via TestFlight without waiting for Apple’s reply to my request? Do I need to wait Apple’s reply to distribute the app to internal tester under Family Controls (Development) ? Has anybody had the same issue and solved it without waiting for Apple to approve the request during development (no distribution)? I have done a deep search about this topic but it is still not clear to me if an internal build could be distributed under Family Controls (Development) or if it is mandatory to wait for the distribution one

Unable to upload new ipa builds to TestFlight since today

We are trying to upload iOS app in Test Flight. The iOS SDK version we are using is 18 and Xcode Version is 16. While uploading the app (we are using Jenkins & Fastlane), we are getting an error saying the app is built with iOS SDK 16.4. Due to that we the upload is failing. The error text says An error occurred during the build: Error uploading ipa file: [Application Loader Error Output]: [ContentDelivery.UploadError c0000171810C] Asset validation failed (90725) SDK version issue. This app was built with the iOS 16.4 SDK. All iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution. (ID: 671ae668-d311-43de-b85c-1d142f6a8fbd) [Application Loader Error Output]: Error uploading '/var/folders/qq/2qkbtw5s7657 5cmd3kq0kmwh80gm7/T/73c3d853-ddb3-48b6-a78f- bfbb979afbb.ipa'. [Application Loader Error Output]: Asset validation failed SDK version issue. This app was built with the iOS 16.4 SDK. All iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution. (ID: 671ae668-d311-43de-b85c-1d142f6a8fbd) (90725) [Application Loader Error Output]: The call to the altool completed with a non-zero exit status: 1. This indicates a failure."