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?

I am trying to release a beta version of an app for internal TestFlight testing but I keep getting a notification saying it has invalid binary. I have tried looking this up but I can't find anything that helps. Please help! If you need anything in addition to this, let me know. I just wasn't sure what to share.

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

We have an enormous legacy based application which has been ported from Windows. The build system is make and has literally hundreds of .cpp, .c, .h, .m, and .mm files. I've gotten it successfully running on MacOSX and managed to build nice installation packages using the "Packages" package which have been sucessfully signed, notarized and stapled, and install nicely on "clean" Machines. The .app/bundle format has been lovingly laid out to match the app. Now, I'd like to use Testflight to deliver the app, and eventually the Mac App Store. In my first attempt, I tried xcrun altool --validate-app .. to validate the Packages built app. It, not surprisingly, failed spectacularly because I guess it hasn't kept up with however packages need to be build to pass --validate. (It's an amazing tool though) So, I decided to use pkgbuild and productbuild to build the package: pkgbuild --root App_name.app --identifier com.mycompany.myapp --sign "Developer ID Installer: ...." --scripts Scripts --install-location "/Applications/MyApp.app" Distribution.pkg productbuild --synthesize --package Distribution.pkg Distribution.xml productbuild --distribution Distribution.xml --sign "Developer ID Installer..." --package-path . MyApp.productbuild.pkg xcrun altool --validate-app -f MyApp.productbuild.pkg -u username --type macos This fails with: { NSLocalizedDescription = "Could not find the main bundle or the Info.plist is missing a CFBundleIdentifier in \U2018MyApp.productbuild.pkg\U2019."; NSLocalizedFailureReason = "Unable to validate your application."; } I confirmed I have an info.plist and if contains a valid CFBundleIdentifier, and I extracted the package using Pacifist and confirmed it's there, too. I'm at a loss. Converting the package to XCode would be a monumental effort right now, and I'd really like to avoid it. Is there something I'm missing, or should this work? Thanks!

Transaction.updates When testing on TestFlight, Transaction.updates emits payments that occur on the same device (usually within 1min after payment is finished), contradicting the docs: The asynchronous sequence that emits a transaction when the system creates or updates transactions that occur outside of the app or on other devices. Transaction.unfinished When testing on TestFlight, Transaction.unfinished contains finished payments from a different device (same App Store account). Docs: A sequence that emits unfinished transactions for the user. Both issues do not happen when testing with Xcode. Xcode 15.2, iOS 17.3, 17.4

Hi guys, need some help on this issue when I submit my testing app to TestFlight using GitHub Actions and Fastlane, I get this warning from App Store Connect: We noticed one or more issues with a recent delivery for the following app: Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-90725: SDK version issue - This app was built with the iOS 16.2 SDK. Starting April 29, 2024, 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. I am using React Native CLI, and Fastlane to run and build my app through Github Actions. After scouring around, from what I understood was that all I needed to do was just to update my Xcode and iOS SDK to the latest, which I did. Currently my Xcode is 15.2 and iOS SDK is on 17 already. However, I still receive this warning whenever I submit my app. Is it something that I need to resolve on my end or?

I made the app file in xcode validate the app and then I shared it only in test fligth when I wanted to test it on my iphone 14 Plus device the following message appears try uploading other builds same thing happens with the other two apps I've been two weeks trying to solve this bug or problem, I searched for information on google but what appears is from 2014 how much appstore had the name of itunes Connect, I have asked in other forums and ddicen to wait a while that is normal but I think it takes a long time. If someone has gone through this and put you solve agadeceria you can help me

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

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.

So I have an app live in the app store all good, however I am now developing an update to it that adds the ability to allow photos to be used and that requires that the app gets an additional access to the camera roll. Now on upload to testflight I get this error emailed to me, not in the interface: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. To me that is saying that I cant add new features to an app that requires additional permissions. Is that correct? How can I get around this, will my app get rejected when I submit it due to this, or is it just an information item?

I had everything working with Revenue Cat. Then my app got rejected for not loading subscriptions, which was odd because a previous built was rejected for wording on that same paywall. I checked, and realised I suddenly can't fetch products in testFlight either. I can only see products in Xcode using the store kit configuration file. I've found many issues like this online and everybody point to the same solutions (that seem to work for most), but here's what I tried so far: Checked that all my agreements in App Store Connect are active Checked that ids match between Xcode / revenue cat / App Store connect Store kit config file is syncing with App Store Connect correctly I removed revenue cat and used the store kit api directly to fetch products. The array of products is empty in all environments that don't have access to store kit config file. Checked status of all subscriptions (all waiting for review -- as they were when the paywall worked) Nothing seems to work... Any suggestions? Many thanks