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

Hello, during development of a simple game for iPhone and iPad, I'm using a Swift package to keep track of app launches — this does not collect any user-related information. Only the device model, iOS version and build version number are reported by the package, which automatically also includes the originating IP address. While looking at the Swift package reports, I'm seeing a few unexpected entries: launches from devices that do not belong to any testers (established by looking at the device models) launches from builds that have been expired in App Store Connect launches from IP addresses apparently from the Apple WAN (established by looking up the addresses via e.g. whois) A single public link to a TestFlight build was shared with a single group of testers — none of which have the device models described above in 1. This link has been expired as soon as I noticed the unexpected entries. But the entries keep coming, and they mostly coincide with new TestFlight builds — although the launches do not come from the new builds, but rather from older ones. Has anyone experienced something similar with TestFlight builds...? Thank you, D.

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

Hi, I am testing out an update for my app in macOS Sonoma. I first installed the App Store version of my app on the device running macOS Sonoma, and it ran fine. I then installed an updated version of my app through TestFlight (built with macOS Ventura SDK), but when I run this updated version, I get prompted ”MyApp differs from previously opened versions. Are you sure you want to open it?". Why is this happening? Is this warning only because the app is updated through TestFlight, or do I need to do something to prevent this warning from happening when I update my app through the App Store? I see this mentioned in an Apple security update:: App Sandbox now associates your macOS app with its sandbox container using its code signature. The operating system asks the person using your app to grant permission if it tries to access a sandbox container associated with a different app. For more information, see Accessing files from the macOS App Sandbox. My app is already sandboxed, and I'm not trying to access a different app's sandbox container, just my own. For the TestFlight build, it probably also uses the same Release configuration that the App Store build uses. I might have changed my provisioning profiles recently because they expired. Would that affect this and cause a prompt to be showed? Would love to know more about this prompt and how to avoid it. 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.

Since yesterday, we have experienced Xcode Cloud failing to upload our archives to TestFlight/App Store. Unsupported SDK or Xcode version? Here is one of the error messages we see on Xcode Cloud: Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases. All of our Xcode Cloud workflows are configured to use the 'Latest Release' of Xcode and macOS (Currently Xcode 15.3 Release Candidate (15E5202a)), so I'm unsure why we are getting the above error. Invalid Bundle (SPM)? Some other errors that have just started to pop up are related to our Swift Package dependencies. We use Xcode's in-IDE interface for managing package dependencies (no custom Package.swift file). Here's some of the error messages we've seen: Invalid Bundle. The bundle {MyAppName}.app/Frameworks/{FrameworkName}.framework does not support the minimum OS Version specified in the Info.plist. Invalid MinimumOSVersion. Apps that only support 64-bit devices must specify a deployment target of 8.0 or later. MinimumOSVersion in '{MyAppName}.app/Frameworks/{FrameworkName}.framework' is ''. Missing Info.plist value. A value for the key 'MinimumOSVersion' in bundle {MyAppName}.app/Frameworks/{FrameworkName}.framework is required. The bundle 'Payload/{MyAppName}.app/Frameworks/{FrameworkName}.framework' is missing plist key. The Info.plist file is missing the required key: CFBundleShortVersionString. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring I am not sure what to make of these errors, as we have not made any changes to minimum deployment version of any of our project's targets. These errors seemed to start happening out of nowhere, sometime between last Friday and yesterday. Any help would be very appreciated!!

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 }

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?

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." } ] }

I created a release app and then uploaded a test flight. so after installation and trying to open the app. app crashed. this was created on Xcode 15.2. and also this worked on Xcode 14 properly. please help us to fix this issues. please check this. this is an error log