Hello, everyone, I have been having problems with builds uploaded to TestFlight for a couple of weeks now. These , from the app (iPhone, iPad, Mac), are not downloading. If I try I get an error message saying the app is unavailable or does not exist. If I try to add a build to an external tester group I get the warning : There was an error while processing your request. Please try again later. Checking in the browser termianel I noticed the error : Failed to load resource: the server responded with a status of 422 () with in : message: "API Response Error: TF_BETA_APP_REVIEW_RESPONSE" I've tried everything but can't figure out how to fix it. Can anyone. give me a hand? Do you know what is going on?

We have a network content-filter consisting of a main target/GUI, a FilterDataProvider extension and a FilterControlprovider extension. The app is installed via MDMs and works without issues the vast majority of times, but during testing of TestFlight builds we've found that intermittently the device fails to install the network extensions and blocks internet access. The GUI is working fine though. From the logs we can see that when this happens the device tries to start the network extensions repeatedly. The issue is solved by restarting the device. Has anyone experienced similar issues or have some ideas of what might cause this behaviour? These are some of the logs we see in Console: neagent [u E6D696F2-62FB-4262-A97C-B2006EC528C5:m (null)] [<private>(<private>)] Hub connection error: Error Domain=NSCocoaErrorDomain Code=4097 "connection to service named <BundleID>.FilterDataProvider" ugDescription=connection to service named <BundleID>.FilterDataProvider}code-block Failed to start the data extension <BundleID>.FilterDataProvider: Error Domain=NSCocoaErrorDomain Code=4097 "connection to service named <BundleID>.FilterDataProvider" ugDescription=connection to service named <BundleID>.FilterDataProvider} nehelper Denying connection from nesessionmanager (264) because it is missing the com.apple.private.network.socket-delegate entitlement nesessionmanager <BundleID>[inactive]: starting launchd Service could not initialize: posix_spawn(/private/var/containers/Bundle/Application/F84E2325-05A6-4DC2-8DD6-20C97EF43E8D/<AppName>.app/PlugIns/FilterDataProvider.appex/FilterDataProvider) failed, error 0x2 - No such file or directory nesessionmanager NEFilterPlugin(<BundleID>[inactive]): Sending start command nesessionmanager <BundleID>[inactive]: starting neagent Looking for a data extension with identifier <BundleID>.FilterDataProvider neagent [d <private>] <PKHost:0x718915550> Query: { NSExtensionIdentifier = "<BundleID>.FilterDataProvider"; NSExtensionPointName = "com.apple.networkextension.filter-data"; } neagent Found 1 data extension(s) with identifier <BundleID>.FilterDataProvider neagent Looking for a control extension with identifier <BundleID>.FilterControlProvider neagent [d <private>] <PKHost:0x718915550> Query: { NSExtensionIdentifier = "<BundleID>.FilterControlProvider"; NSExtensionPointName = "com.apple.networkextension.filter-control"; } neagent Found 1 control extension(s) with identifier <BundleID>.FilterControlProvider neagent Beginning data extension request with extension <BundleID>.FilterDataProvider neagent [u C743CE7B-9E19-4A41-BF46-91AEFB24169D:m (null)] [<private>(<private>)] Failed to start plugin; pkd returned an error: Error Domain=PlugInKit Code=4 .<AppName>.FilterDataProvider(C743CE7B-9E19-4A41-BF46-91AEFB24169D): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch ErrorDomain Code=2 "No such file or directory" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}" UserInfo={NSLocalizedDescription=RBSLaunchRequest error trying to launch 7B-9E19-4A41-BF46-91AEFB24169D): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0xdb88df3d0 {Error UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}} neagent Extension request with data extension <BundleID>.FilterDataProvider started with identifier (null) neagent Failed to start the data extension <BundleID>.FilterDataProvider: Error Domain=PlugInKit Code=4 "RBSLaunchRequest error trying to launch vider(C743CE7B-9E19-4A41-BF46-91AEFB24169D): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., SIXErrorDomain Code=2 "No such file or directory" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}" UserInfo={NSLocalizedDescription=RBSLaunchRequest error trying to DataProvider(C743CE7B-9E19-4A41-BF46-91AEFB24169D): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., SIXErrorDomain Code=2 "No such file or directory" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}} nesessionmanager NESMFilterSession[FilterDataProvider:0C4C9E40-5005-47A5-8C60-F7C8630F29DF] in state NESMFilterSessionStateStarting: plugin NEFilterPlugin(e with error: 1 nesessionmanager <BundleID>[266]: disposing neagent Initializing the delegate neagent App <BundleID> is not installed or is not valid neagent App <BundleID> is not installed or is not valid neagent Failed to find a com.apple.networkextension.filter-data extension inside of app <BundleID> neagent NEAgentSession: failed to create the delegate nesessionmanager <BundleID>[259]: Tearing down XPC connection due to setup error: Error Domain=NEAgentErrorDomain Code=2 "(null)" nesessionmanager <BundleID>[259]: XPC connection went away nesessionmanager NESMFilterSession[FilterDataProvider:0C4C9E40-5005-47A5-8C60-F7C8630F29DF]: Failed to start with error: Error Domain=NEAgentErrorDomain Code=2 "(null)"

The Statement I have a SwiftUI app that uses CoreData and iCloud with NSPersistentCloudKitContainer prepared for beta testing via TestFlight. The app utilizes iCloud solely as a private database for user data across different devices. The app doesn't use any public or shared database. According to Apple's guidelines, deploying the development schema to production is necessary before submitting to the App Store: Before you publish your app, you must deploy the development schema to the production environment to copy over its record types, fields, and indexes. I am aware that once deployed to production, it's impossible to delete or modify any types or fields: To prevent conflicts, you can’t delete record types or fields that are already in production. Every time you deploy the development schema, its additive changes merge into the production schema. The Questions: When is the appropriate time to deploy the schema to production? Should it be done before beta testing via TestFlight, or is it sufficient to deploy it just before releasing the app on the App Store after beta testing? If the schema needs to be deployed before beta testing, does that mean I won't be able to reset the schema if testers discover critical bugs related to the data model, and I'll be compelled to delete or modify any types or fields? Thank you in advance for any responses!

Xcode crashes when i'm validating/distributing my archived app for testflight testing purposes. I have previously submitted two versions of the same app, and didn't have this problem. The only changes are the source code (which successfully builds and runs on the ios simulator or different android machines), and the Version (which is currently 0.0.8, while the previous were 0.0.6, 0.0.7) Whenever I press the button for validate app/distribute app, the process crashes. I recorded the screen and found that it crashes on validating "Runner.app". I have tried doing the steps below, and none of them are working. Any hints of solving this issue would help a lot. checked that my apple developer account has agreed to all terms of use updated macOS, xcode, cocoapods to the latest version deleted all developer/xcode cache files and rearchived the source code and revalidated the app uninstalled and reinstalled xcode tried increasing the application version/build version in xcode checked my version number consists of three integers (0.0.8, 0.0.9, etc) the xcode build ios/device is selected identical to the one installed on my mac m1 (iphone 15 pro max, ios 17.2) FYI This is the report i got after xcode crashed. Translated Report (Full Report Below) Process: Xcode [33912] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 15.3 (22618) Build Info: IDEApplication-22618000000000000~2 (15E204a) App Item ID: 497*** App External ID: 863*** Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 5** Date/Time: 2024-03-16 00:55:26.7732 +0900 OS Version: macOS 14.4 (23E214) Report Version: 12 ... System Integrity Protection: enabled Crashed Thread: 7 Dispatch queue: com.apple.root.default-qos Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [33912] Application Specific Information: abort() called Application Specific Signatures: success ==================================== Any type of help or advice is welcome. Thanks.

I received an email that says, although submission for TestFlight review was successful, you may want to correct the following issues in your next submission for TestFlight review. Once you've corrected the issues, upload a new binary to App Store Connect. I am aware of the one minor issue that needs to be corrected. Which we will upload soon. What I don't understand is that the email says that the Test review was successful but yet My status is still saying waiting for review. Can I get some clarification please....

My archived xcode builds show that they have been successfully uploaded to testflight but once in the appstore they do not appear. Is there anyone else with the same problem?

rt thanks

I encounter a warning: "Cannot be used with TestFlight because the signature for the bundle at “Lattics.app” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight." (90886). I don't need the TestFlight. And I add "com.apple.application-identifier" to the entitlements, but it crash on opening. I got an error: Code Signing Crashes

Hello, We're having a problem from the past week with installing / updating all our apps from Testflight. All the testers get this error message after tapping the "Install" or "Update" button: "Could not install . The requested app is not available or doesn't exist". Can you please help investigate and let us know why this issue occurs? Thank you! Note: We're using Xcode 15.2 both locally and on CI through Xcode Cloud

Does anyone know how TestFlight counts the number of installs, sessions and crashes? I'm seeing totally insane numbers. I don't understand. Right now for the latest beta it shows me: number of installs "-", number of sessions 19 and number of crashes 36. What's that supposed to mean? When I look at the individual testers, sometimes there's already complete crap there. For example, there is a user who has reached 1180 crashes in 13 runs. What? Can you imagine a person who runs an application 1180 times and it crashes? I don't. What's really best, TestFlight gives me almost no crash logs. There were a few from the early betas, but none the last few days. Do you know of any other tool from which I get consistent information on absolutely all crashes?

The app was uploaded correctly in previous versions and suddenly stopped working in Test flight. There is no warning in Xcode when archiving, I use to verify (xcode option) the app before uploading, and upload only for Testing. The owner of the developer account enrollment already asked on last friday and there is no response at all.

we have an app in App Store Connect; we have 4 External Testing groups; we have testers, who are simultaneously in two or more groups; tester who consists in several groups can see all available builds in these groups on their device via TestFlight; I choose to remove the tester from one group; check this group - the tester is removed; check other groups - the tester remains in other groups; but checking the TestFlight on the device shows "tester removed" and NONE of the builds available before can be seen now. According to this article: Removed testers will no longer have access to new builds added to this group in the TestFlight app. They’ll continue to have access to existing builds until they expire, but in fact we can see opposite behavior and the tester looses access to ALL groups and builds in TestFlight after being removed just from one of the groups. So the question is: is there a way to fix this? Or we misunderstand the explanation of "Remove testers from a group"?

What should i do if i wanted to use iPhone device on MacOS? Previously when i have only iPhone in destination, it appeared as "Mac (Designed for iPhone)", but after i added iPad, it auto changed to "Mac (Designed for iPad)". Now it's running on iPad device in TestFlight when opening from M1 Macs. How do I get it to run on iPhone device?

I've uploaded a new build 0.2 (build 3) to the TestFlight platform, and invites have gone out. But when they click on the invite it takes them to a previous build 0.2 (build 1) (which I've deactivated. So no-one can install or update the new build. Attached are screenshots of what this looks like when I invite myself to the tester group. I've tried deleting the. old version from my phone so that no versions exist on my phone but that doesn't help.

I have successfully build app and upload but not show in the Builds.

I deploy Codepush on react native. When I push new code to update on testflight and when I press install on the device then close the app and reopen the app, it crashes. How to fix it ? Thanks! x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000000000000010 x5: 0x0000000000002280 x6: 0x00000002816e2280 x7: 0x0000000197c0985d x8: 0x08b0abbc53e37153 x9: 0x08b0abbda73d74d3 x10: 0x0000000168421887 x11: 0x003f00010680a400 x12: 0x000000000000003e x13: 0x000000010680a7d0 x14: 0x04000001f4def511 x15: 0x00000001f4def510 x16: 0x0000000000000148 x17: 0x00000001f4de0580 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x0000000000000103 x21: 0x00000001f4de0660 x22: 0x0000000106009f80 x23: 0x00000001f6201d10 x24: 0x0000000000000010 x25: 0x000000019ed8fa4f x26: 0x00000001f576adf0 x27: 0x00000001f3acc000 x28: 0x0000000000000000 fp: 0x000000016baae0e0 lr: 0x00000001eccd31ac sp: 0x000000016baae0c0 pc: 0x00000001dc56f674 cpsr: 0x40000000 esr: 0x56000080 Address size fault

Hey all, Tl;dr: In debug-build using a .storekit file, all is good. When uploading a release build to testflight, purchasing follow the expected flow, but it does not seem the subscription status is reflected. Full description I've implemented auto-renewable subscriptions in my app. In debug, I've setup a scheme to use products.storekit. When I run this scheme on my device, I can subscrbe, cancel etc, and it all works as expected. When I upload my release scheme to testflight, purchasing can be done, but changes do not seem to be reflected inside the app (i.e.e no features get unlocked). Same thing when I run this scheme on my device. This scheme has None set for Storekit configuration. When I set 'Storekit configuration' to the Products.storekit, file I can't make a purches at all: SubscriptionStoreView shows Subscription unavailable. The subscription is unavailable in the current storefront'. I've watched a number of WWDC sessions on the topic, read most (all?) of the documentation, and I just can't seem to find out what it is that needs to be done. Unfortunately, debugging has been rather cumbersome and sometimes impossible lately, especially when trying to debug a release build. Anyone can tell me what it is I am overlooking, or what piece of information or link I missed? Here is the relevant code (which works OK in debug) private func listenForTransactions() -> Task<Void, Error> { return Task.detached { for await anUpdate in Transaction.updates { do { let transaction = try self.checkVerified(anUpdate) await self.checkSubscriptionStatus() await transaction.finish() } } } } And here's checkSubscriptionStatus(): @MainActor private func checkSubscriptionStatus() async { var hasActiveSubscription = false do { for aStatus in try await Product.SubscriptionInfo.status(for: "718A7488") { let state = aStatus.state hasActiveSubscription = (state == .inGracePeriod) || (state == .subscribed) } } catch { print(error) } self.hasActiveSubscription = hasActiveSubscription }

I'm working on an app (actually in Test Flight) that has camera and NFC support. So in iPhone is obviously working as expected, but when testers want to try the camera "aspect" of the app on iPads they can't even download the app it says "No compatible hardware" in Test Flight. What I need to do in this case, I already have a UI/UX solution when theres no NFC support or it's disabled (Android can detect this) but here I have no clue if I'm missing something. Thanks in advance

I have got an error response when I have summit app for review. Any one face this issue please kindly help. Thank { "errors": [ { "id": "a9580e9f-103a-4a02-94c0-0a181df057df", "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." } ] }

After creating an install with pkgbuild/productbuild and submitting for TestFlight, one of the errors I got was: 2024-03-03 16:51:36.715 *** Error: Asset validation failed The product archive is invalid. The installer package may not include install scripts. (ID: 78500c2e-db43-4bd3-8e23-215b2fc30e15) (90254) { NSLocalizedDescription = "Asset validation failed"; NSLocalizedFailureReason = "The product archive is invalid. The installer package may not include install scripts. (ID: 78500c2e-db43-4bd3-8e23-215b2fc30e15)"; NSUnderlyingError = "Error Domain=IrisAPI Code=-19241 \"Asset validation failed\" UserInfo={status=409, detail=The product archive is invalid. The installer package may not include install scripts., id=78500c2e-db43-4bd3-8e23-215b2fc30e15, code=STATE_ERROR.VALIDATION_ERROR.90254, title=Asset validation failed, NSLocalizedFailureReason=The product archive is invalid. The installer package may not include install scripts., NSLocalizedDescription=Asset validation failed}"; "iris-code" = "STATE_ERROR.VALIDATION_ERROR.90254"; } That seems pretty explicit. Are install scripts like postinstall no longer allowed?